From: Jean Louis <bugs@gnu.support>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Jim Porter <jporterbugs@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
71321@debbugs.gnu.org
Subject: bug#71321: 30.0.50; M-x grep: not recognizing well files with colon
Date: Tue, 4 Jun 2024 22:08:32 +0300 [thread overview]
Message-ID: <Zl9mMCP3hJ8fXgAO@lco2> (raw)
In-Reply-To: <3e418ce1-5b78-43a3-9bfa-6ecac92a5488@gutov.dev>
* Dmitry Gutov <dmitry@gutov.dev> [2024-06-04 13:21]:
> On 04/06/2024 07:27, Jean Louis wrote:
> > Actual grep command is this:
> >
> > M-x grep RET
> > grep --color=auto -nH -e '|' *.txt
>
> I guess that means that you changed the command by hand when running 'M-x
> grep'?
Of course, I cannot search without saying what I am searching with the M-x grep command.
> What does the variable grep-command say?
grep-command ➜ "grep --color=auto -nH -e "
> Both grep-command and grep-template are generated in the same place, so if
> one has the --null argument, so should the other.
I did not customize it. Even if I use --null it gives same result.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
✡️🛡️ Proudly standing with Israel, a nation rooted in history and culture. Let's condemn hatred and promote understanding.
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2024-06-04 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 10:03 bug#71321: 30.0.50; M-x grep: not recognizing well files with colon Jean Louis
2024-06-02 10:02 ` Eli Zaretskii
2024-06-03 4:17 ` Jim Porter
2024-06-03 11:43 ` Eli Zaretskii
2024-06-03 12:03 ` Dmitry Gutov
2024-06-04 4:28 ` Jean Louis
2024-06-04 4:27 ` Jean Louis
2024-06-04 10:20 ` Dmitry Gutov
2024-06-04 19:08 ` Jean Louis [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=Zl9mMCP3hJ8fXgAO@lco2 \
--to=bugs@gnu.support \
--cc=71321@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@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 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).