-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12-Nov-2017 15:03 +0100, Nazri Ramliy wrote:
> On Sun, Nov 12, 2017 at 8:34 PM, Tony Mechelynck 
> <[email protected]> wrote:
>> The way I see it, there was a bug before (which you used as an 
>> undocumented feature), now the bug has been fixed, and you're 
>> complaining. The way your pattern is written, it _ought_ to
>> match everywhere, though in the case of its last branch it is a
>> zero-length match. There was a patch recently about search
>> highlighting… let me see… « 8.0.1250  'hlsearch' highlighting not
>> removed after incsearch ». Maybe that was what changed the
>> behaviour?
> 
> Perhaps. But I find it hard to accept the "undocumented feature"
> part. To compare the regular expression behavior of GNU grep:
> 
> $ echo foobar | grep --color=always -E 'foo|' foobar ^^^ only 'foo'
> is highlighted here, which is similar to how vim behaved before
> this, but not recently.
> 
> The current vim behavior now seems to say "empty pattern match 
> anything, so that's why everything gets highlighted" which feels 
> wrong. Empty pattern should not match anything, that's what the
> '.' atom is for, isn't it?.

No, 8.0.1250 was about incsearch artifacts in other windows. I think
the "undocumented feature" is that incsearch now highlights all
matches (8.0.1238: incremental search only shows one match), not just
the next one. Previously, an empty branch would just match a single
character under the cursor (so just one screen cell would be colored /
the cursor would re-appear with IncSearch color); now, _every_
character gets highlighted.

Though technically correct (an empty branch matches anywhere), this
indeed is irritating with the new incsearch behavior. Even when typing
the search pattern quickly, the whole buffer will suddenly "light up".
A special case would be nice: If a pattern matches anywhere (like the
empty branch), do not apply any incsearch highlighting at all.

- -- regards, ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJaCHu7AAoJEA7ziXlAzQ/vOZEH/2FybJkov3nImu7hgQaYtybf
jrKuYeInOqhN7oFIEE5/lCbPpFcYoTNln+x9U0hDJN5nbOQVC/SvRXW//QXmN4mL
IuhR5pnhhdxgTaIK9SHFXrzHmzhXp1SRu1j+VrPJjlC27MSrdkehuaUV+rjw32qB
J0W0rzA8Sd3pj4umqoaUvYKVjbmoDkoAgDCfMr1k/ty0GJ1TXKENaB5899siw7N1
K2w5HG17sHUuT72cfCRCOIpTvV+6rWT4Olf0H1Pj7V2EPSO7t94yFyAjFmqvI/rs
HU1b3WRdn+W0LtR+XP1KY2TL8suBWTXsi78FimOyhY3qn46ehfJtbsfdOuxBatc=
=ssw8
-----END PGP SIGNATURE-----

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui