unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 06 Sep 2023 14:28:58 +0300	[thread overview]
Message-ID: <83ledj35hh.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm9x7WbM7CGSx6L3G2foCEhtgKqP4MjPGhjE35AR9Arww@mail.gmail.com> (message from Stefan Kangas on Tue, 5 Sep 2023 15:43:21 -0700)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 5 Sep 2023 15:43:21 -0700
> Cc: 64791@debbugs.gnu.org, manuel@ledu-giraud.fr
> 
> Stefan Kangas <stefankangas@gmail.com> writes:
> 
> >> 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
> >
> > Agreed.  Let's change it into a defcustom.
> >
> >>  . it will allow users to customize the value and thus avoid costly
> >>    search  for the program and prevent finding the wrong version of
> >>    'ls'
> >
> > Perhaps this part is okay though, given that the search should only
> > affect users on macOS and *BSD (who presumably will want this anyways)?
> >
> > Proposed patch attached.
> 
> This doesn't work either, as it's also evaluated at dump time.

I thought it should be evaluated at dump time _and_ at startup time.
Was I misremembering?

> I guess we'd have to set it in something like `normal-top-level'.

We have a machinery for delaying the initialization to startup time:
custom-initialize-delay.





  reply	other threads:[~2023-09-06 11:28 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
2023-09-05 22:27                     ` Stefan Kangas
2023-09-05 22:43                       ` Stefan Kangas
2023-09-06 11:28                         ` Eli Zaretskii [this message]
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=83ledj35hh.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).