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

Previous Next

Full log

Message #65 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: Fri, 03 Jun 2022 08:55:31 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 55743 <at> debbugs.gnu.org,  juri <at> linkov.net
> Date: Fri, 03 Jun 2022 05:10:36 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> 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?

Previous Next

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