unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "63875@debbugs.gnu.org" <63875@debbugs.gnu.org>
Subject: bug#63875: 26.3; Doc of `dired-guess-shell-alist-user'
Date: Sat, 3 Jun 2023 16:21:55 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488C446362AD6A3CB5C3254F34FA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83zg5g7c7j.fsf@gnu.org>

> > The doc string doesn't say what REGEXP is, e.g., what it's intended to
> > match.  It should say that up front and explicitly.
> 
> ???The doc string says:
> 
>   Each element of this list looks like
> 
>       (REGEXP COMMAND...)
> 
>   COMMAND will be used if REGEXP matches the file to be processed.
>   If several files are to be processed, REGEXP has to match all the
>   files.
> 
> "REGEXP matches the file to be processed".  What else needs to be
> said?

Apologies.  The bug report was from Emacs 26.  I see
now that the doc string was improved since then to
what you quote.

In Emacs 26, it says only this:

 Each element of this list looks like

     (REGEXP COMMAND...)

 where each COMMAND can either be a string or a Lisp
 expression that evaluates to a string.

Feel free to close the bug.  Thx.






  reply	other threads:[~2023-06-03 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 16:08 bug#63875: 26.3; Doc of `dired-guess-shell-alist-user' Drew Adams
2023-06-03 16:14 ` Drew Adams
2023-06-04 16:44   ` Juri Linkov
2023-06-03 16:16 ` Eli Zaretskii
2023-06-03 16:21   ` Drew Adams [this message]
2023-06-03 16:24     ` Eli Zaretskii
2023-06-03 16:26     ` Drew Adams
2023-06-03 16:29       ` Eli Zaretskii
2023-06-03 17:20         ` Drew Adams
2023-06-03 18:50           ` Eli Zaretskii
2023-06-03 19:29             ` Drew Adams

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=SJ0PR10MB5488C446362AD6A3CB5C3254F34FA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=63875@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).