From: Eli Zaretskii <eliz@gnu.org>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: 62004@debbugs.gnu.org, akrl@sdf.org
Subject: bug#62004: 30.0.50; comp-run-async-workers failure when default-directory deleted
Date: Mon, 06 Mar 2023 22:10:19 +0200 [thread overview]
Message-ID: <83jzzt7iac.fsf@gnu.org> (raw)
In-Reply-To: <87v8jdww42.fsf@gmail.com> (message from No Wayman on Mon, 06 Mar 2023 13:46:39 -0500)
> From: No Wayman <iarchivedmywholelife@gmail.com>
> Cc: akrl@sdf.org, 62004@debbugs.gnu.org
> Date: Mon, 06 Mar 2023 13:46:39 -0500
>
> The example I gave used the emacs-lisp-native-compile-and-load
> directly because it is the simplest way to reproduce the error.
> The same error can happen if the jit native compilation kicks in
> (because an entirely different feature is loaded but needs to be
> jit compiled) while in the buffer which no longer has a file
> associated with it.
Sorry, I don't think I understand. Are you saying that we don't bind
default-directory to a safe value when compiling? IOW, how could a
directory where the async compilation subprocess runs become invalid,
in Real Life?
next prev parent reply other threads:[~2023-03-06 20:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:48 bug#62004: 30.0.50; comp-run-async-workers failure when default-directory deleted No Wayman
2023-03-06 16:49 ` Eli Zaretskii
2023-03-06 17:20 ` No Wayman
2023-03-06 18:31 ` Eli Zaretskii
2023-03-06 18:46 ` No Wayman
2023-03-06 20:10 ` Eli Zaretskii [this message]
2023-03-06 21:29 ` No Wayman
2023-03-07 3:30 ` Eli Zaretskii
[not found] ` <xjfo7p4vmjr.fsf@ma.sdf.org>
2023-03-07 13:17 ` Eli Zaretskii
2023-03-07 13:51 ` Andrea Corallo
2023-03-07 14:16 ` Eli Zaretskii
2023-03-07 15:20 ` No Wayman
2023-03-07 15:53 ` No Wayman
2023-03-07 16:06 ` Andrea Corallo
2023-03-07 16:14 ` Eli Zaretskii
2023-03-07 16:30 ` No Wayman
2023-03-08 20:19 ` Andrea Corallo
2023-03-08 20:51 ` No Wayman
2023-03-09 9:25 ` Andrea Corallo
2023-03-07 16:00 ` Andrea Corallo
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=83jzzt7iac.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62004@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=iarchivedmywholelife@gmail.com \
/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.