From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 43702@debbugs.gnu.org
Subject: bug#43702: Emacs master: Incorrect highlighting in regexp isearch.
Date: Tue, 29 Sep 2020 15:33:55 +0000 [thread overview]
Message-ID: <20200929153355.GB27007@ACM> (raw)
In-Reply-To: <83wo0ck5ig.fsf@gnu.org>
Hello, Eli.
On Tue, Sep 29, 2020 at 17:43:35 +0300, Eli Zaretskii wrote:
> > Date: Tue, 29 Sep 2020 12:13:17 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: acm@muc.de
> > In the Emacs master branch
> > (i) emacs -Q
> > (ii) C-x C-f emacs/src/syntax.c<CR>
> > (iii) C-M-s \(inc\|dec\)_both
> > (iv) Press C-s a few times.
> > Notice that the highlighting of the found match has the purple
> > background over the correct characters, but the characters displayed in
> > the foreground are " _both". This incorrect display is a bug.
> Here, I don't see any incorrect display, I see a new feature at work.
> If you don't like it, set search-highlight-submatches to nil.
Ah. I wasn't aware of this new feature.
> How many colors do you have on the terminal where you see the problem?
16. The problem was that the submatch highlight was light magenta on
dark magenta, which I just didn't see. Maybe the colours used for
isearch-group-1 on a 16 colour terminal are suboptimal. They certainly
don't work well on my Linux virtual tty.
However, on pressing backspace to go back to previous matches, this new
highlighting is no longer there.
So, perhaps there is/are (a) bug(s) here after all, just not the one I
thought I'd found.
Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-09-29 15:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 12:13 bug#43702: Emacs master: Incorrect highlighting in regexp isearch Alan Mackenzie
2020-09-29 14:43 ` Eli Zaretskii
2020-09-29 15:33 ` Alan Mackenzie [this message]
2020-09-29 16:07 ` Eli Zaretskii
2020-09-30 2:08 ` Lars Ingebrigtsen
2020-09-30 19:16 ` Juri Linkov
2020-09-30 21:28 ` Drew Adams
2020-10-01 19:11 ` Juri Linkov
2020-10-01 19:38 ` Drew Adams
2020-10-01 22:41 ` Drew Adams
2020-10-06 20:01 ` Juri Linkov
2020-10-06 22:40 ` Drew Adams
2020-10-07 8:13 ` Juri Linkov
2020-10-07 15:42 ` Drew Adams
2020-10-12 19:59 ` Juri Linkov
2020-10-12 23:07 ` Drew Adams
2020-10-13 20:14 ` Juri Linkov
2020-10-13 20:54 ` Drew Adams
2020-10-14 8:57 ` Juri Linkov
2020-10-14 17:03 ` Drew Adams
2020-10-07 7:16 ` Eli Zaretskii
2020-10-07 8:09 ` Juri Linkov
2020-10-07 9:14 ` Eli Zaretskii
2020-10-07 19:09 ` Juri Linkov
2020-10-07 20:02 ` Drew Adams
2020-10-07 20:22 ` Juri Linkov
2020-10-07 20:56 ` Drew Adams
2020-10-01 1:12 ` Lars Ingebrigtsen
2020-10-01 19:20 ` Juri Linkov
2020-10-01 19:23 ` Lars Ingebrigtsen
2020-10-01 19:26 ` Eli Zaretskii
2020-10-01 19:39 ` Drew Adams
2020-10-02 6:57 ` Juri Linkov
2020-10-06 20:17 ` Juri Linkov
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=20200929153355.GB27007@ACM \
--to=acm@muc.de \
--cc=43702@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).