From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 71321@debbugs.gnu.org
Subject: bug#71321: 30.0.50; M-x grep: not recognizing well files with colon
Date: Sun, 02 Jun 2024 13:02:14 +0300 [thread overview]
Message-ID: <86v82rmzmh.fsf@gnu.org> (raw)
In-Reply-To: <87y17rty4s.fsf@lco2.mail-host-address-is-not-set> (message from Jean Louis on Thu, 30 May 2024 13:03:31 +0300)
> From: Jean Louis <bugs@gnu.support>
> Date: Thu, 30 May 2024 13:03:31 +0300
>
> I have files like:
>
> ~/tmp/2024-05-17-10:39:33-RCD TEMPORARY BUFFER.txt
>
> and if I do M-x grep on those files, I get results such as:
>
> 2024-01-22-11:39:12-RCD TEMPORARY BUFFER.txt:13:| | TOTAL | -57000 |
> 2024-05-17-10:39:33-RCD TEMPORARY BUFFER.txt:3:|------------+-------------------------------+---------|
> 2024-05-17-10:39:33-RCD TEMPORARY BUFFER.txt:4:| Date | Description | Amount |
> 2024-05-17-10:39:33-RCD TEMPORARY BUFFER.txt:5:|------------+-------------------------------+---------|
> 2024-05-17-10:39:33-RCD TEMPORARY BUFFER.txt:6:| 2024-05-09 | Exchange US $1000 | 3759000 |
>
> Where by when I try to click on the file, it is attempting to find wrong
> file "2024-05-17-10" instead of "2024-05-17-10:39:33-RCD TEMPORARY
> BUFFER.txt" so I guess that regular expression of finding the file in
> *grep* temporary buffer shall be improved.
Improved how? Can you suggest how to distinguish between ":39:" and
":13:" in the Grep output, when searching where the file name ends and
the line number and the following test starts?
Do the problems go away if you use "M-x occur" instead? If so,
perhaps that's a better solution for such file names.
next prev parent reply other threads:[~2024-06-02 10:02 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 [this message]
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
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=86v82rmzmh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71321@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).