| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
| |
Ref #4615
Ref vim/vim#768
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Adds unit test for tv_list_extend and regression test for extend() VimL
function.
|
|
|
|
| |
Fixes some FIXMEs in eval/null_spec.lua.
|
|
|
|
|
|
| |
For now it is full of FIXMEs and tests for incorrect behaviour. Sorted out to
have FIXMEs in one place, commented crashing tests in other and correctly
working tests in the third one.
|
|
|
|
|
|
| |
Found two bugs:
1. Multiple unneeded error messages, vim/vim#1039.
2. Unformatted error string, vim/vim#1040.
|
| |
|
|
|
|
|
|
|
|
|
| |
Additionally
- Rename former tv_get_float to tv_get_float_chk due to name conflict (former
get_tv_float is better suited for being tv_get_float).
- Add E907 error to get_tv_float() and test that it is being raised when
appropriate.
|
| |
|
|
|
|
| |
Also fixes buffer reusage in setmatches() and complete().
|
| |
|
|
|
| |
Regression test coverage for #6070.
|
| |
|
|\
| |
| | |
Better b:changedtick support
|
| | |
|
| |
| |
| | |
Fixes #6147
|
| |
| |
| | |
Port of vim-patch:8.0.0343
|
| |
| |
| | |
Port of vim-patch:8.0.0345
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
If I am not mistaking, this commit should not change any functionality.
|
| |
| |
| | |
It still may be unlocked by `:unlock b:.var`.
|
| |
| |
| | |
Contains a number of FIXMEs.
|
|\ \
| |/
|/| |
Refactor writefile() and create more tests for it
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| | |
Return 1 for UNIX with a functioning clipboard provider.
Closes #6103
|
|/
|
|
|
|
|
|
| |
Main points:
- Replace `char_u` with `char` in some cases.
- Remove `str[len] = NUL` hack in some cases when `str` may be considered
`const`.
|
| |
|
|
|
|
|
| |
This test sometimes fails on AppVeyor, but we still want to exercise the
code path and get at least a "soft" notification in the pending list.
|
|
|
|
| |
Absolute path is considered executable even *without* an extension.
|
|
|
|
|
|
|
|
|
|
| |
patch 8.0.0280: problem setting multi-byte environment var on MS-Windows
Problem: On MS-Windows setting an environment variable with multi-byte
strings does not work well.
Solution: Use wputenv when possible. (Taro Muraoka, Ken Takata)
7c23d1d9d9cc
|
|
|
|
|
|
|
|
| |
This allows executables to be found by :!, system(), and executable() if
they live next to ("sibling" to) nvim.exe. This is what gvim on Windows
does, and also matches the behavior of Win32 SearchPath().
https://github.com/vim/vim/blob/c4a249a736d40ec54794827ef95804c225d0e38f/src/os_win32.c#L354-L370
|
| |
|
|\
| |
| | |
Fix xclip tests to cleanup on their own
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When test/functional/eval/system_spec.lua is run on its own,
helpers.os_name() was being called before a session had been created.
This caused that describe block to fail.
Turning printargs_path into a function delays the call of
helpers.os_name() until the test is being run, which ensures a session
is available.
|
| |
| |
| |
| | |
Closes #4900
|
| | |
|
|/
|
|
| |
Closes #5422
|
|
|
|
|
|
| |
Test sometimes fails on AppVeyor (Windows). 300/50=6, but there could be
environment factors that miss the timer interval on the "edges".
timer_start() does not have such a hard requirement.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also make setpos("'A", [999, 1, 1, 0]) fail, i.e. return -1 (assuming there is no buffer 999).
Fixes #5713
Background:
`:help setpos()` mentions an argument `"bufnum"` that determines the buffer a mark should be put in.
This argument is respected for uppercase marks, but not for lowercase marks.
This is reasonable (though I personally would like `setpos()` to be able to set marks in other buffers), but the help doesn't mention this anywhere.
It's also strange that attempting to change buffers with `setpos('.', [bufnr('#'), 1, 1, 0])` alerts the user that having a different buffer is an error, while attempting to set a mark with `setpos("'d", [bufnr('#'), 1, 1, 0])` doesn't tell the user that the `"bufnum"` argument is an error.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Do _not_ set v:shell_error on parameter validation error.
system([...]) does not invoke a shell, so this change is somewhat
questionable. But `:help v:shell_error` is sufficiently vague to allow
-1 in this case.
|
| |
|