From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#55743: 28.1.50; No directory error in comp-run-async-workers Date: Fri, 03 Jun 2022 08:55:31 +0300 Message-ID: <837d5ye1f0.fsf@gnu.org> References: <86y1yhsxin.fsf@mail.linkov.net> <83wne1h66x.fsf@gnu.org> <86wne1trce.fsf@mail.linkov.net> <83leuhgljn.fsf@gnu.org> <861qw97x41.fsf@mail.linkov.net> <83h754hbwf.fsf@gnu.org> <86a6aw2o4e.fsf@mail.linkov.net> <83o7zcf9kw.fsf@gnu.org> <861qw7zf6r.fsf@mail.linkov.net> <83ee07fq6y.fsf@gnu.org> <87czfr32ex.fsf@gnus.org> <83bkvbfo8q.fsf@gnu.org> <878rqf30tu.fsf@gnus.org> <838rqffihz.fsf@gnu.org> <8735gmcuhf.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12865"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55743@debbugs.gnu.org, juri@linkov.net To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jun 03 07:56:37 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nx0IW-00039U-RY for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 03 Jun 2022 07:56:37 +0200 Original-Received: from localhost ([::1]:60324 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nx0IT-0008BK-KL for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 03 Jun 2022 01:56:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nx0Hy-0008BB-2E for bug-gnu-emacs@gnu.org; Fri, 03 Jun 2022 01:56:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:32874) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nx0Hx-0003zD-PH for bug-gnu-emacs@gnu.org; Fri, 03 Jun 2022 01:56:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nx0Hx-0001Ri-KT for bug-gnu-emacs@gnu.org; Fri, 03 Jun 2022 01:56:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 03 Jun 2022 05:56:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55743 X-GNU-PR-Package: emacs Original-Received: via spool by 55743-submit@debbugs.gnu.org id=B55743.16542357325501 (code B ref 55743); Fri, 03 Jun 2022 05:56:01 +0000 Original-Received: (at 55743) by debbugs.gnu.org; 3 Jun 2022 05:55:32 +0000 Original-Received: from localhost ([127.0.0.1]:55004 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nx0HU-0001Qf-04 for submit@debbugs.gnu.org; Fri, 03 Jun 2022 01:55:32 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35926) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nx0HP-0001QL-DU for 55743@debbugs.gnu.org; Fri, 03 Jun 2022 01:55:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48006) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nx0HJ-0003rI-Ah; Fri, 03 Jun 2022 01:55:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=20L7eSuvKIDt9DaBLD8LcElIx3urFWNXfbwGK63B0+w=; b=dt20WMH2Tx7g i7nhoLLIpyC2s1c5HGPXNlRQQEEmpHnnT/ELJ4SeBw8uIm1LBWO3CSXgRYKnjQdlQuB78VN1hqc1O fju4fHT+ZLmIQLrb3+QaYw3NVxOg6s+KPO1GyiGWsfamBxVDNA4C5baLwZ9OiskDEfBFw3voZIlMr NC5eq2U6KviR0+7XcrNLC4sTPcwLMXoq7TPIKF5yXd8i6Y6x7lwPPFdT1kZqYfsH7LwsHejrW8kWF URrSihKPaSS9h0Pt4aGldSOxdILeXrgmYcwpwTGNKCuR2EskVRqfRH25JnVNBnKcspZa4Xka3AnAt j+hQRhpHHnR/2JhUInT5fA==; Original-Received: from [87.69.77.57] (port=2047 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nx0HI-0000SO-Qd; Fri, 03 Jun 2022 01:55:21 -0400 In-Reply-To: <8735gmcuhf.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 03 Jun 2022 05:10:36 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:233585 Archived-At: > From: Lars Ingebrigtsen > Cc: 55743@debbugs.gnu.org, juri@linkov.net > Date: Fri, 03 Jun 2022 05:10:36 +0200 > > Eli Zaretskii writes: > > > Once again, how would you know what is the correct directory that will > > allow the compilation (in this case) or any external process (in other > > cases) DTRT? The place where we invoke comp-run-async-workers cannot > > possibly know enough about the compilation to make such decisions. > > comp-run-async-workers knows that it needs an existing directory to > work, so it should arrange to have an existing directory be the current > one. Yes, we can arrange for an existing directory, but: . it could be wrong, i.e. it could yield wrong compilation results . it will silently sweep under the carpet cases like this one, where a Lisp program makes default-directory invalid -- don't we want to uncover such cases?