From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21176@debbugs.gnu.org
Subject: bug#21176: 25.0.50; Garbage in the header line of *Occur* buffers
Date: Sat, 1 Aug 2015 17:01:12 +0200 [thread overview]
Message-ID: <CAH8Pv0ifTmBG-PYKXzw1CMLWj0qsEFR3KsMsuZmd9VHgT2WBrw@mail.gmail.com> (raw)
In-Reply-To: <83oairuoqg.fsf@gnu.org>
On Sat, Aug 1, 2015 at 3:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 1 Aug 2015 14:57:49 +0200
>> From: Dani Moncayo <dmoncayo@gmail.com>
>> Cc: 21176@debbugs.gnu.org
>>
>> > But it didn't search for "e", it searched for the regexp that is
>> > shown.
>>
>> Yes, the regexp. I suspected that, and I still made the bug report,
>> because IMO, a user who makes a simple (non-regexp) Isearch doesn't
>> care about the implementation details such as the internal regexp used
>> to perform the actual search. Therefore, in that sense it is garbage.
>>
>> Showing that long string there is plain ridiculous, IMO.
>
> Would you also submit a bug report if one of the matches was è or ĕ or
> ⓔ?
Yes, I would, because the _search string_ (i.e. the string supplied by
the user to search for) was just "e", not a regexp.
The fact that "è", "ĕ" or "ⓔ" can be matches in this case is due to
the combination of (a) the search string, _plus_ (b) the current
Isearch options (char-fold enabled in this case).
So, the header line of *Occur* buffers could perhaps show, in addition
to the search string, some Isearch options -- like the Isearch prompt
string does. But showing that huge, auto-generated regexp in place of
the original search string makes little sense, IMO.
--
Dani Moncayo
next prev parent reply other threads:[~2015-08-01 15:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 12:22 bug#21176: 25.0.50; Garbage in the header line of *Occur* buffers Dani Moncayo
2015-08-01 12:44 ` Eli Zaretskii
2015-08-01 12:57 ` Dani Moncayo
2015-08-01 13:23 ` Eli Zaretskii
2015-08-01 15:01 ` Dani Moncayo [this message]
2015-08-02 20:34 ` Juri Linkov
2015-08-03 6:41 ` Dani Moncayo
2015-08-03 21:49 ` Stefan Monnier
2015-10-10 7:56 ` Dani Moncayo
2015-10-11 0:40 ` Glenn Morris
2015-10-12 20:21 ` Juri Linkov
2015-10-12 21:05 ` Dani Moncayo
2015-10-13 22:05 ` Juri Linkov
2015-10-13 22:25 ` Dani Moncayo
2015-10-14 16:09 ` Juri Linkov
2015-08-04 12:05 ` Angelo Graziosi
2015-08-04 12:32 ` Alexis
2015-08-04 12:44 ` Dani Moncayo
2015-08-04 12:50 ` Dani Moncayo
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=CAH8Pv0ifTmBG-PYKXzw1CMLWj0qsEFR3KsMsuZmd9VHgT2WBrw@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=21176@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).