GNU bug report logs -
#77121
[PATCH] Make isearch highlight overlays non-sticky (non-advance) at both ends
Previous Next
Reported by: Sora Takai <SoraTakai <at> protonmail.com>
Date: Wed, 19 Mar 2025 16:56:03 UTC
Severity: normal
Tags: patch
Merged with 77120
Fixed in version 31.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Sorry, here is an updated patch. I think this is enough since it is for the most part lazy-highlights with (setq isearch-lazy-highlight t) and (setq lazy-highlight-cleanup nil) that matter for editing.
On Wednesday, March 19th, 2025 at 11:10 PM, Sora Takai <SoraTakai <at> protonmail.com> wrote:
> Tags: patch
>
> Hi,
>
> here is a simple patch to make isearch highlights non-sticky at both ends (i.e. no front and rear advance on overlays), thereby making them more intuitive and less bothersome for further editing. Currently, every isearch overlay, including lazy highlights, inherits isearch highlight color when you type characters at front and rear positions. By applying this patch, users will no longer get that color stickiness when editing around isearch highlights, which makes them more 'self-contained'.
>
> (This is the first time I am submitting a patch to this community - apologies in advance if I am not following the conventions in some way.)
[Message part 2 (text/html, inline)]
[0001-Make-isearch-lazy-highlights-non-sticky-at-both-ends.patch (application/octet-stream, attachment)]
This bug report was last modified 86 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.