| Age | Commit message (Collapse) | Author |
|---|
|
Problem: "\p" in a regexp does not match double-width characters.
(Yukihiro Nakadaira)
Solution: Don't count display cells, use vim_isprintc().
|
|
Problem: Searching for composing char only and using \Z has different
results.
Solution: Make it match the composing char, matching everything is not
useful.
|
|
Problem: New regexp engine does not ignore order of composing chars.
Solution: Ignore composing chars order.
|
|
Problem: Not all patterns are tested with auto / old / new engine.
Solution: Test patterns with three values of 'regexpengine'.
|
|
Problem: New regexp engine: Matching composing characters is wrong.
Solution: Fix matching composing characters.
|
|
Problem: \Z does not work properly with the new regexp engine.
Solution: Make \Z work. Add tests.
|
|
Problem: New regexp engine is inefficient with multi-byte characters.
Solution: Handle a character at a time instead of a byte at a time. Also
make \Z partly work.
|
|
Problem: New regexp: adding \Z makes every character match.
Solution: Only apply ireg_icombine for composing characters.
Alsl add missing change from patch 1008. (Ken Takata)
|
|
Problem: Test 95 fails on MS-Windows.
Solution: Set 'nomore'. Change \i to \f. Change multi-byte character to
something that is not matching \i. (Ken Takata)
|
|
Problem: No easy to run an individual test. Tests 64 fails when
'encoding' is not utf-8.
Solution: Add individual test targets to the Makefile. Move some lines from
test 64 to 95.
|
|
Problem: In the new regexp engine \p does not work on multi-byte
characters.
Solution: Don't point to an integer but the characters.
|
|
Problem: Syntax highlighting can be slow.
Solution: Include the NFA regexp engine. Add the 'regexpengine' option to
select which one is used. (various authors, including Ken Takata,
Andrei Aiordachioaie, Russ Cox, Xiaozhou Liua, Ian Young)
|
