unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: renke.vonseggern@gmx.de, 59023-done@debbugs.gnu.org
Subject: bug#59023: 26.1; Setting find-name-arg to -regex breaks dired-do-find-regexp and dired-do-find-regexp-and-replace
Date: Mon, 14 Nov 2022 02:27:54 +0200	[thread overview]
Message-ID: <55003e2f-fb32-3eaf-4b35-8fff38417d12@yandex.ru> (raw)
In-Reply-To: <Y2VKs0JWgW13oZXO@laptop03>

Hi!

On 04.11.2022 20:01, renke.vonseggern@gmx.de wrote:
> Steps to reproduce:
> 1. Create a file containing the string "hello".
> 2. Set the variable "find-name-arg" to "-regex" via Easy Customization.
> 3. Visit the directory containing the file created in step 1 in dired.
> 4. Mark the file created in step 1 in dired.
> 5a. Execute "dired-do-find-regexp" on the marked file by pressing "A"
>      and enter "hello" in the prompt.
>      => Function reports "user-error: No matches for: hello" but I
>         expected it to open an "*xref*" buffer listing the file created
>         in step 1.
> 5b. Execute "dired-do-find-regexp-and-replace" on the marked file by
>      pressing "Q", enter "hello" in the first prompt and an arbitrary
>      replacement string in the second prompt.
>      => Function reports "user-error: No matches for: hello" but I
>         expected it to open the file created in step 1 with the option to
>         replace "hello" with the replacement string.

Thanks for the report. It seems we shouldn't use the customized value in 
project--files-in-directory, just the base value.

I've pushed the fix to master, it should appear in GNU ELPA soon as 
well, in 'project' version 0.8.3.





      reply	other threads:[~2022-11-14  0:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 18:01 bug#59023: 26.1; Setting find-name-arg to -regex breaks dired-do-find-regexp and dired-do-find-regexp-and-replace renke.vonseggern
2022-11-14  0:27 ` Dmitry Gutov [this message]

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=55003e2f-fb32-3eaf-4b35-8fff38417d12@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=59023-done@debbugs.gnu.org \
    --cc=renke.vonseggern@gmx.de \
    /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).