From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 53739@debbugs.gnu.org, van.ly@sdf.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: Thu, 03 Feb 2022 11:18:47 +0200 [thread overview]
Message-ID: <831r0k5mvc.fsf@gnu.org> (raw)
In-Reply-To: <87o83o7500.fsf@yahoo.com> (message from Po Lu on Thu, 03 Feb 2022 16:01:51 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Van Ly <van.ly@sdf.org>, 53739@debbugs.gnu.org
> Date: Thu, 03 Feb 2022 16:01:51 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I guess the version of 'ls' there is incompatible or something? The
> > message means that 'ls' exited with a non-zero status for some reason.
>
> Yes, Plan 9 from User Space (which provides the ports of Plan 9
> utilities to Unix-like systems) provides an ls binary that is
> incompatible with what Emacs expects.
>
> > Please investigate more what went wrong there and report here the
> > details, so we could decide whether we want to support "plan9/bin"
> > idiosyncrasies, whatever they are.
>
> It would be a great deal of trouble to support their version of ls (and
> indeed, their versions of many other common Unix utilities such as `rm'
> and `cp'), so I think the answer is simply "don't run Emacs with
> plan9/bin at the head of your PATH".
Can you tell more about the incompatibilities, perhaps by comparing
the output of their 'ls' with a compatible one?
Thanks.
next prev parent reply other threads:[~2022-02-03 9:18 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 [this message]
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
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
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=831r0k5mvc.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 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).