| 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: Old regexp engine does not match pattern with backref correctly.
(Dominique Pelle)
Solution: Fix setting status. Test multi-line patterns better.
|
|
Problem: Compiler warning for unitialized variable. (Tony Mechelynck)
Solution: Set the length to the matching backref.
|
|
Problem: Backreference to previous line doesn't work. (Lech Lorens)
Solution: Implement looking in another line.
|
|
Problem: New regexp engine: Matching plain text could be faster.
Solution: Detect a plain text match and handle it specifically. Add
vim_regfree().
|
|
Problem: Crash when debugging regexp.
Solution: Do not try to dump subexpr that were not set. Skip over count of
\% items.
|
|
Problem: Now that the NFA engine handles everything every failure is a
syntax error.
Solution: Remove the syntax_error flag.
|
|
Problem: No error for using empty \%[].
Solution: Give error message.
|
|
Problem: Crash when regexp logging is enabled.
Solution: Avoid using NULL pointers. Advance over count argument.
|
|
Problem: Flags in 'cpo' are search for several times.
Solution: Store the result and re-use the flags.
|
|
Problem: New regexp engine: \%'m not supported.
Solution: Implement \%'m. Add tests.
|
|
Problem: New regexp engine: \%V not supported.
Solution: Implement \%V. Add tests.
|
|
Problem: Compiler warnings for unused variables.
Solution: Put the variables inside #ifdef.
|
|
Problem: New regexp engine: no error when using \z1 or \z( where it does
not work.
Solution: Give an error message.
|
|
Problem: New regexp engine: \@<= and \@<! are not implemented.
Solution: Implement look-behind matching. Fix off-by-one error in old
regexp engine.
|
|
Problem: A leading star is not seen as a normal char when \{} follows.
Solution: Save and restore the parse state properly.
|
|
Problem: Look-behind matching is very slow on long lines.
Solution: Add a byte limit to how far back an attempt is made.
|
|
Problem: Typo in char value causes out of bounds access.
Solution: Fix character value. (Klemens Baum)
|
|
Problem: In the old regexp engine \i, \I, \f and \F don't work on
multi-byte characters.
Solution: Dereference pointer properly.
|
|
Problem: Regexp debug logs don't have a good name.
Solution: Use clear names and make it possible to write logs for the old and
new engines separately. (Taro Muraoka)
|
|
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)
|
|
Problem: Cannot easily use :s to make title case.
Solution: Have "\L\u" result in title case. (James McCoy)
|
|
Problem: "\@<!" in regexp does not work correctly with multi-byte
characters, especially cp932.
Solution: Move column to start of multi-byte character. (Yasuhiro Matsumoto)
|
|
Problem: "/[^\n]" does match at a line break.
Solution: Make it do the same as "/.". (Christian Brabandt)
|
|
Problem: "\k" in regexp does not work in other window.
Solution: Use the right buffer. (Yukihiro Nakadaira)
|
|
Problem: Crash with specific use of search pattern.
Solution: Initialize reg_buf to curbuf.
|
|
Problem: ml_get error when searching, caused by curwin not matching curbuf.
Solution: Avoid changing curbuf. (Lech Lorens)
|
|
Problem: Equivalence classes only work for latin characters.
Solution: Add the Unicode equivalence characters. (Dominique Pelle)
|
|
Problem: Using "\n" in a substitute inside ":s" does not result in a line
break.
Solution: Change behavior inside vim_regexec_nl(). Add tests. (Motoya
Kurotsu)
|
|
Problem: Crash when using very long regexp. (Peter Odding)
Solution: Reset reg_toolong. (Carlo Teubner)
|
|
|
|
|
|
Problem: When "\\\n" appears in the expression result the \n doesn't result
in a line break. (Andy Wokula)
Solution: Also replace a \n after a backslash into \r.
|
|
Problem: When using an expression in ":s" backslashes in the result are
dropped. (Sergey Goldgaber, Christian Brabandt)
Solution: Double backslashes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
