From: Eli Zaretskii <eliz@gnu.org>
To: No Wayman <iarchivedmywholelife@gmail.com>,
Andrea Corallo <akrl@sdf.org>
Cc: 62004@debbugs.gnu.org
Subject: bug#62004: 30.0.50; comp-run-async-workers failure when default-directory deleted
Date: Mon, 06 Mar 2023 18:49:09 +0200 [thread overview]
Message-ID: <83sfeh7rlm.fsf@gnu.org> (raw)
In-Reply-To: <874jqxyhfo.fsf@gmail.com> (message from No Wayman on Mon, 06 Mar 2023 10:48:58 -0500)
> From: No Wayman <iarchivedmywholelife@gmail.com>
> Date: Mon, 06 Mar 2023 10:48:58 -0500
>
>
> A corner case I've recently run into with comp-run-async-workers:
>
> 1. create a non-empty elisp file at /tmp/dir/test.el
> 2. visit /tmp/dir/test.el
> 3. delete /tmp/dir/
> 4. from within the test.el buffer `M-x
> emacs-lisp-native-compile-and-load`
>
> The process will fail with:
>
> > /tmp/dir/test.el: Opening input file, No such file or directory,
> > /tmp/dir/test.el
>
> A similar edge case is accounted for when the buffer has no
> associated file.
> e.g. attempting emacs-lisp-native-compile-and-load from the
> *scratch* buffer results in the user error:
>
> > The buffer must be saved in a file first.
>
> Perhaps a similar check should be made in the case described
> above.
That's not the same check: the latter checks whether the buffer visits
a file, which in the former case is true.
I'm not sure we should do anything here: after all, the error message
tells what's wrong quite clearly. Andrea, WDYT?
next prev parent reply other threads:[~2023-03-06 16:49 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 [this message]
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
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
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=83sfeh7rlm.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 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).