From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: luangruo@yahoo.com, 53739@debbugs.gnu.org
Subject: bug#53739: 28.0.91; "C-x d" fails when "emacs -Q" starts on NetBSD with plan9/bin on head of PATH
Date: Fri, 04 Feb 2022 13:50:15 +0200 [thread overview]
Message-ID: <83o83m3l6w.fsf@gnu.org> (raw)
In-Reply-To: <654b7fa8-6d12-289-b036-923f58eebfb6@SDF.ORG> (message from Van Ly on Fri, 4 Feb 2022 08:59:11 +0000 (UTC))
> Date: Fri, 4 Feb 2022 08:59:11 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: Po Lu <luangruo@yahoo.com>, 53739@debbugs.gnu.org
>
> On Fri, 4 Feb 2022, Eli Zaretskii wrote:
>
> >
> > The problem, as I explained up-thread, seems to be that 'ls' returns a
> > non-zero exit status, which insert-directory takes as a sign that the
> > directory listing didn't work.
>
> The "9 man intro" page has this paragraph containing the "exit" keyword.
>
> '''
> DIAGNOSTICS
> In Plan 9, a program's exit status is an arbitrary text
> string, while on Unix it is an integer. Section (1) of this
> manual describes commands as though they exit with string
> statuses. In fact, exiting with an empty status corresponds
> to exiting with status 0, and exiting with any non-empty
> string corresponds to exiting with status 1. See exits(3).
> '''
>
> >
> > So: what does "ls -l" return as exit status when using the plan9
> > variant of 'ls'?
> >
>
> Starting 'emacs -Q' at the end of this typescript reproduces the problem.
>
> '''
> ; on GNU/Linux
> % echo $SHELL
> /usr/bin/zsh
> % PATH=/usr/local/plan9/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export PATH
> % echo $PATH
> /usr/van/.opam/cs3110-2-21fa/bin:/usr/local/plan9/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
> % which ls
> /usr/local/plan9/bin/ls
> % ls -l
> --rw-r--r-- M 0 van dialout 46 Feb 4 18:22 emacs28
> --rw-r--r-- M 0 van dialout 47 Feb 4 18:14 emacs28q
> % echo $?
> 0
> % /usr/local/plan9/bin/ls -l
> --rw-r--r-- M 0 van dialout 46 Feb 4 18:22 emacs28
> --rw-r--r-- M 0 van dialout 47 Feb 4 18:14 emacs28q
> % echo $?
> 0
Thanks, but we need to know what Emacs sees as the exit status inside
insert-directory. So, as I already said, the best approach top
investigating this is to step with Edebug through the code in
insert-directory, and see what kind of exit status we receive there,
and why we decide that "directory listing failed".
next prev parent reply other threads:[~2022-02-04 11:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 22:12 bug#53739: 28.0.91; "C-x d" fails when "emacs -Q" starts on NetBSD with plan9/bin on head of PATH Van Ly
2022-02-03 7:22 ` Eli Zaretskii
2022-02-03 8:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 9:18 ` Eli Zaretskii
2022-02-03 10:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 10:31 ` Eli Zaretskii
2022-02-03 11:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 11:08 ` Eli Zaretskii
2022-02-03 11:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 13:20 ` Van Ly
2022-02-03 16:47 ` Eli Zaretskii
2022-02-03 13:12 ` Van Ly
2022-02-03 16:47 ` Eli Zaretskii
2022-02-04 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 4:29 ` Van Ly
2022-02-04 4:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 7:18 ` Van Ly
2022-02-04 7:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 8:05 ` Eli Zaretskii
2022-02-04 8:59 ` Van Ly
2022-02-04 9:26 ` Van Ly
2022-02-04 11:52 ` Eli Zaretskii
2022-02-05 3:07 ` Van Ly
2022-02-05 7:37 ` Eli Zaretskii
2022-02-05 9:04 ` Van Ly
2022-02-05 9:19 ` Eli Zaretskii
2022-02-05 10:57 ` Van Ly
2022-02-05 21:57 ` Lars Ingebrigtsen
2022-02-04 11:50 ` Eli Zaretskii [this message]
2022-02-03 13:05 ` Van Ly
2022-02-03 16:45 ` Eli Zaretskii
2022-02-03 13:00 ` Van Ly
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=83o83m3l6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53739@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=van.ly@sdf.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.