From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 22097@debbugs.gnu.org
Subject: bug#22097: Ispell: lazy highlighting doesn't work properly.
Date: Sat, 05 Dec 2015 16:20:38 +0200 [thread overview]
Message-ID: <83d1ulf03t.fsf@gnu.org> (raw)
In-Reply-To: <20151205140609.GB2698@acm.fritz.box>
> Date: Sat, 5 Dec 2015 14:06:09 +0000
> Cc: 22097@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > This is a "feature". Ispell skips regions determined by certain
> > regexps, see ispell-skip-region-alist. In this case, the ASCII-art
> > diagram around the second occurrence of "xdisp" includes regions that
> > match some of the regexps (AFAICT, the '+' character followed and
> > preceded by '-' triggers that). Lazy highlight doesn't want to try
> > matching in those skip-regions, and since it cannot support
> > non-contiguous regions, it simply limits itself to the beginning of
> > the first such region, which happens to be before the second "xdisp".
>
> Ah. I didn't know this.
Neither did I. I just traced through the code, is all.
> However, the bug manifests itself a bit later on in plain text.
>
> There's a paragraph starting at L199 about bidi. After several more
> hits on the space bar, the first occurrence of "bidi" (L201) gets
> highlighted; the second occurrence (on the same line) gets lazily
> highlighted. The third (L204) and fourth (L205) remain unhighlighted.
>
> Hit the spacebar another time. All four occurrences are now
> highlighted.
>
> As far as I can see, there's nothing remotely ASCII-arty in that
> paragraph. Unless the "---" sequences are somehow being interpreted as
> ASCII-art.
ispell-skip-region-alist is a complex regexp, something there must've
(mis)fired.
next prev parent reply other threads:[~2015-12-05 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 11:42 bug#22097: Ispell: lazy highlighting doesn't work properly Alan Mackenzie
2015-12-05 13:23 ` Eli Zaretskii
2015-12-05 14:06 ` Alan Mackenzie
2015-12-05 14:20 ` Eli Zaretskii [this message]
2015-12-05 16:04 ` Alan Mackenzie
2015-12-05 16:47 ` Eli Zaretskii
2015-12-05 23:04 ` Juri Linkov
2015-12-08 0:47 ` Juri Linkov
2015-12-09 21:59 ` Alan Mackenzie
2020-09-07 16:34 ` Lars Ingebrigtsen
2015-12-10 0:04 ` Juri Linkov
2015-12-10 16:08 ` Alan Mackenzie
2015-12-11 22:45 ` 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=83d1ulf03t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22097@debbugs.gnu.org \
--cc=acm@muc.de \
/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).