| Commit message (Collapse) | Author | Age |
... | |
| | | |
| | | |
| | | |
| | | | |
This macro serves as a sanity-check / documentation.
|
|/ / /
| | |
| | |
| | | |
This invariant is explained in aa39fc56f68e.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rework-of: ea7491586fcc
Helped-by: Björn Linse <bjorn.linse@gmail.com>
- The old (Vim) use of (char_u **)"" before ea7491586fcc is garbage,
which hints that this value was never used.
- The necessary condition is next to the NULL assigmnent, the pointer
would only be started to be accessed, if the length assignment next to
it is also changed.
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
False positive: vim_fgets has side effects.
ref 8586770e1fd8
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Vim version of Test_help_tagjump() tests for `:help sm?le` here. That
command got removed from Nvim, so the test was changed to check against `:help
sp?it` instead.
The new test already handled the case that on Win `:h split` would jump to the
entry for split() and on all other systems to the entry for :split.
Then this commit happened:
bb3aa824b lua/stdlib: vim.inspect, string functions
Since then `:h split` would jump to split() for macOS as well! I'm not sure why.
Anyway, instead of adding another check for has('mac'), we change the test once
more to be more akin to the original test. Instead of testing for :smile, which
is exclusive to Vim, we check against :checkhealth, which is exclusive to Nvim.
|
|/ /
| |
| |
| |
| | |
close #9515
ref #9280
|
|\ \
| | |
| | | |
screen: don't unconditionally clear messages on window scroll
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In vim, scrolling a window might mess up the cmdline. To keep it simple,
cmdline was always cleared for any window scroll. In nvim, where safe scrolling
is implemented in the TUI layer, this problem doesn't exist.
Clearing the message on scrolling, when we not do it e.g when switching tabs
is a bit weird, as the former is a much smaller context change.
A vim patch introduced the possibility to avoid the cmdlline clear for
redraws caused by async events. This case will now trivially be covered,
as the redraw is always avoided.
vim-patch:8.0.0592: if a job writes to a buffer screen is not updated
|
| |
| |
| |
| |
| |
| |
| | |
Reverts d2944e6a298e. mf_open() _can_ fail if the file does not exist.
closes #9503
closes #9504
|
|\ \
| | |
| | | |
lua: expose full interface of vim.inspect and add test
|
|/ /
| |
| |
| |
| |
| | |
Implement lazy loading for vim.submodule, this would be over-engineering
for inspect only, but we expect to use this solution also for more and
larger modules.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of eager-loading during plugin/* sourcing, define runtime
modules such as `vim.inspect` as lazy builtins. Otherwise non-builtin
Lua modules such as `vim.inspect` would not be available during startup
(init.vim, `-c`, `--cmd`, …).
ref #6580
ref #8677
|
|/ /
| |
| |
| |
| | |
ref #6580
ref #8677
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
closes #9349
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- When setting a fixed/locked/readonly var, it is more relevant to
report on the key, not its container dict. If its container dict (v:)
is readonly, that does not mean the key itself is readonly.
- Allow modifying a "fixed" var. "fixed" only prevents deletion.
|
|/ /
| |
| |
| |
| | |
- old URL redirects to https://www.viva64.com/en/pvs-studio-download/
- page now contains tgz files for macOS and Linux; the pattern must
match only the Linux URL
|
|\ \ |
|
| | |
| | |
| | |
| | | |
False positive: win_valid_any_tab() already checks `win != NULL`.
|
| | |
| | |
| | |
| | |
| | | |
Vim 8.1 source has equivalent structure (this isn't a case of accidental
regression), but it depends on FEAT_MBYTE.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
False positive, see b6c1fae6a94d. Clang ignores the assert introduced in
that commit?
|
|/ / |
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This maintenance release fixes some issues found in v0.3.3.
FIXES:
8a7b6200fbaa #9487 provider: improve error message if provider is missing
44ea903ca51a #9468 checkhealth: detect broken pip
b4028056fa5d Windows: nvim-qt v0.2.12 (fix potential "blank screen" at startup)
|
| |\ \
| | | |
| | | | |
release candidate 0.3.4
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Move `has_eval_provider()` check to `eval_call_provider()` to make sure that
every code path calls it first.
Previously we would, when pynvim was missing, get a nice error message for
`:python3 1`, but not for `:py3file blah`.
Fixes https://github.com/neovim/neovim/issues/9485
|
| | | | |
|
| |/ / |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This maintenance release fixes some issues found in v0.3.2 .
FIXES:
a597ab8d1ba7 #9442 Merge pull request from jamessan/revert-pynvim
d7b3ac029c30 health/provider: Check for available pynvim when neovim module missing
edeb19d5e959 python#CheckForModule: Use the given module string instead of hard-coding pynvim
0dd89cda9c47 {health,provider}/python: Import the neovim, rather than pynvim, module
fc6e8a4db8eb #9423 TUI: Konsole DECSCUSR fixup
|
| | | |
|
| | |
| | |
| | |
| | | |
grep support of "\s" pattern is unreliable.
|
| |\ \
| | | |
| | | | |
Rework Python provider/health check to use neovim module again
|
| |\ \ \
| | | | |
| | | | | |
Mark a few more functionaltests as fragile
|