aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/regexp_nfa.c
Commit message (Collapse)AuthorAge
...
* Remove has_mbyte from lines near changes in parent commitZviRackover2018-08-16
|
* Remove occurences of mb_head_offZviRackover2018-08-15
|
* lintJan Edmund Lazo2018-08-12
|
* vim-patch:8.0.1397: pattern with \& following nothing gives an errorJan Edmund Lazo2018-08-12
| | | | | | Problem: Pattern with \& following nothing gives an error. Solution: Emit an empty node when needed. https://github.com/vim/vim/commit/890dd05492d88d48eee1dda7f7a1811d027ce7ca
* lintJan Edmund Lazo2018-08-11
|
* vim-patch:8.1.0099: exclamation mark in error message not neededJan Edmund Lazo2018-08-11
| | | | | | Problem: Exclamation mark in error message not needed. Solution: Remove the exclamation mark. https://github.com/vim/vim/commit/3c867daaf09e8ac6ce4b9d43d6fbbfdd7689702d
* vim-patch:8.1.0097: superfluous space before exclamation markJan Edmund Lazo2018-08-11
| | | | | | Problem: Superfluous space before exclamation mark. Solution: Remove the space. Don't translate debug message. https://github.com/vim/vim/commit/5efa0102de6ed6049fb19e1e83787e5b3b24b6a2
* vim-patch:8.1.0090: "..." used inconsistently in a messageJan Edmund Lazo2018-08-11
| | | | | | Problem: "..." used inconsistently in a message. Solution: Define the message with " ..." once. (hint by Ken Takata) https://github.com/vim/vim/commit/9b0c5c23bd5260caef82a4f3dcc945c129857c52
* vim-patch:8.1.0078: "..." used inconsistently in messagesJan Edmund Lazo2018-08-11
| | | | | | Problem: "..." used inconsistently in messages. Solution: Drop the space before " ...". https://github.com/vim/vim/commit/c166927a32fe5c054ad35deecff00aa12c629cf7
* vim-patch:8.0.1470: integer overflow when using regexp patternJan Edmund Lazo2018-08-11
| | | | | | Problem: Integer overflow when using regexp pattern. (geeknik) Solution: Use a long instead of int. (Christian Brabandt, closes vim/vim#2251) https://github.com/vim/vim/commit/2c7b906afb86b986476cfc959732e433b1b4a3b1
* vim-patch:8.0.1254: undefined left shift in gethexchrs()Jan Edmund Lazo2018-08-11
| | | | | | Problem: Undefined left shift in gethexchrs(). (geeknik) Solution: Use unsigned long. (idea by Christian Brabandt, closes vim/vim#2255) https://github.com/vim/vim/commit/4c22a91d20cce4f28dd2852a13129b5a4cc691da
* vim-patch:8.0.0828: Coverity: may dereference NULL pointerJan Edmund Lazo2018-08-11
| | | | | | Problem: Coverity: may dereference NULL pointer. Solution: Bail out if calloc_state() returns NULL. https://github.com/vim/vim/commit/983b3a5bc44a91cc7e40b8e71e3bfdb03dd4606f
* style: fixing minor issues noted in code review.ZviRackover2018-08-06
|
* Remove some occrrences of enc_utf8 and has_mbyteZviRackover2018-08-06
| | | | | Removing uses and related dead code in the locallity of changes of the two parent commits.
* Remove all occurences of the mb_ptr2char macroZviRackover2018-08-06
| | | | | | | First step towards implemening issue #7401. The same can be done for all deprecated mb_ functions in follow-up patches.
* vim-patch:8.0.0451: some macros are in lower caseJan Edmund Lazo2018-06-12
| | | | | | | Problem: Some macros are in lower case. Solution: Make a few more macros upper case. Avoid lower case macros use an argument twice. https://github.com/vim/vim/commit/91acfffc1e6c0d8c2abfb186a0e79a5bf19c3f3f
* vim-patch:8.0.0520: using a function pointer while the function is known (#8513)KunMing Xie2018-06-10
| | | | | | | Problem: Using a function pointer instead of the actual function, which we know. Solution: Change mb_ functions to utf_ functions when already checked for Unicode. (Dominique Pelle, closes vim/vim#1582) https://github.com/vim/vim/commit/ace95989ed81929a84e205b26d0972cb9d6b4b19
* lintJan Edmund Lazo2018-06-04
|
* vim-patch:8.0.0623: error for invalid regexp is not very informativeJan Edmund Lazo2018-06-04
| | | | | | Problem: The message "Invalid range" is used for multiple errors. Solution: Add two more specific error messages. (Itchyny, Ken Hamada) https://github.com/vim/vim/commit/966e58e413ffa88af8d748e697aa2999571fcd7b
* vim-patch:8.0.0519: character classes not well tested (#8460)KunMing Xie2018-06-01
| | | | | | | | | Problem: Character classes are not well tested. They can differ between platforms. Solution: Add tests. In the documentation make clear which classes depend on what library function. Only use :cntrl: and :graph: for ASCII. (Kazunobu Kuriyama, Dominique Pelle, closes vim/vim#1560) Update the documentation. https://github.com/vim/vim/commit/0c078fc7db2902d4ccba04506db082ddbef45a8c
* regexp_nfa: Silence PVS/V560: current code is more obviousZyX2018-04-22
| | | | | While warning is technically true (cannot enter this case with `state->c` greater then NFA_Z…9) it makes condition less readable and relies on knownledge of enum internal structure.
* lintJames McCoy2018-01-02
|
* vim-patch:8.0.0160: EMSG() is sometimes used where it should be IEMSG()James McCoy2018-01-02
| | | | | | | Problem: EMSG() is sometimes used for internal errors. Solution: Change them to IEMSG(). (Dominique Pelle) And a few more. https://github.com/vim/vim/commit/de33011ec623fd562419dede6bf465b5b9881a20
* vim-patch:8.0.0165 (#7132)KunMing Xie2017-08-10
| | | | | | Problem: Ubsan warns for integer overflow. Solution: Swap two conditions. (Dominique Pelle) https://github.com/vim/vim/commit/f446b48ff0bffae2b453cd4f9e3c25dfe363d29d
* vim-patch:8.0.0020Jurica Bradaric2017-07-29
| | | | | | | Problem: The regexp engines are not reentrant. Solution: Add regexec_T and save/restore the state when needed. https://github.com/vim/vim/commit/6100d02aab7c8294b581cb299250eea164b50e9d
* vim-patch:7.4.2354Shougo Matsushita2017-07-12
| | | | | | | | Problem: The example that explains nested backreferences does not work properly with the new regexp engine. (Harm te Hennepe) Solution: Also save the end position when adding a state. (closes vim/vim#990) https://github.com/vim/vim/commit/d563883a1fb5ec6cf4a2758c5e36ac1ff4e9bb3d
* regexp_nfa: Fix invalid fallthrough in character class detectionJames McCoy2017-05-12
| | | | | | | | | When the end character in a range matches a different standard range (e.g., [0-z]), the range would be incorrectly detected as the class of the end character (CLASS_az). Instead of using a fallthrough, immediately FAIL when the end character doesn't match the expected range.
* *: Comment intentional fallthroughsJames McCoy2017-05-12
| | | | | Falling through a switch case should be commented so it's clear that behavior is intentional.
* Merge #6460 from ZyX-I/1476-changesJustin M. Keyes2017-05-08
|\ | | | | Refactor functions which find character in a string
| * Merge branch 'master' into 1476-changesZyX2017-04-10
| |\
| * | strings: Remove vim_strbyteZyX2017-04-07
| | | | | | | | | | | | Ref #1476
* | | *: Add comment to all C filesZyX2017-04-19
| | |
* | | regexp_nfa: Remove octal constantZyX2017-04-16
| | |
* | | regexp_nfa: Remove another has_mbyte/…-checking codeZyX2017-04-16
| |/ |/|
* | lint: fix clint errors around mb_tolower callsBjörn Linse2017-04-10
| |
* | mbyte: replace vim_tolower with mb_tolower handling locale correctlyBjörn Linse2017-04-10
|/
* eval: Split eval.c into smaller filesZyX2017-03-29
|
* vim-patch:7.4.2355Justin M. Keyes2017-03-22
| | | | | | | | Problem: Regexp fails to match when using "\>\)\?". (Ramel) Solution: When a state is already in the list, but addstate_here() is used and the existing state comes later, add the new state anyway. https://github.com/vim/vim/commit/16b3578f355282846f2600ce77fb344950f0b9ce
* vim-patch:7.4.1793Michael Ennen2016-12-31
| | | | | | | | Problem: Some character classes may differ between systems. On OS/X the regexp test fails. Solution: Make this less dependent on the system. (idea by Kazunobu Kuriyama) https://github.com/vim/vim/commit/e8aee7dcf9b12becff86e8ce1783a86801c5f9f6
* vim-patch:7.4.1708James McCoy2016-12-06
| | | | | | | | | | | Problem: New regexp engine does not work properly with EBCDIC. Solution: Define equivalence class characters. (Owen Leibman) https://github.com/vim/vim/commit/2a6fa564a3b5061c14ff63b8b0f12801df0b0ac2 Although nvim doesn't support EBCDIC systems, this keeps us inline with upstream code so its easier to merge future patches in this area and improves the readability of the code.
* vim-patch:7.4.1967Michael Ennen2016-11-02
| | | | | | | | | | Problem: Falling back from NFA to old regexp engine does not work properly. (fritzophrenic) Solution: Do not restore nfa_match. (Christian Brabandt, closes vim/vim#867) https://github.com/vim/vim/commit/6747fabc7348bf5f41ccfe851e2be3e900ec8ee0 Helped-by: jamessan
* refactor: eliminate misc2.cJustin M. Keyes2016-09-13
| | | | | | | | | | move `call_shell` to misc1.c Move some fns to state.c Move some fns to option.c Move some fns to memline.c Move `vim_chdir*` fns to file_search.c Move some fns to new module, bytes.c Move some fns to fileio.c
* lint: Close resource leak (#5288)Patrick Jackson2016-09-03
|
* vim-patch:7.4.1305 #5094Michael Ennen2016-08-01
| | | | | | | | | | Problem: "\%1l^#.*" does not match on a line starting with "#". Solution: Do not clear the start-of-line flag. (Christian Brabandt) https://github.com/vim/vim/commit/7c29f387819b5817b003d2ba73e2b5cf3cb3d0dd Helped-by: jamessan Helped-by: mhinz
* *: Also fix the adjacent errorsZyX2016-06-11
|
* *: Fix errors from new linter checksZyX2016-06-11
|
* *: Fix new linter errorsZyX2016-05-01
| | | | Originally there were 128 new errors, so I thought this is a good idea to fix all of them. Of course, this commit also fixes many suppressed errors.
* regexp_nfa.c: Fix various linter errorsJames McCoy2016-04-25
|
* vim-patch:7.4.613James McCoy2016-04-25
| | | | | | | Problem: The NFA engine does not implement the 'redrawtime' time limit. Solution: Implement the time limit. https://github.com/vim/vim/commit/70781ee4035b5fd5e3cbb3fe4c7646e19119f0a8
* vim-patch:7.4.937watiko2016-02-17
| | | | | | | | Problem: Segfault reading unitialized memory. Solution: Do not read match \z0, it does not exist. (Marius Gedminas, closes vim/vim#497) https://github.com/vim/vim/commit/5ad075c0735d3d8b97708d17c22de8facb15f997
generated by cgit (git 2.34.1) at 2025-06-07 12:18:09 +0000