| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
It would previously fail with `set shell=sh` (no slash).
For the test itself we can just use a non-existing (fake) shell, because
it is only about the verbose output.
Ref: https://github.com/neovim/neovim/issues/9330
|
|
|
|
|
|
|
|
|
|
|
| |
* tests: move "busted" dir to "test"
It is used for outputHandlers only, and clearly belongs to the tests.
Use the full module name with the `-o` option to `busted` then for
clarity.
* luacheck
* test/busted/outputHandlers/TAP.lua: use/extend upstream
|
|
|
|
|
|
|
| |
Also fix V576: use width specification
> Incorrect format. Consider checking the third actual argument of the
> 'sscanf' function. It's dangerous to use string specifier without width
> specification. Buffer overflow is possible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- reltimestr(): Produce negative value by comparing the unsigned
proftime_T value to INT64_MAX.
https://github.com/neovim/neovim/issues/10452#issuecomment-511155132
1. The interfaces of nearly all platforms return uint64_t. INT64_MAX is
only half of that.
2. Low-level interfaces like this typically define that there is no
fixed starting point. The only guarantees are that it's (a)
monotonically increasing at a rate that (b) matches real time.
ref 06af88cd72ea
fix #10452
|
|\
| |
| | |
highlight: expose builtin highlight groups using hl_group_set event
|
| | |
|
| |
| |
| | |
Fixes https://github.com/neovim/neovim/issues/3757.
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Fix problem that 1byte extra memory was allocated in is_executable_in_path
* Revert "Revert "tests: executable_spec: enable pending test #10443" (#10454)"
This reverts commit 13fbeda0e56db36aeeb865bb5b33d13f69b2fdbc.
|
|\ \
| |/
|/| |
messages: fix missing newlines in execute("syn list").
|
| | |
|
|/
|
|
|
|
|
|
|
| |
The interaction between 'winblend' and doublewidth chars in the background
does not look very good. But check no chars get incorrectly placed
at least.
Also check that hidden EndOfBuffer region (from style="minimal") blends
correctly.
|
|
|
|
|
|
|
| |
The inspect modules is vendored as `vim.inspect`, and therefore it makes
sense to use this in tests also.
Ref: https://github.com/neovim/neovim/issues/6580
Ref: https://github.com/neovim/neovim/commit/bb3aa824b
|
|\
| |
| | |
ui: implement better redrawdebug for the compositor
|
| | |
|
|\ \
| | |
| | | |
compositor: handle float overlapping left half of doublewidth char
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
- define proftime_T as signed integer
- profile_sub(): allow negative result
closes #10452
|
|/
|
| |
This reverts commit b53c483a4a6db91aad621d5f404cc6e930b434de.
|
|\
| |
| | |
window: allow resize wincmds for floats
|
| | |
|
|/
|
| |
Closes https://github.com/neovim/neovim/pull/4766.
|
|\
| |
| | |
api/window: add style="minimal" flag to disable unwanted UI features for simple floats
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Move __gcov_flush to process_spawn, for more reliable coverage
tracking of subprocesses
- Travis: use GCOV_ERROR_FILE
- codecov: use "-X fix" to skip "fixing" uploaded coverage data; it
should be handled by codecov's backend instead.
- AppVeyor: no $PATH mangling, which breaks with the improved coverage tracking
due to missing .dll in PATH.
|
| |
| |
| | |
Should hopefully work now after efc6d9951b.
|
|/
|
|
|
|
| |
Problem: 'numberwidth' can only go up to 10.
Solution: Allow up to 20. (Charlie Stanton, closes vim/vim#4584)
https://github.com/vim/vim/commit/f8a071265535b8cc43e50a81f4d5049883ca50e4
|
|\
| |
| | |
screen: disable redrawing inside VimResized
|
| |
| |
| |
| |
| |
| | |
Note: test doesn't fail on master. I cannot reproduce the glitches with
-u NONE, probably it requires interfering events. But add some coverage
for these checks at least.
|
|/
|
|
|
|
|
| |
ext_message doesn't set msg_col. Add a space and let client deal with
wrapping. When using silent redirect show the unwrapped message form.
Removed check is already part of msg_advance()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Flaky test (osx):
[ FAILED ] ...is/build/neovim/neovim/test/functional/lua/loop_spec.lua @ 23: vim.loop timer
...is/build/neovim/neovim/test/functional/lua/loop_spec.lua:56: Expected objects to be the same.
Passed in:
(number) 0
Expected:
(number) 2
stack traceback:
...is/build/neovim/neovim/test/functional/lua/loop_spec.lua:56: in function <...is/build/neovim/neovim/test/functional/lua/loop_spec.lua:23>
It was bumped from sleeping for 20ms to 50ms in d33aaa0f5f already.
|
| |
|
|
|
|
|
|
|
|
| |
- Move .luacheckrc to root, add read_globals=vim
- Simplify lualint target, run it on all lua files
- Lint preload.lua, but ignore W211
- Remove testlint target, included in lualint (and lint)
- Clean up .luacheckrc
|
|
|
|
| |
Use it to improve ls_spec: it should not use the user's real shell for
performance and other reasons.
|
|
|
|
| |
It was moved to become pending in 18127f64c, but the assertion should be
kept.
|
|
|
|
| |
- Ensure the opposite of the expected bg is active.
- Improves performance: 1.2s instead of 4.5s.
|
|
|
|
|
|
|
|
|
|
|
| |
stops" (#10377)
[ ERROR ]...neovim/neovim/test/functional/autocmd/termclose_spec.lua @ TermClose event triggers when fast-exiting terminal job stops
test/functional/helpers.lua:96: Vim(call):E900: Invalid channel id
stack traceback:
test/functional/helpers.lua:96: in function 'request'
test/functional/helpers.lua:254: in function 'command'
...neovim/neovim/test/functional/autocmd/termclose_spec.lua:23: in function <...neovim/neovim/test/functional/autocmd/termclose_spec.lua:20>
|
|
|
|
|
|
| |
`retry()` would only try it three times (waiting for 20ms in between),
despite the large timeout.
Fixes https://github.com/neovim/neovim/issues/10265.
|
|
|
| |
ref #6289
|
|\
| |
| | |
api/lua: make nvim_execute_lua use native lua floats, not special tables
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rationale: the purpose of nvim_execute_lua is to simply call lua code with lua
values. If a lua function expects a floating point value, it should be enough
to specify a float as argument to nvim_execute_lua.
However, make sure to preserve the existing roundtripping behavior of
API values when using `vim.api` functions. This is covered by existing
lua/api_spec.lua tests.
|
|/
|
|
|
| |
- position might get invalid with "longest" match
- position might be wrong when completed pattern ends in "/"
|
|\
| |
| | |
luv callbacks: throw error on deferred methods instead of crashing
|
| |
| |
| |
| |
| | |
This avoids initializing libluv a second time if a plugin invokes
require'luv'. It is probably not an issue, but better to be safe.
|
| |
| |
| |
| |
| | |
Disable the use of deferred API functions in a fast lua callback
Correctly display error messages from a fast lua callback
|
|/
|
|
| |
closes #10267
|
|
|
|
|
|
|
|
|
|
| |
* build: update some test dependencies
* luacheck ignores
* BuildLua: add ${BUSTED} to depends for ${BUSTED_LUA}
This is required to rebuild it when busted gets updated.
|
|
|
|
|
|
|
|
|
|
|
| |
This matches Vim behavior. From `:help :ls` :
R a terminal buffer with a running job
F a terminal buffer with a finished job
? a terminal buffer without a job: `:terminal NONE`
TODO: implement `:terminal NONE`.
ref #10349
|
|
|
|
|
|
|
|
|
|
|
|
| |
Seen on Travis (osx):
[ RUN ] timers can be stopped from the handler: FAIL
.../build/neovim/neovim/test/functional/eval/timer_spec.lua:167: Expected objects to be the same.
Passed in:
(number) 2
Expected:
(number) 3
stack traceback:
.../build/neovim/neovim/test/functional/eval/timer_spec.lua:167: in function <.../build/neovim/neovim/test/functional/eval/timer_spec.lua:153>
|
|\
| |
| | |
eval/api: don't allow the API to be called in the sandbox
|
| |
| |
| |
| |
| | |
Identifying and maintaining a "secure" subset of the API would be too
much busywork. So just disable the entire thing.
|