From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63744@debbugs.gnu.org, Leo Liu <sdl.web@gmail.com>
Subject: bug#63744: 28.2; fix dired-guess-default
Date: Tue, 30 May 2023 02:24:25 +0200 [thread overview]
Message-ID: <87pm6i4qfa.fsf@web.de> (raw)
In-Reply-To: <834jnvgfh2.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 May 2023 21:27:53 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I understand all that. But you are evidently still not understanding
> what I'm asking.
If interested - else feel free to ignore.
If this didn't answer your question:
> Can't you generate the entire value of dired-guess-shell-alist-user
> dynamically, including the RE part?
then you meant to recompute the variable's value every time the user wants
to open a file with dired?
It's a defcustom so Emacs should not change the value at all.
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. 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.
Michael.
next prev parent reply other threads:[~2023-05-30 0:24 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 [this message]
2023-05-30 2:36 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm6i4qfa.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=63744@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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.