From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
64791@debbugs.gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
Subject: bug#64791: 30.0.50; [PATCH] Fix dired mismatch on some filenames
Date: Tue, 05 Sep 2023 08:20:29 +0800 [thread overview]
Message-ID: <s0dmsy1v5bm.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmKoLTwKHKnFu0QUaF3fpCow2a04MQcCVFUs1GiueRo9w@mail.gmail.com> (Stefan Kangas's message of "Mon, 4 Sep 2023 12:22:58 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> I doubt anyone would make install GNU coreutils on top of a BSD
> userland, because there would be no end to the breakage that would
> create. That's the exact reason why the 'popular name' on BSD is
> "gls".
???
GNU ls is a compatible replacement for Unix ls, the installation of
which shouldn't produce problems on Unix systems. I've been installing
it from the coreutils tarball since it was still named fileutils,
without any ill effect.
>> Favoring `gls' over `ls' will lead to Emacs overlooking a
>> potentially
>> newer Coreutils installation as long as one from the package manager
>> is already present.
>
> I don't think I understand what situation you have in mind here.
Where /usr/local/bin/gls is older than another installation of
coreutils.
next prev parent reply other threads:[~2023-09-05 0:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 13:22 bug#64791: 30.0.50; [PATCH] Fix dired mismatch on some filenames Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-22 13:50 ` Eli Zaretskii
2023-07-22 14:46 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-22 15:24 ` Eli Zaretskii
2023-09-03 11:34 ` Stefan Kangas
2023-09-03 11:44 ` Eli Zaretskii
2023-09-03 14:04 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 18:18 ` Stefan Kangas
2023-09-03 18:24 ` Eli Zaretskii
2023-09-03 18:54 ` Stefan Kangas
2023-09-03 19:25 ` Eli Zaretskii
2023-09-04 7:57 ` Stefan Kangas
2023-09-04 8:05 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 8:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 8:36 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 19:22 ` Stefan Kangas
2023-09-05 0:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-05 21:57 ` Stefan Kangas
2023-09-04 12:17 ` Eli Zaretskii
2023-09-05 22:27 ` Stefan Kangas
2023-09-05 22:43 ` Stefan Kangas
2023-09-06 11:28 ` Eli Zaretskii
2023-09-24 12:34 ` Stefan Kangas
2023-09-24 15:32 ` Eli Zaretskii
2023-09-25 9:39 ` Stefan Kangas
2023-09-24 15:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 15:56 ` Stefan Kangas
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=s0dmsy1v5bm.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64791@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
--cc=stefankangas@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).