GNU bug report logs - #55743
28.1.50; No directory error in comp-run-async-workers

Previous Next

Full log

Message #53 received at 55743 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 55743 <at> debbugs.gnu.org, juri <at> linkov.net
Subject: Re: bug#55743: 28.1.50; No directory error in comp-run-async-workers
Date: Thu, 02 Jun 2022 13:48:56 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 55743 <at> debbugs.gnu.org,  juri <at> linkov.net
> Date: Thu, 02 Jun 2022 10:51:25 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > IMO, it's the other way around: any Lisp program that could
> > potentially trigger a subprocess, including compilation, should make
> > sure the default-directory is always valid.
> 
> No, the thing that starts the external process should ensure that it can
> do so.  See `with-existing-directory'.

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.