all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Jim Porter <jporterbugs@gmail.com>, 66806@debbugs.gnu.org
Subject: bug#66806: 30.0.50; [PATCH] 'project-find-regexp' passes Git submodules to the search program
Date: Mon, 30 Oct 2023 00:02:48 +0200	[thread overview]
Message-ID: <3c9c9b20-fe67-4665-5664-13c974bd9eb4@gutov.dev> (raw)
In-Reply-To: <cd8d3fe8-4d9e-7d08-951a-45d7c301a060@gmail.com>

On 29/10/2023 07:36, Jim Porter wrote:
> (Looking at the definition for ripgrep, I'm guessing the "-g '!*/'" is 
> the trick for that program, but nothing similar works for ag.)

Actually, it's a failed solution which I copied from the rg's issue 
tracker but I didn't test it enough or it broke in some later versions, 
and then I put off dealing with it when finally noticed. Maybe it never 
worked and only could filter out directories when those are passed with 
a trailing slash.

What should work, is adding the argument "--max-depth 0" (stopping the 
traversal of passed directories). For ag, the corresponding fix seems to 
be "--depth 0", but I haven't tested that in practice.

Anyway, see the other email, which should make it all unnecessary 
(unless you have a 3rd party package which has to work with older 
project.el too).





  parent reply	other threads:[~2023-10-29 22:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29  5:36 bug#66806: 30.0.50; [PATCH] 'project-find-regexp' passes Git submodules to the search program Jim Porter
2023-10-29  6:06 ` Eli Zaretskii
2023-10-29 17:54   ` Jim Porter
2023-10-29 19:22     ` Eli Zaretskii
2023-10-29 22:14   ` Dmitry Gutov
2023-10-29 21:41 ` Dmitry Gutov
2023-10-30  0:58   ` Jim Porter
2023-10-30  2:00     ` Dmitry Gutov
2023-10-30  3:53       ` Jim Porter
2023-10-29 22:02 ` Dmitry Gutov [this message]
2023-10-30  0:25   ` Jim Porter

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3c9c9b20-fe67-4665-5664-13c974bd9eb4@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=66806@debbugs.gnu.org \
    --cc=jporterbugs@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.