| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | | |
Function was split into tv_dict_add_nr() and tv_dict_add_str().
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Also fixes buffer reusage in setmatches() and complete().
|
| | | |
|
| | |
| | |
| | | |
Closes #5823
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Reasoning; currently INTERNAL_CALL is mostly used to determine whether it is
needed to deal with NL-used-as-NUL problem. This code is useful for nvim_… API
calls done from VimL, but not for API calls done from lua, yet lua needs to
supply something as channel_id.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Note: this will *still* crash when using API in cases similar to the one
described in first commit. Just it needs different code to reproduce.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
No tests yet, no documentation update, no :lua* stuff, no vim module.
converter.c should also work with typval_T, not Object.
Known problem: luaeval("1", {}) results in
PANIC: unprotected error in call to Lua API (attempt to index a nil value)
Ref #3823
|
| |
| |
| |
| |
| |
| | |
* The allow_keys global is unused in nvim, remove it
* clint
|
| |
| |
| |
| |
| |
| | |
Problem: Error for min() and max() contains %s. (Nikolay Pavlov)
Solution: Pass the function name. (closes vim/vim#1040)
https://github.com/vim/vim/commit/26b84339fd8766898bcf6a259cbc2e0c38689726
|
|\ \
| | |
| | | |
vim-patch: 7.4.2255,7.42256
|
| |/
| |
| |
| |
| |
| |
| | |
Problem: Coverity complains about null pointer check.
Solution: Remove wrong and superfluous error check.
https://github.com/vim/vim/commit/db249f26edf7a5f88d1f4468d08ec5b84f5ab7ad
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Part of ":oldfiles" command isn't cleared. (Lifepillar)
Solution: Clear the rest of the line. (closes 1018)
https://github.com/vim/vim/commit/885c00eabe6d1fd757d4f0eb531ad3a15a35ec04
|
|/
|
|
|
|
|
| |
The original patch makes all the modeline comments consistent, but these
have been removed in the neovim source. However there as a correction of
a comment included in the patch that we can use.
https://github.com/vim/vim/commit/edf3f97ae2af024708ebb4ac614227327033ca47
|
|
|
|
|
|
| |
Problem: Missing colon in error message.
Solution: Add the colon. (Dominique Pelle)
https://github.com/vim/vim/commit/ba2099034f92a2814494f37bddb0c57d034401b4
|
|\
| |
| | |
vim-patch:7.4.2069,7.4.2101,7.4.2222,7.4.2223
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Buffer overflow when using latin1 character with feedkeys().
Solution: Check for an illegal character. Add a test.
https://github.com/vim/vim/commit/d3c907b5d2b352482b580a0cf687cbbea4c19ea1
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
vim-patch:7.4.1991,7.4.1992,7.4.1993,7.4.1994
|
| |
| |
| |
| |
| |
| |
| |
| | |
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: Cannot get all information about a quickfix list.
Solution: Add an optional argument to get/set loc/qf list(). (Yegappan
Lakshmanan)
https://github.com/vim/vim/commit/d823fa910cca43fec3c31c030ee908a14c272640
|
|\
| |
| | |
Better b:changedtick support
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reasonings:
1. It is not used for anything, but scope dictionaries currenly. So there is no
need to generalize and split it into dict_set_var (which will contain some
scope-dictionary-specific checks) and dict_set_value (which will work for any
dictionary).
2. Check for key size is no longer valid for non-scope dictionaries: you *can*
use empty keys there. In scope dictionaries also, but you actually are not
supposed to store there anything, but variables.
Note that actually one may still do
let b:[''] = 1
and “bypass” check for variable name. It won’t change what `echo b:` will show,
but it may affect code which iterates over scope dictionary keys and sets them
to something (if there is such code).
|
| |
| |
| | |
Was replaced by the previous patch. Also fixes legacy test 055.
|
| |
| |
| | |
Port of vim-patch:8.0.0343
|
| |
| |
| | |
Port of vim-patch:8.0.0345
|
| | |
|
| |
| |
| |
| |
| | |
- They are no longer responble for using gettext.
- They now receive string length and use %.* format specifier in messages.
- And one less global: one of the error messages is never repeated.
|
| |
| |
| | |
Ref vim/vim#1497
|
| |
| |
| | |
If I am not mistaking, this commit should not change any functionality.
|
| |
| |
| | |
It still may be unlocked by `:unlock b:.var`.
|
| | |
|
|\ \
| | |
| | | |
Refactor writefile() and create more tests for it
|
| | |
| | |
| | | |
This way success/failure return from this function is more precise.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1. When calling writefile(list, fname, []) do not show error message twice.
2. Do not allow file name to be overwritten for writefile([1], 2).
3. Do not show “Can’t open file with an empty name” error after error like
“using Float as a String” when type of the second argument is not correct.
4. Do not give multiple error messages and still continue for code like
`writefile(["test", [], [], [], "tset"])`.
Note that to fix 4. ideally I need tv_check_str_or_nr which is currently present
in two PRs: #6114 and #5119. I would want to avoid copying this function into
a yet another PR.
Ref vim/vim#1476.
|
| | |
| | |
| | | |
Previously it could attempt to write trailing newline before returning.
|
| | | |
|
| | | |
|