From: Juri Linkov <juri@linkov.net>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 21176@debbugs.gnu.org
Subject: bug#21176: 25.0.50; Garbage in the header line of *Occur* buffers
Date: Sun, 02 Aug 2015 23:34:02 +0300 [thread overview]
Message-ID: <87lhdtsbil.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAH8Pv0ifTmBG-PYKXzw1CMLWj0qsEFR3KsMsuZmd9VHgT2WBrw@mail.gmail.com> (Dani Moncayo's message of "Sat, 1 Aug 2015 17:01:12 +0200")
> 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).
Also you could try ‘M-s w text M-s o’ and see:
1 match for "\<text\>" in buffer: *scratch*
where the search regexp includes additional \<...\>, etc.
What do you expect 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.
Maybe the Occur header should be the same as Isearch message,
but this requires closer integration between Isearch and Occur.
next prev parent reply other threads:[~2015-08-02 20:34 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
2015-08-02 20:34 ` Juri Linkov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhdtsbil.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=21176@debbugs.gnu.org \
--cc=dmoncayo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.