| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | | |
Expand mappings first by calling `vpeekc()` directly.
|
|\ \ \
| | | |
| | | | |
fix(inccommand): do not change reg_prev_sub when previewing
|
| | | | |
|
| | | |
| | | |
| | | | |
Fixes #17207
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit fixes #9358, where emitting multiple messages with 'echo' or
a single one with 'echom' or 'echoerr' would result in a press-enter
prompt that couldn't be dismissed by pressing enter.
This requires adapting a few tests to spawn a UI before testing whether
press-enter prompts are blocking.
It also fixes #11718, as when combined with #15910 it enables making
sure that neovim never blocks and emits messages on startup.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This removes expand_spec.lua and copies test_expand.vim from Vim at
version v8.1.2278.
The rest of patch 8.1.2278 were already applied in #15952, so this marks
that patch as fully ported.
vim-patch:8.1.2278: using "cd" with "exe" may fail
Problem: Using "cd" with "exe" may fail.
Solution: Use chdir() instead.
https://github.com/vim/vim/commit/3503d7c94a6c8c2a5ca1665d648d0cb81afcc863
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: The write message mentions characters, but it's actually bytes.
Solution: Change "C" to "B" and "characters" to "bytes".
https://github.com/vim/vim/commit/3f40ce78f5c178d15871bd784ed878c78f0b8a44
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have to be sure that the bugs fixed in the previous patches also apply to
nvim_win_call.
Checking v8.1.2124 and v8.2.4026 is especially important as these patches were
only applied to win_execute, but nvim_win_call is also affected by the same
bugs. A lot of win_execute's logic can be shared with nvim_win_call, so factor
it out into a common macro to reduce the possibility of this happening again.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: ml_get error with :doautoall and Visual area. (Sean Dewar)
Solution: Disable Visual mode while executing autocommands.
https://github.com/vim/vim/commit/cb1956d6f2aece8ad93e19e5d4c7e0b5e405f056
This should also fix #16937 for nvim_buf_call, so test for it.
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
feat(highlight): ns=0 to set :highlight namespace
|
| | | |
| | | |
| | | |
| | | | |
Passing ns=0 to nvim_set_hl will alter the `:highlight` namespace.
|
|\ \ \ \
| |/ / /
|/| | | |
feat(statusline): support multibyte fillchar
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This includes a partial port of Vim patch 8.2.2569 and some changes to
nvim_eval_statusline() to allow a multibyte fillchar. Literally every
line of C code touched by that patch has been refactored in Nvim, and
that patch contains some irrelevant foldcolumn tests I'm not sure how to
port (as Nvim's foldcolumn behavior has diverged from Vim's).
|
|\ \ \ \
| | | | |
| | | | | |
vim-patch:8.2.{3787,3932,3934,3935,3938}: text formatting patches
|
| | | | |
| | | | |
| | | | |
| | | | | |
This no longer needed as Vim patch 8.1.1434 has been ported.
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
* fix: has('python') error
* fix: functional tests
|
| | | |
| | | |
| | | | |
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: The eval.txt help file is way too big.
Solution: Move the builtin function details to a separate file.
https://github.com/vim/vim/commit/1cae5a0a034d0545360387407a7a409310f1efe2
Note: Neovim-specific references to |functions| were changed to
|builtin-functions|. This included updates to:
1. test/functional/vimscript/functions_spec.lua
2. test/functional/vimscript/eval_spec.lua
3. runtime/doc/lua.txt
|
|\ \ \ \
| | | | |
| | | | | |
feat(provider)!: remove support for python2 and python3.[3-6]
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These versions of python has reached End-of-life. getting rid
of python2 support removes a lot of logic to support two
incompatible python versions in the same version.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
fix: set RedrawingDisabled before entering aucmd_win
|
| | |/ /
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
different (#17112)
Problem: After restoring a session buffer order can be quite different.
Solution: Create buffers first. (Evgeni Chasnovski, closes vim/vim#9520)
https://github.com/vim/vim/commit/26ebf1f036517ebeacf571c333a83cca7e13bbe2
---------------
As in Vim, this basically reverts 8.1.0829 providing different solution
(see vim/vim#9520).
Regarding Neovim, this basically reverts changes from #15062. Test about
restoring same terminals was a bit too restrictive with using actual
buffer ids, which changed with this patch (now they should be in the
same order as at `mksession` call), so I tweaked it.
|
|\ \ \ \
| | | | |
| | | | | |
fix(eval): v:lua support for `-` in module names
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
feat(api): expose extmark right_gravity and end_right_gravity
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vim-patch:8.2.3095: with 'virtualedit' set to "block" block selection is wrong
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: With 'virtualedit' set to "block" block selection is wrong after
using "$". (Marco Trosi)
Solution: Compute the longest selected line. (closes vim/vim#8495)
https://github.com/vim/vim/commit/b17ab86e7b8712206aa9ea7198c28db969e25936
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When trying to load a language parser, escape the value of
the language.
With language injection, the language might be picked up from the
buffer. If this value is erroneous it can cause `nvim_get_runtime_file`
to hard error.
E.g., the markdown expression `~~~{` will extract '{' as a language and
then try to get the parser using `parser/{*` as the pattern.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vim-patch:8.2.4203: entering a character with CTRL-V may include modifiers
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vim-patch:8.2.{3121,3410}: two 'listchars' fixes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: 'listchars' "exceeds" character appears in foldcolumn. Window
separator is missing. (Leonid V. Fedorenchik)
Solution: Only draw the "exceeds" character in the text area. Break the
loop when not drawing the text. (closes vim/vim#8524)
https://github.com/vim/vim/commit/41fb723ee97baa2f095cde601a5a144b168b7a6b
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
vim-patch:8.2.3153: URLs with a dash in the scheme are not recognized
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
vim-patch:8.2.1762: when a timer uses :stopinsert completion isn't stopped
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: When a timer uses :stopinsert Insert mode completion isn't
stopped. (Stanley Chan)
Solution: Call ins_compl_prep(ESC).
https://github.com/vim/vim/commit/d0e1b7103c14eb0d175c6b245b4b6ed93a204da9
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
feat(--headless): do not print anything when stdioopen() has been used
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit adds an on_print callback to stdioopen's dictionary
argument which lets the caller specify a function called each time
neovim will try to output something to stdout (e.g. on "echo" or
"echoerr" in --headless mode).
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
vim-patch:8.2.{3584,3586,3587}: :command "-keepscript" argument
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: "verbose set efm" reports the location of the :compiler command.
(Gary Johnson)
Solution: Add the "-keepscript" argument to :command and use it when
defining CompilerSet.
https://github.com/vim/vim/commit/58ef8a31d7087d495ab1582be5b7a22796ac2451
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
input: never escape CSI bytes and clean up related names and comments
|