unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 27456@debbugs.gnu.org, darkfeline@felesatra.moe
Subject: bug#27456: 25.2; Not possible to use -prune with find-dired
Date: Sun, 09 Sep 2018 07:32:19 +0200	[thread overview]
Message-ID: <87in3fi6cc.fsf@web.de> (raw)
In-Reply-To: <4a51546f-d4b6-739e-5cc2-55c5f5694b33@orcon.net.nz> (Phil Sainty's message of "Sun, 9 Sep 2018 17:22:21 +1200")

Phil Sainty <psainty@orcon.net.nz> writes:

> Despite that, I think it would be useful and consistent for
> `find-dired' to acquire the prefix argument behaviour of `rgrep':
>
> > With C-u prefix, you can edit the constructed shell command line
> > before it is executed.
> > With two C-u prefixes, directly edit and run `grep-find-command'.
>
> This would give some users a more familiar solution to the problem
> if they are not used to the particular find options needed to work
> around the problem (which was the situation I found myself in just
> the other day, so the new activity on this bug was very timely :)

Yes, that could be useful.  Do you want to provide a patch, or can you
open a new bug report with the feature request?


Thanks,

Michael.





  reply	other threads:[~2018-09-09  5:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  6:00 bug#27456: 25.2; Not possible to use -prune with find-dired Allen Li
2017-07-12 19:40 ` Michael Heerdegen
2017-07-13  6:56   ` Allen Li
2017-07-19  0:21     ` Michael Heerdegen
2017-07-13  7:32 ` Andreas Schwab
2018-09-09  0:35 ` Allen Li
2018-09-09  2:39   ` Michael Heerdegen
2018-09-09  5:22     ` Phil Sainty
2018-09-09  5:32       ` Michael Heerdegen [this message]
2018-09-09  9:38         ` Phil Sainty
2018-09-09 11:49           ` Phil Sainty
2018-09-09 14:04           ` bug#32668: " 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=87in3fi6cc.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=27456@debbugs.gnu.org \
    --cc=darkfeline@felesatra.moe \
    --cc=psainty@orcon.net.nz \
    /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).