unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20195@debbugs.gnu.org
Subject: bug#20195: 25.0.50; Let Dired commands such as `dired-do-search' (`A') use prefix arg
Date: Wed, 25 Mar 2015 23:50:52 +0200	[thread overview]
Message-ID: <87619oiw5f.fsf@mail.linkov.net> (raw)
In-Reply-To: <3126891c-8c4d-4d6f-aa97-7c2e5b4ed2d0@default> (Drew Adams's message of "Tue, 24 Mar 2015 20:56:26 -0700 (PDT)")

> Enhancement request:
>
> Typically in Dired commands that act on the marked files will act on the
> next PREFIX-ARG files instead, if a prefix arg is provided.  This is not
> true of commands such as `dired-do-search', but it would be good if it
> were.
>
> All that is needed is to (a) add an optional argument ARG to each such
> command and (b) include ARG in the call to `dired-get-marked-files'.
> For example:
>
> (defun dired-do-search (regexp &optional arg) ; <=== Add ARG
>   "..."
>   (interactive "sSearch marked files (regexp): \nP")
>   (tags-search
>     regexp (dired-get-marked-files nil arg 'dired-nondirectory-p)))
>                                         ^
>                                         |
>                                      use ARG

There is a problem with `dired-do-query-replace-regexp' where a prefix arg
means replace word-delimited matches.





  reply	other threads:[~2015-03-25 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  3:56 bug#20195: 25.0.50; Let Dired commands such as `dired-do-search' (`A') use prefix arg Drew Adams
2015-03-25 21:50 ` Juri Linkov [this message]
2015-03-25 23:08   ` Drew Adams
2015-03-31 20:33     ` Juri Linkov
2015-03-31 21:22       ` Drew Adams
2015-03-31 21:54         ` Filipp Gunbin
2015-04-01  0:36           ` Drew Adams
2015-04-02 13:32             ` Filipp Gunbin
2015-04-02 14:01               ` Drew Adams
2022-02-03 21:19       ` Lars Ingebrigtsen

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=87619oiw5f.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=20195@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).