all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55743@debbugs.gnu.org
Subject: bug#55743: 28.1.50; No directory error in comp-run-async-workers
Date: Wed, 01 Jun 2022 09:13:14 +0300	[thread overview]
Message-ID: <861qw97x41.fsf@mail.linkov.net> (raw)
In-Reply-To: <83leuhgljn.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Jun 2022 05:33:16 +0300")

>> >> and why comp-run-async-workers tries to run a process in such arbitrary invalid dirs.
>> >
>> > It is not comp-run-async-workers that does it, it's the low-level
>> > infrastructure in subroutines of make-process: it makes sure the
>> > directory in which the process will run is valid, and if it isn't
>> > signals an error.
>>
>> Shouldn't native compilation run in the directory where the emacs
>> source files are located instead of running in the default directory
>> of an arbitrary buffer that might be invalid?
>
> No, because native compilation could be invoked to compile a file that
> has nothing to do with the Emacs source tree, e.g., some file of the
> user or some 3rd-party package installed in some arbitrary place.

Still, shouldn't it run compilation in the same directory
where that file is located?  Isn't this better than running
compilation in a random dir from a random buffer?





  reply	other threads:[~2022-06-01  6:13 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861qw97x41.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=55743@debbugs.gnu.org \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.