From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55743@debbugs.gnu.org, juri@linkov.net
Subject: bug#55743: 28.1.50; No directory error in comp-run-async-workers
Date: Thu, 02 Jun 2022 13:48:56 +0300 [thread overview]
Message-ID: <838rqffihz.fsf@gnu.org> (raw)
In-Reply-To: <878rqf30tu.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 02 Jun 2022 10:51:25 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 55743@debbugs.gnu.org, juri@linkov.net
> Date: Thu, 02 Jun 2022 10:51:25 +0200
>
> Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2022-06-02 10:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 17:31 bug#55743: 28.1.50; No directory error in comp-run-async-workers Juri Linkov
2022-05-31 19:07 ` Eli Zaretskii
2022-05-31 19:49 ` Juri Linkov
2022-06-01 2:33 ` Eli Zaretskii
2022-06-01 6:13 ` Juri Linkov
2022-06-01 11:16 ` Eli Zaretskii
2022-06-01 19:13 ` Juri Linkov
2022-06-01 19:49 ` Eli Zaretskii
2022-06-02 7:40 ` Juri Linkov
2022-06-02 8:02 ` Eli Zaretskii
2022-06-02 8:17 ` Lars Ingebrigtsen
2022-06-02 8:44 ` Eli Zaretskii
2022-06-02 8:51 ` Lars Ingebrigtsen
2022-06-02 10:48 ` Eli Zaretskii [this message]
2022-06-03 3:10 ` Lars Ingebrigtsen
2022-06-03 5:55 ` Eli Zaretskii
2022-06-03 8:22 ` Andreas Schwab
2022-06-03 11:43 ` Eli Zaretskii
2022-06-02 8:17 ` Andreas Schwab
2022-06-02 8:45 ` Eli Zaretskii
2022-06-02 17:30 ` Juri Linkov
2022-06-02 19:02 ` Eli Zaretskii
2022-06-03 7:49 ` Juri Linkov
2022-06-03 11:12 ` Eli Zaretskii
2022-06-01 6:10 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rqffihz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55743@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).