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: Sat, 05 Feb 2022 09:37:00 +0200 [thread overview]
Message-ID: <831r0h3gtf.fsf@gnu.org> (raw)
In-Reply-To: <81de2e66-99d7-29f-40b8-e9454ae77ae1@SDF.ORG> (message from Van Ly on Sat, 5 Feb 2022 03:07:07 +0000 (UTC))
> Date: Sat, 5 Feb 2022 03:07:07 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: luangruo@yahoo.com, 53739@debbugs.gnu.org
>
> The "result" exit status is "1" on line 7512 closing parenthesises.
>
> The call is "ls -al -- /usr/X" and the problem is Plan's ls doesn't
> take the "-a" switch. For example
>
> '''
> % ls -a
> usage: ls [-dlmnpqrstuFQ] [file ...]
> % echo $?
> 1
> % ls -al
> usage: ls [-dlmnpqrstuFQ] [file ...]
> % echo $?
> 1
> '''
Thanks, the problem is clear now.
> The Edebug steps continue to line 7581.
>
> lisp/files.el:7581
> "Listing directory failed but `access-file' worked"
>
> In the case of Plan9's ls what is needed is to leave out the "-a" switch.
Which means "C-u C-x d" should fix your use case nicely. You can also
customize dired-listing-switches in your init file, if you intend to
use this version of 'ls' routinely. It's a defcustom for this very
reason.
Bottom line: I think we can close this bug with no further action.
next prev parent reply other threads:[~2022-02-05 7:37 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 [this message]
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=831r0h3gtf.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).