| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Error while typing :/foo/s// with 'incsearch' enabled.
Solution: Do not give search errors when highlighting matches.
https://github.com/vim/vim/commit/50eb16c3b23235b21ce4494673a7741a9a196176
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Using :s with 'incsearch' prevents CTRL-R CTRL-W. (Boris Staletic)
Solution: When past the pattern put cursor back in the start position.
(closes vim/vim#3413)
https://github.com/vim/vim/commit/99f043a57d0be35ef72572b0429cf51525c3cd2b
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' for :/foo/s//<Esc> changes last search pattern.
Solution: Save the last search pattern earlier.
https://github.com/vim/vim/commit/198cb66d652d3d8ac16226dcc929a11b0b720151
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Wrong highlight when 'incsearch' set and cancelling :s.
Solution: Reset search line range. (Hirohito Higashi, Masamichi Abe)
https://github.com/vim/vim/commit/f13daa46da85a80dd05704cdde0660c2b2651a5a
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' regression: /\v highlights everything.
Solution: Put back the empty_pattern() check.
https://github.com/vim/vim/commit/4edfe2d2a2d70ea66a7f73e9b923c2d1f6246a57
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Too much 'incsearch' highlight for pattern matching everything.
Solution: Add the skiplen to the command and remove the line range.
(Christian Brabandt) Check for empty pattern earlier.
https://github.com/vim/vim/commit/8b0d5ce881ac16a36ea00018ba13a58b0fdb7534
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Command parsing for 'incsearch' is a bit ugly.
Solution: Return when there is no pattern. Put common checks together.
https://github.com/vim/vim/commit/111bbd61e96d1d3ee4bc07ae435fd97b88413aba
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: No 'incsearch' highlighting for :vimgrep and similar commands.
Solution: Parse the :vimgrep command and similar ones to locate the search
pattern. (Hirohito Higashi, closes vim/vim#3344)
https://github.com/vim/vim/commit/264cf5cfaf40e704aea2578e70c15ed9a9d0161e
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' highlighting not used for :sort.
Solution: Handle pattern in :sort command.
https://github.com/vim/vim/commit/81f56536b1bc324eb173924a8cf4d7dbbf4f3fdb
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' does not apply to :smagic and :snomagic.
Solution: Add support. (Hirohito Higashi)
https://github.com/vim/vim/commit/167ae42685dcd430800c51ac7339f7f0938a3e70
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'cursorline' highlighting wrong with 'incsearch'.
Solution: Move the cursor back if the match is outside the range.
https://github.com/vim/vim/commit/2f6a346a4cd2d5bdd6dc9b3209ebce7b6340221d
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' does not work with command modifiers.
Solution: Skip command modifiers.
https://github.com/vim/vim/commit/33c4dbb74bdf41aadd193a704f597d4df20f0e47
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Parsing command modifiers is not separated.
Solution: Move command modifier parsing to a separate function.
https://github.com/vim/vim/commit/effed9315c6c5a35fc2824b90da4af753c7a02dc
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' highlighting does not work for ":g!/".
Solution: Skip the exclamation mark. (Hirohito Higashi)
https://github.com/vim/vim/commit/def7b1dc6104a6ce6d7c3e3a615231178601b124
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' highlighting does not skip white space.
Solution: Skip white space after the command. (issue vim/vim#3321)
https://github.com/vim/vim/commit/2b926fcb3c5d8bd09a219009336bbec7c66ae67e
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' highlighting does not accept reverse range.
Solution: Swap the range when needed. (issue vim/vim#3321)
https://github.com/vim/vim/commit/60d0871000e9abf3716ee035cba5b5a9d659e327
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' highlighting wrong in a few cases.
Solution: Fix using last search pattern. Restore highlighting when changing
command. (issue vim/vim#3321)
https://github.com/vim/vim/commit/c7f08b7ee1c1ff2080d425c2fcdb6907c26fc98e
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' with :s doesn't start at cursor line.
Solution: Set cursor before parsing address. (closes vim/vim#3318)
Also accept a match at the start of the first line.
https://github.com/vim/vim/commit/976b847f43dd16eb6cd809d2dcab7dde6045e176
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' triggers on ":source".
Solution: Check for the whole command name.
https://github.com/vim/vim/commit/21f990e1c22ffa2fdb66a548ebbe25e6e7194776
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Invalid memory access when using 'incsearch'.
Solution: Reset "patlen" when using previous search pattern.
https://github.com/vim/vim/commit/ef73a28401cde680dc0d02d4b0fb19ed659ec1d3
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'incsearch' doesn't work for :s, :g or :v.
Solution: Also use 'incsearch' for other commands that use a pattern.
https://github.com/vim/vim/commit/b0acacd767a2b0618a7f3c08087708f4329580d0
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: The getcmdline() function is way too big.
Solution: Factor out the incremental search highlighting.
https://github.com/vim/vim/commit/0ee81cb63876e6ec1b2a6e0125295b43f1c63c7d
|
| |/
|/| |
|
|\ \
| | |
| | | |
Fix invalid events with `o` `<CR>` and `autoindent`
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a bit of test cleanup
ärrår
feeel
SPLIT
fix: sned correct updates on <CR>
|
|\ \ \
| |/ /
|/| | |
lua: cleanup naming conventions of executor functions
|
|/ / |
|
|\ \
| | |
| | | |
Bytetrack
|
| | |
| | |
| | |
| | | |
This is irrelevant to neovim usecases anyway.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will significantly reduce the parsing work
needed e.g. when rehighlighting after every keypress
in insert mode.
Also add safety check for tree-sitter trying to read
past the end of a line. This can happen after we sent
an incorrect buffer update.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This implements byte-resolution updates of buffer changes.
Note: there is no promise that the buffer state is valid inside
the callback!
|
| | |
| | |
| | |
| | |
| | | |
When editing a line in insert mode, this value will be
used for every keypress.
|
| | | |
|
| | |
| | |
| | |
| | | |
as the byte logic will be the same for all of these
|
|/ /
| |
| |
| |
| | |
* Use upstream git repo as snap source.
* Fix typo in snapcraft.yaml
Use latest_tag instead of branch because branch is undefined.
|
|\ \
| | |
| | | |
treesitter: fix some highlight issues
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Seems like redundant env var separators (";" on Windows) in $PATH can
cause weird behavior. From #7377:
> After some time, system(['win32yank', '-o']) and system('win32yank -o')
> start returning different results: specifically first returns an
> empty string.
>
> 1. $PATH weirdly contains double semicolon followed by path to the
> “installation directory” (unpacked directory from archive).
> 2. If I run `let $PATH=substitute($PATH, ';;', ';', 'g')` the problem is fixed.
close #7377
ref 224f99b85d311ebd31451db13b66e4a3c7e51938
|
| |
| |
| |
| |
| | |
Problem: No digraph for 0x2022 BULLET.
Solution: Use "oo". (Hans Ginzel, closes vim/vim#6904)
https://github.com/vim/vim/commit/57ad94c5a9ee6f3626e1ec728519a8558a4346c8
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Windows environment variables are semicolon-separated, but some logic
was assuming colon (:). This broke initialization and parsing of
XDG_CONFIG_DIRS, XDG_DATA_DIRS, 'runtimepath', stdpath(), etc.
- test/defaults_spec: enable tests on Windows
ref #12793
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Architectures supported by Travis due not match 1 to 1 to the
architectures supported by snapcraft.io and launchpad. To support as
many architectures as possible, deploys to the snap store should be done
via a simulated Github webhook. An additional secret will need to be
added to Travis-ci
|
| | | |
|
| | | |
|
| | | |
|