| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| | |
Update runtime files, new color schemes
https://github.com/vim/vim/commit/30ab04e16e1e9e6133590181197b3f8e70cb495e
Skip: doc/* (in-progress rewrite of the user manual on creating vim(9)script plugins)
|
| |
| |
| |
| |
| |
| |
| |
| | |
The formatting for these files were originally disabled as to signal
that "we don't own these files", meaning we intentionally want to
minimize the amount of work put in these files as the return will be
very little. This unfortunately conflicts with other refactoring efforts
that happen to touch these files, and it's easier to simply enable
formatting.
|
|\ \
| | |
| | | |
ci(clint): remove check for include order
|
| | |
| | |
| | |
| | |
| | |
| | | |
Uncrustify and clang-format are already both excellent at ordering
includes; this isn't something we need to check for ourselves. Also
remove the section on include order in the dev-style documentation.
|
|/ / |
|
|\ \
| | |
| | | |
vim-patch:8.2.{4951,4953}: with 'si' inserting char after completion goes wrong
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: With 'smartindent' inserting '}' after completion goes wrong.
Solution: Check the cursor is in indent. (closes vim/vim#10420)
https://github.com/vim/vim/commit/2e444bbef0f36535bf941f007f2961f3f66bbe87
|
|/ /
| |
| |
| |
| |
| | |
Problem: Smart indenting done when not enabled.
Solution: Check option values before setting can_si. (closes vim/vim#10420)
https://github.com/vim/vim/commit/de5cf287812510d2c8ffe66b99cf33c4e1a6e6f1
|
|\ \
| | |
| | | |
refactor(api/nvim_cmd): use `kvec_t` for constructing cmdline string
|
| | |
| | |
| | |
| | | |
Co-authored-by: Björn Linse <bjorn.linse@gmail.com>
|
| | |
| | |
| | | |
Co-authored-by: Sarchia <74000088+Sarchia@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
q in "$MANPAGER mode" does not quit Nvim. This is because
ftplugin/man.vim creates its own mapping:
nnoremap <silent> <buffer> <nowait> q :lclose<CR><C-W>c
which overrides the one set by the autoload file when using :Man!
("$MANPAGER mode")
Solution:
Set b:pager during "$MANPAGER mode" so that ftplugin/man.vim can set the
mapping correctly.
Fixes #18281
Ref #17791
Helped-by: Gregory Anders <8965202+gpanders@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Update runtime files and translations
https://github.com/vim/vim/commit/3f32a5f1601ab2b0eba0caad00d4c26fb86a02a2
skip eval.txt (requires 8.2.4883)
|
| | |
| | |
| | |
| | |
| | | |
Problem: Search highlight disappears in the Visual area.
Solution: Combine the search attributes. (closes vim/vim#8134)
https://github.com/vim/vim/commit/2d5f385cee3668c44089edcb9d60b0b5d751ee5d
|
| |/
|/| |
|
| |
| |
| |
| | |
This reverts commit 7ac5359143ef25c4c8c0c427d5533f8d5824ed17.
This fix can cause more problems than it solves.
|
| | |
|
| |
| |
| |
| | |
gperf was removed in 36613b888bae7df764a26a28ca1627a2c0c2edeb
yay!
|
| |
| |
| | |
This was missed in https://github.com/neovim/neovim/pull/15583
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Changing 'switchbuf' may have no effect.
Solution: Handle 'switchbuf' in didset_string_options(). (Sean Dewar,
closes vim/vim#10406)
https://github.com/vim/vim/commit/39c46b43780ad00ea27a93d92aadd44753d4c3ea
Guess it doesn't hurt to cherry-pick didset_string_options from v8.1.2045
(but in option.c, for now).
|
|\ \
| | |
| | | |
refactor: replace char_u variables and functions with char
|
| | |
| | |
| | |
| | | |
Work on https://github.com/neovim/neovim/issues/459
|
|\ \ \
| | | |
| | | | |
refactor(eval): use Hashy McHashFace instead of gperf
|
| | | |
| | | |
| | | |
| | | | |
this removes gperf as a build dependency
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Implement filtering of actions based on the kind when passing the 'only'
parameter to code_action(). Action kinds are hierachical with a '.' as
the separator, and the filter thus allows, for example, both 'quickfix'
and 'quickfix.foo' when requestiong only 'quickfix'.
Fix https://github.com/neovim/neovim/pull/18221#issuecomment-1110179121
|
|\ \ \
| | | |
| | | | |
vim-patch:8.2.{4919,4921}: can add invalid bytes with :spellgood
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Spell test fails because of new illegal byte check.
Solution: Remove the test.
https://github.com/vim/vim/commit/fe978c2b6bb9d897d962595a4a51dd7a71dc8e89
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Problem: Can add invalid bytes with :spellgood.
Solution: Check for a valid word string.
https://github.com/vim/vim/commit/7c824682d2028432ee082703ef0ab399867a089b
|
| | |
| | |
| | |
| | |
| | |
| | | |
Hardcoding a charset causes trouble when porting Vim patches.
I previously tried to unset "charset" for certain file extensions, but
vim-patch.sh can generate more files, and automatically detecting file
encoding is more correct anyway.
|
|/ /
| |
| |
| |
| | |
Problem: '[ and '] marks may be wrong after undo.
Solution: Adjust the '[ and '] marks if needed. (closes vim/vim#10407, closes vim/vim#1281)
https://github.com/vim/vim/commit/82444cefa3fef87624a078ea86a72af7ef4ef42e
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`:tabmove` takes either an argument (`:tabmove -`) or an address (`:-tabmove`).
The code assumed that `:tabmove` is the first command on the cmdline, but that
is not the case when using additional modifiers like `:silent`.
Make the addr parsing more robust by searching the command first, then going
back to check for a potential address `-`.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
See: https://gitlab.freedesktop.org/xdg/xdg-specs/-/commit/4f2884e16db35f2962d9b64312917c81be5cb54b
- Move session persistent data to $XDG_STATE_HOME Change 'directory',
'backupdir', 'undodir', 'viewdir' and 'shadafile' default location to
$XDG_STATE_HOME/nvim.
- Move logs to $XDG_STATE_HOME, too.
- Add stdpath('log') support.
Fixes: #14805
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will check if the string after the variable in a @param is either
"number", "string", "table", "boolean" and "function" and if so add a
parenthesis around it. This will help separate the variable type with
the following text. Had all our functions been annotated with emmylua
then a more robust solution might have been preferable (such as always
assuming the third string is parameter type without making any checks).
I believe however this is a clear improvement over the current situation
and will suffice for now.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At the moment of comparison, the pointer save_curwin can be invalid (as
suggested by the comment) because it has been free'd. Worst, the new
curwin could have been re-allocated to that same pointer, altering the
execution flow unpredictably.
While there are many other potential similar cases to fix in the
codebase, the presented scenario is not hypothetical and does happen in
practice (while spawning new windows from fzf for instance).
There are numerous other instances of curwin comparisons in the
codebase, and they may need further investigation.
closes #16941
|
| |
| |
| |
| |
| |
| |
| |
| | |
Most code in keymap.h is for keycode definitions, while most code in
keymap.c is for the parsing and conversion of keycodes.
The name "keymap" may also make people think these two files are for
mappings, while in fact keycodes are used even when no mappings are
involved, so "keycodes" should be a better file name than "keymap".
|
| |
| |
| |
| |
| |
| |
| |
| | |
(undocumented) sourcehut feature for conditionally running consequent tasks.
ref:
https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C3cd90a91b7ce113bb3c5f07898c77543%40hacktivista.com%3E
https://git.sr.ht/~sircmpwn/builds.sr.ht/tree/master/item/worker/tasks.go#L196-198
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's special cased by the vimSubst syntax group, and isn't present in Vim's
vimCommand group.
For example, this fixes `call s:Foo()` highlighting `:` as Error in Nvim, as the
`s` is parsed as vimCommand rather than as vimUserFunc since
`contains=vimCommand` was added to vimUserFunc (and vimFunc) in a rt update.
Interestingly, `g:`, `l:`, etc. have the same issues due to :global, :list, etc.
Vim also has that problem, so it should ideally be fixed upstream.
We could also omit g[lobal] from vimCommand and rely on vimGlobal instead, but
it doesn't work in some cases, like when there's a `:` before the command. Also,
Vim matches only `g` in vimCommand for some reason, which doesn't produce any
highlight for `:global/foo/bar` (with Nvim you at least get some highlights on
the `global` bit despite the leading `:`).
Also, remove special handling of :py3 in syntax/vim.vim, as the generator seems
to have no problems finding it.
|
| |
| |
| |
| | |
- Use consistent formatting for args docs.
- Clarify inclusivity/exclusivity in `nvim_buf_[get|set]_text`.
|
| | |
|
| |
| |
| | |
Closes #18526.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
positions (#18525)
Problem: matchfuzzypos() with "matchseq" does not have all positions.
Solution: Also add a position for white space. (closes vim/vim#10404)
https://github.com/vim/vim/commit/9af2bc075169e14fd06ed967d28eac7206d21f36
|
|\ \
| | |
| | | |
vim-patch:8.2.{4901,4938}: NULL pointer access when using invalid pattern
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Crash when matching buffer with invalid pattern.
Solution: Check for NULL regprog.
https://github.com/vim/vim/commit/a59f2dfd0cf9ee1a584d3de5b7c2d47648e79060
|
|/ /
| |
| |
| |
| |
| | |
Problem: NULL pointer access when using invalid pattern.
Solution: Check for failed regexp program.
https://github.com/vim/vim/commit/8e4b76da1d7e987d43ca960dfbc372d1c617466f
|
|\ \
| | |
| | | |
feat(api): add `nvim_cmd`
|
| | |
| | |
| | |
| | | |
Adds the API function `nvim_cmd` which allows executing an Ex-command through a Dictionary which can have the same values as the return value of `nvim_parse_cmd()`. This makes it much easier to do things like passing arguments with a space to commands that otherwise may not allow it, or to make commands interpret certain characters literally when they otherwise would not.
|
| | | |
|
| | |
| | |
| | |
| | | |
add https://github.com/neovim/neovim/commit/aefdc6783cb77f09786542c90901a9e7120bea42
to .git-blame-ignore-revs
|