unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 55743@debbugs.gnu.org
Subject: bug#55743: 28.1.50; No directory error in comp-run-async-workers
Date: Tue, 31 May 2022 20:31:36 +0300	[thread overview]
Message-ID: <86y1yhsxin.fsf@mail.linkov.net> (raw)

0. emacs -Q
1. C-x C-f emacs/lisp/s TAB M-v

Then after switching to the Completions window
after a short delay this error is raised:

Debugger entered--Lisp error: (file-missing "Setting current directory" "No such file or directory" "emacs/lisp/s/")
  make-process(:name "Compiling: emacs/lisp/net/goto-addr.el" :buffer #<buffer *Async-native-compile-log*> :command ("emacs/src/emacs" "--batch" "-l" "/tmp/emacs-async-comp-goto-addr-cVqUYL.el") :sentinel #f(compiled-function (process event) #<bytecode -0x812502d31259a48>) :noquery t)
  comp-run-async-workers()
  #f(compiled-function (process event) #<bytecode -0xb3837fe88441506>)(#<process Compiling: emacs/lisp/emacs-lisp/bytecomp.el> "finished\n")
  completing-read-default("Find file: " read-file-name-internal file-exists-p confirm-after-completion "emacs/lisp/" file-name-history "emacs/lisp/" nil)
  read-file-name-default("Find file: " nil "emacs/lisp/" confirm-after-completion nil nil)
  read-file-name("Find file: " nil "emacs/lisp/" confirm-after-completion)
  find-file-read-args("Find file: " confirm-after-completion)
  command-execute(find-file)

This is because default-directory is set in the Completions buffer
to a non-existent "emacs/lisp/s/" from incomplete minibuffer input.
And comp-run-async-workers fails to make a process in that non-existent dir.

So here are two problems: why completion sets default-directory to non-existent dir,
and why comp-run-async-workers tries to run a process in such arbitrary invalid dirs.





             reply	other threads:[~2022-05-31 17:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 17:31 Juri Linkov [this message]
2022-05-31 19:07 ` bug#55743: 28.1.50; No directory error in comp-run-async-workers 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
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=86y1yhsxin.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=55743@debbugs.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 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).