From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 63744@debbugs.gnu.org, sdl.web@gmail.com
Subject: bug#63744: 28.2; fix dired-guess-default
Date: Tue, 30 May 2023 05:36:11 +0300 [thread overview]
Message-ID: <83353eh7fo.fsf@gnu.org> (raw)
In-Reply-To: <87pm6i4qfa.fsf@web.de> (message from Michael Heerdegen on Tue, 30 May 2023 02:24:25 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Leo Liu <sdl.web@gmail.com>, 63744@debbugs.gnu.org
> Date: Tue, 30 May 2023 02:24:25 +0200
>
> then you meant to recompute the variable's value every time the user wants
> to open a file with dired?
No, every time the situation changes in a way that requires its
recomputation. I don't have a clear idea when that happens, but if
the REGEXP part is ".", it is clear to me it happens quite often
already, since the list of commands for a given file depends on the
file, and "." does not.
> It's a defcustom so Emacs should not change the value at all.
We are talking about user customizations. A user can make his/her
customizations change the value as often as needed.
> And recomputing the whole value every time is much slower than computing
> a list of defaults for one class of files matched by the regexp.
That is not Leo's use case, AFAICT: the list of commands is
dynamically recomputed when needed anyway.
> The conditions that need to be checked are very different for
> different file types in a typical scenario, and the suggested design
> is more efficient: first look at the file type by matching the RE
> part, then decide, at the moment of user request, what applications
> are appropriate for this type of file (and only for this type) in
> this moment.
Like I said: I'm not against extending the value to support this, I
just don't see how this could be considered an urgent bugfix that must
be done in Emacs 29, that's all.
next prev parent reply other threads:[~2023-05-30 2:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 4:10 bug#63744: 28.2; fix dired-guess-default Leo Liu
2023-05-27 6:49 ` Eli Zaretskii
2023-05-28 2:40 ` Leo Liu
2023-05-28 6:27 ` Eli Zaretskii
2023-05-29 1:23 ` Michael Heerdegen
2023-05-29 3:49 ` Leo Liu
2023-05-29 12:38 ` Eli Zaretskii
2023-05-30 0:04 ` Michael Heerdegen
2023-05-29 12:07 ` Eli Zaretskii
2023-05-29 18:20 ` Leo Liu
2023-05-29 18:27 ` Eli Zaretskii
2023-05-30 0:24 ` Michael Heerdegen
2023-05-30 2:36 ` Eli Zaretskii [this message]
2023-06-02 0:14 ` Michael Heerdegen
2023-06-02 4:28 ` Leo Liu
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=83353eh7fo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63744@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=sdl.web@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).