From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 64791@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#64791: 30.0.50; [PATCH] Fix dired mismatch on some filenames
Date: Sun, 03 Sep 2023 14:44:38 +0300 [thread overview]
Message-ID: <83pm2z7a6x.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm9ByKe+C1asqfFLkSjSqV_nmUr0gDK-bW_BARqV6mFEQ@mail.gmail.com> (message from Stefan Kangas on Sun, 3 Sep 2023 04:34:38 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 3 Sep 2023 04:34:38 -0700
> Cc: Manuel Giraud <manuel@ledu-giraud.fr>, 64791@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Manuel Giraud <manuel@ledu-giraud.fr>
> >> Cc: 64791@debbugs.gnu.org
> >> Date: Sat, 22 Jul 2023 16:46:27 +0200
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> > I'm not sure there can be the end to such fixes. The real fix is to
> >> > use GNU 'ls' which has special support for Dired (or use ls-lisp.el).
> >> > I guess you don't have GNU 'ls', since you are on OpenBSD?
>
> Yup. Perhaps we should consider checking for the existence of "gls" and
> using that. E.g., I use the following, here:
>
> (if (and (memq system-type '(berkeley-unix darwin))
> (executable-find "gls"))
> (setq insert-directory-program "gls"))
>
> But I've only tested this on macOS so far, so I'm not sure how well this
> would work on *BSD. From memory, I think it should be fine. Perhaps
> Manuel can say what he thinks.
>
> >> You're right I'm using OpenBSD's ls. But I thought it was a reasonable
> >> fix: it seems more obvious then looking for something that looked like a
> >> file size.
> >
> > Maybe. Let's hear what others think about this.
>
> FWIW, I don't think I mind such portability fixes. It wouldn't be a bad
> thing if Dired played a bit more nicely on BSD machines.
>
> The point that this could be a slippery slope is valid, but we can also
> choose to reject further tweaks on a case-by-case basis. The format of
> ls is also inherently stable: many things depend on it.
>
> On the other hand, the fix I propose above might be all that is needed
> in many cases.
I'm still undecided. And it doesn't help that none of *BSD users
except you spoke up.
next prev parent reply other threads:[~2023-09-03 11:44 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 [this message]
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
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=83pm2z7a6x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64791@debbugs.gnu.org \
--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).