From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 48071-done@debbugs.gnu.org, Boruch Baum <boruch_baum@gmx.com>
Subject: bug#48071: 28.0.50: dired-guess-default: comply with docstring options [PATCH]
Date: Thu, 22 Jul 2021 14:10:08 +0200 [thread overview]
Message-ID: <87eebqmtwf.fsf@gnus.org> (raw)
In-Reply-To: <87k0lj8cwr.fsf@web.de> (Michael Heerdegen's message of "Thu, 22 Jul 2021 01:28:36 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> So the (only) remaining user visible change is that now all matching
> entries are considered instead of only the first one, which is actually
> a fix: the docstring of `dired-guess-shell-alist-user' describes it
> should work like that.
Well... does it? It's pretty vague on the issue. And the comments
seem to contradict that:
;; * Parse `dired-guess-shell-alist-user' and
;; `dired-guess-shell-alist-default' (in that order) for the first REGEXP
;; that matches the first file in the file list.
;;
;; * If the REGEXP matches all the entries of the file list then evaluate
;; COMMAND, which is either a string or a Lisp expression returning a
;; string. COMMAND may be a list of commands.
;;
;; * Return this command to `dired-guess-shell-command' which prompts user
;; with it. The list of commands is put into the list of default values.
;; If a command is used successfully then it is stored permanently in
;; `dired-shell-command-history'.
But this is pretty nonsensical -- it describes how the function what
implemented, but not really what to do when the rest of the files don't
match, or when more of them match "the first file".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-22 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 18:53 bug#48071: 28.0.50: dired-guess-default: comply with docstring options [PATCH] Boruch Baum
2021-07-20 14:17 ` Lars Ingebrigtsen
2021-07-21 1:53 ` Michael Heerdegen
2021-07-21 2:16 ` Michael Heerdegen
2021-07-21 11:04 ` Lars Ingebrigtsen
2021-07-21 23:28 ` Michael Heerdegen
2021-07-22 3:28 ` Michael Heerdegen
2021-07-22 12:18 ` Lars Ingebrigtsen
2021-07-22 23:21 ` Michael Heerdegen
2021-07-23 13:04 ` Lars Ingebrigtsen
2021-07-22 12:10 ` Lars Ingebrigtsen [this message]
2021-07-21 11:12 ` Lars Ingebrigtsen
2021-07-21 23:22 ` Michael Heerdegen
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=87eebqmtwf.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48071-done@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=michael_heerdegen@web.de \
/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).