all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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: Mon, 04 Sep 2023 15:17:07 +0300	[thread overview]
Message-ID: <83edje5e0s.fsf@gnu.org> (raw)
In-Reply-To: <83wmx75aad.fsf@gnu.org> (message from Eli Zaretskii on Sun, 03 Sep 2023 22:25:30 +0300)

> Cc: 64791@debbugs.gnu.org, manuel@ledu-giraud.fr
> Date: Sun, 03 Sep 2023 22:25:30 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > -(defvar insert-directory-program (purecopy "ls")
> > +(defvar insert-directory-program
> > +  (if (and (memq system-type '(berkeley-unix darwin))
> > +           (executable-find "gls"))
> > +      (purecopy "gls")
> > +    (purecopy "ls"))
> >    "Absolute or relative name of the `ls'-like program.
> >  This is used by `insert-directory' and `dired-insert-directory'
> >  \(thus, also by `dired').")
> 
> If we believe "gls" is the only popular name, I guess that's good
> enough.

Actually, I take this back: this defvar will be computed when files.el
is loaded, which is at dump time.  So this is not TRT, since the
conditions and the environment at dump time could be very different
from those at run time.  It could be even on another machine.

So I once again suggest to make this a defcustom.  This has two
advantages:

 . it will be evaluated at Emacs startup, not at dump time
 . it will allow users to customize the value and thus avoid costly
   search  for the program and prevent finding the wrong version of
   'ls'





  parent reply	other threads:[~2023-09-04 12:17 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
2023-09-05 21:57                           ` Stefan Kangas
2023-09-04 12:17                   ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83edje5e0s.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 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.