unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Allen Li <darkfeline@felesatra.moe>
Cc: 27456@debbugs.gnu.org
Subject: bug#27456: 25.2; Not possible to use -prune with find-dired
Date: Wed, 12 Jul 2017 21:40:24 +0200	[thread overview]
Message-ID: <874luhxx3r.fsf@drachen> (raw)
In-Reply-To: <87k243qm3z.fsf@felesatra.moe> (Allen Li's message of "Thu, 22 Jun 2017 23:00:48 -0700")

Hi Allen,

> It is not possible to effectively use the -prune action with
> find-dired.

I think I can use it successfully.

> With plain find, -prune would be used like:
>
>     find . -name "foo*" -prune -o -name "*.el" -ls
>
> However, find-dired wraps everything:
>
>     (find-dired "." "-name \\"foo*\\" -prune -o -name \\"*.el\\" -ls")

I get an error when I try to eval this.  I think the backslashes should
not be doubled.

> results in the equivalent call:
>
>     find . \( -name "foo*" -prune -o -name "*.el" -ls \) -ls
>
> Notably, this will list files matching foo*

Can't you just leave out the explicit -ls in the arguments?

Also, AFAIK "-prune" is about descending into directories, not about
file names.


Michael.





  reply	other threads:[~2017-07-12 19:40 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 [this message]
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
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=874luhxx3r.fsf@drachen \
    --to=michael_heerdegen@web.de \
    --cc=27456@debbugs.gnu.org \
    --cc=darkfeline@felesatra.moe \
    /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).