unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#52367: 27.2; lgrep and grep-files-aliases
@ 2021-12-08  0:54 Maxence Dutielt
  2021-12-08  2:33 ` Óscar Fuentes
  2021-12-08 12:41 ` Eli Zaretskii
  0 siblings, 2 replies; 6+ messages in thread
From: Maxence Dutielt @ 2021-12-08  0:54 UTC (permalink / raw)
  To: 52367; +Cc: ofv

emacs -Q
M-x lgrep
Search for: foo
Search for "foo" in files matching wildcard (default all): all
In directory: ~/foobar

will always output this error if you don't have any filename starting
with two dots:

grep: ..?*: No such file or directory
Grep exited abnormally with code 2

I noticed "..?*" was introduced here:
commit ref: 856cd948d1a5a016ad36721246a049d33451902f
after reviewing bug #22577 (archived):
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22577

Now that Emacs is smarter at quoting shell commands (at least on 27.2),
"* .[!.]* ..?*" seems overcomplicated and no longer necessary.

I couldn't reproduce bug #22577 with vc-git-grep as mentioned, using
both BSD and GNU grep on Linux, Windows and macOS.

Since "* .*" works as expected again, and doesn't produce the error of
"..?*", I think it should be reverted back into grep-files-aliases.

Lastly, to avoid such messages when using lgrep:

grep: foobar: Is a directory

We could add the parameter --directories=skip by default, since lgrep is
not for recursive search.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-12-08 22:58 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-08  0:54 bug#52367: 27.2; lgrep and grep-files-aliases Maxence Dutielt
2021-12-08  2:33 ` Óscar Fuentes
2021-12-08 12:40   ` Eli Zaretskii
2021-12-08 22:58     ` Óscar Fuentes
2021-12-08 12:41 ` Eli Zaretskii
2021-12-08 16:54   ` Maxence Dutielt

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).