| Commit message (Collapse) | Author | Age |
... | |
| |/ / /
|/| | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Checking did_throw after executing autocommands is wrong. (Daniel
Hahler)
Solution: Call aborting() instead, and only when autocommands were executed.
https://github.com/vim/vim/commit/21662be2211675824df1771c7f169948ede40c41
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`cw` and `cW` behave like `ce` and `cE` respectively. This is
inconsistent compared to `dw` and `dW`.
Introduce a new cpoptions flag "_" to toggle the Vi behavior.
Closes #6234
Patch-by: Christian Brabandt <cblists@256bit.org>
References:
https://github.com/chrisbra/vim-mq-patches/blob/master/cpo_changeword
https://groups.google.com/d/msg/vim_use/aaBqT6ECkA4/ALf4odKzEDgJ
https://groups.google.com/d/msg/vim_dev/Dpn3xtUF16I/T6JcOPKN6usJ
http://www.reddit.com/r/vim/comments/26nut8/why_does_cw_work_like_ce/
|
|/ /
| |
| | |
Signed-off-by: Gavin Thomas Claugus <gclaugus@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Problem: QuickFixCmdPre and QuickFixCmdPost autocommands are not always
triggered.
Solution: Also trigger on ":expr", ":cbuffer", etc. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/04c4ce650f9e533cd35b2aa6803f4d354d3ec7aa
|
|\ \
| | |
| | | |
vim-patch:7.4.2051,7.4.2068,7.4.2097
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Warning from 64 bit compiler.
Solution: use size_t instead of int. (Mike Williams)
https://github.com/vim/vim/commit/d4f31dc45482e8db527ca044b9c3436b1e750006
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Not all arguments of trunc_string() are tested. Memory access
error when running the message tests.
Solution: Add another test case. (Yegappan Lakshmanan) Make it easy to run
unittests with valgrind. Fix the access error.
https://github.com/vim/vim/commit/b9644433d2728e99fab874e5e33147ad95d23a31
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: No proper testing of trunc_string().
Solution: Add a unittest for message.c.
https://github.com/vim/vim/commit/502ae4ba63561c98ac69af26cd9883bfd18d225f
|
|\ \ \
| | | |
| | | | |
vim-patch:7.4.2220,7.4.2265
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: printf() isn't tested much.
Solution: Add more tests for printf(). (Dominique Pelle)
https://github.com/vim/vim/commit/76efafba2af36ae5f6c7b79b56c537fcbcdb386c
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: printf() gives an error when the argument for %s is not a string.
(Ozaki Kiichi)
Solution: Behave like invoking string() on the argument. (Ken Takata)
https://github.com/vim/vim/commit/e5a8f35b4286135f3469f3b00a6c2220553d9658
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the buffer that nvim_buf_set_lines() is changing is not in any vim
window, fix_cursor() leads to calling ml_get_buf() with an invalid line
number. The condition that fix_cursor() was called on was (buf ==
curbuf), but this is always true because of the call to
switch_to_win_for_buf() earlier in the function.
Instead this should be predicated on (save_curbuf.br_buf == NULL)
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do this on all systems, so that portable builds work everywhere. This
allows us to ship archives with this folder structure:
bin/nvim
share/nvim/runtime
then ./bin/nvim works without the user needing to explicitly set VIMRUNTIME.
|
| |
| |
| |
| |
| |
| |
| | |
statusline still disappears in some cases, but this change is a net
improvement.
References #3929 #5692 #4884 #6157
|
| |
| |
| |
| | |
You cannot escape clint...
|
|\ \
| | |
| | | |
ci: Add Coverity modeling
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| |/ /
|/| | |
vim-patch: 8.0.0319, 8.0.0347
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: When using CTRL-X CTRL-U inside a comment, the use of the comment
leader may not work. (Klement)
Solution: Save and restore did_ai. (Christian Brabandt, closes vim/vim#1494)
https://github.com/vim/vim/commit/d099e033703ce0772f152b8df8a763f0b65303ee
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Insert mode completion does not respect "start" in 'backspace'.
Solution: Check whether backspace can go before where insert started.
(Hirohito Higashi)
https://github.com/vim/vim/commit/190b04cdd936f4696c22466b7f077f9371d96580
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After using 'termopen("echo") the current buffer content is changed,
but the cursor position of the current window is not updated.
Because of this, a call to 'mb_adjust_cursor()' can lead to a
heap-buffer-overflow.
Fix this by resetting the cursor for the current window.
Fixes #3161
|
| | |
|
| |
| |
| |
| | |
Closes #3744
|
| |
| |
| |
| |
| |
| | |
The window may have closed already, then `curwin` should not be altered.
Closes #6204
|
| |
| |
| |
| |
| |
| | |
Problem: No testing for Farsi code.
Solution: Add a minimal test. Clean up Farsi code.
https://github.com/vim/vim/commit/ee2615af64fdcee87d8e4b13b65356e77fbd969b
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix a problem when filtering manually folded lines
When foldMarkAdjustRecurse() is called to adjust folds that start inside
the range of lines that are being moved and end outside that range, it
calculates `amount_after` for its recursive call incorrectly.
The calculation assumes that folds inside the changed range are being
deleted, but this is not always the case.
This means nested folds that start after the changed range of lines are
shifted an incorrect amount.
We fix this by calculating the `amount_after` differently if the folds
inside the changed range are not being deleted.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: When using indent folding and changing indent the wrong fold is
opened. (Jonathan Fudger)
Solution: Open the fold under the cursor a bit later. (Christian Brabandt)
https://github.com/vim/vim/commit/54b2bfa399017ebae76ed62f21578261d1b55c1f
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: An address relative to the current line, ":.,+3y", does not work
properly on a closed fold. (Efraim Yawitz)
Solution: Correct for including the closed fold. (Christian Brabandt)
https://github.com/vim/vim/commit/ded2782783f352201ac0b05c6dbe4831adb4a58b
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's important that users have a single, easy-to-remember place for
reading about the API. So this commit changes gen_api_vimdoc.py so that
the generated section is appended to api.txt instead of creating
a separate document.
Also remove the section numbering and ToC: it's a maintenance cost, and
it will be unnecessary when #5169 is integrated.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
In terminal-mode these options are nonsense because cursor is placed at
end of buffer to "follow" output.
Closes #2259
|
| |
| |
| |
| |
| |
| | |
Let the terminal dictate the normal-mode cursor position. This will be
disorienting sometimes, but it is closer to what users expect vs always
going to the last line.
|
|\ \
| | |
| | | |
win/package: runtime files
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime/plugin/gui_shim.vim is from Neovim-Qt. This is a temporary
measure, we will add real UI events which obviate gui_shim.vim.
Closes #6145
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
Problem: When the window scrolls horizontally when the popup menu is
displayed part of it may not be cleared. (Neovim issue #6184)
Solution: Remove the menu when the windows scrolled. (closes vim/vim#1524)
Fixes #6184
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Man test fails when run with the GUI.
Solution: Adjust for different behavior of GUI. Add assert_inrange().
https://github.com/vim/vim/commit/61c04493b00f85d0b97436260a9ef9ab82143b78
Only changes related to assert_inrange() were included, since we have a
distinct man plugin.
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Text object tests are old style.
Solution: Turn them into new style tests. (James McCoy, closes vim/vim#941)
https://github.com/vim/vim/commit/00b24be454800f544676aa8850fb4378a568901e
|
|\ \
| | |
| | | |
vim-patch:7.4.1991,7.4.1992,7.4.1993,7.4.1994
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: True-false test fails.
Solution: Filter the dict to only keep the value that matters.
https://github.com/vim/vim/commit/05e418d436410cd8bbf5a29ff81e8ad68408b1e8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Not all TRUE and FALSE arguments are tested.
Solution: Add a few more tests.
https://github.com/vim/vim/commit/6bb450145e96d7b182769fd9502a267da72667ec
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Values for true and false can be confusing.
Solution: Update the documentation. Add a test. Make v:true evaluate to
TRUE for a non-zero-arg.
https://github.com/vim/vim/commit/e381d3d5e098546854b008e01ca1d28ba1a4a057
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: glob() does not add a symbolic link when there are no wildcards.
Solution: Remove the call to mch_getperm().
https://github.com/vim/vim/commit/00efded1064427ab3f84e4d57af62e0aab876fc6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Default Vim behavior of i_CTRL-<Space> is to insert the last-inserted
text and exit insert mode. :help i_CTRL-@
Before this commit that did not happen because insert_handle_key()
checks for NUL instead of checking for ' ' with a CTRL `mod_mask`.
I'm leaving the check for NUL despite the fact that at the moment that
key is never seen when using the terminal UI (not for C-Space, nor C-@).
This is because I assume it's still allowed for other front-ends to pass
NUL, but at the moment the terminal UI isn't.
|
|\ \ \
| | | |
| | | | |
vim-patch:8.0.0353
|