| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Problem: Menu test fails on MS-Windows using gvim.
Solution: First delete the English menus.
https://github.com/vim/vim/commit/a1c8ecfda90c0e0e519762ae0521d7f6e297c32e
|
|
|
|
|
|
| |
- Return the menu properties, not only its children.
- If the {path} param is given, return only the first node. The "next"
nodes in the linked-list are irrelevant.
|
|
|
|
|
| |
Caused by a typo: `dict` instead of `dic`. Renamed variable to `d` to
make it less similar.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
:menu should print sub-menu contents. E.g. this should print the
"File.Save" submenu:
nvim -u NORC
:source $VIMRUNTIME/menu.vim
:menu File.Save
Regressed in dc685387a3d6
Blocks #8173
menu_get() also was missing some results for some cases.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Lua
- developer guidelines
- MAINTAIN.md
- TUI: cleanup
- TUI: mention Windows terminfo builtins
- cleanup if_pyth, redirect python-bindeval tag
Helped-by: Björn Linse <bjorn.linse@gmail.com>
Helped-by: erw7 <erw7.github@gmail.com>
|
| |
| |
| |
| |
| |
| | |
Problem: Menu test fails on MS-Windows.
Solution: Use a menu entry with only ASCII characters.
https://github.com/vim/vim/commit/5558d19432120696409c007c64d5ba52eed42670
|
|/
|
|
|
|
| |
Problem: We can't change the case in menu entries, it breaks translations.
Solution: Ignore case when looking up a menu translation.
https://github.com/vim/vim/commit/11dd8c1201033dd74e2ea665ba277425b4b965b0
|
|
|
|
|
|
|
| |
Add 'multiline' flag to history for correct :messages output
Use larger buffer size for multiline messages. if this turns out to not
be enough, we could do size calculation like api_set_error
|
| |
|
|
|
|
|
| |
The added function behaves like the non-echo function but display message
in a echo-style way (i.e. tab and newline are preserved)
|
|
|
| |
closes #9522
|
|
|
|
|
|
|
|
|
|
|
|
| |
closes #8274
The parent commit tries a different approach, but that fails on Apple
Clang version:
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin17.7.0
which somehow compiles the check_c_source_compiles() check, but then
complains during later compilation that __fpclassify is not defined
(regardless of "#include <math.h>").
|
|
|
|
|
|
|
|
|
|
|
|
| |
closes #8274
- Instead of #undef and re-#define, define "xfoo" wrappers to avoid
include-order sensitivity.
- The warnings are bogus, caused by bad interaction between glibc and
clang 6+.
- https://bugs.llvm.org/show_bug.cgi?id=35268
- https://bugs.llvm.org/show_bug.cgi?id=39738
- https://bugzilla.redhat.com/show_bug.cgi?id=1472437
|
|\
| |
| | |
Remove support for using jemalloc instead of the system allocator
|
| |
| |
| |
| |
| |
| | |
There was never any investigation done to determine whether using
jemalloc was actually a net benefit for nvim. It has been a portability
limitation and adds another factor to consider when triaging issues.
|
|\ \
| | |
| | | |
API/UI: add nvim_input_mouse() including multigrid mouse support
|
| |/ |
|
| | |
|
|/
|
|
|
| |
Otherwise the symbols defined in config/config.h.in may not be defined,
depending on include-order.
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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?
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is various places where 'conceallevel' and 'concealcursor'
necessitates additional redraws. This tries to separate the different
cases and handle each accordingly:
- Share code with 'cursorline' for the common case: vertical move of
cursor within the same window (concealcursor not active)
- Improve the logic for managing 'concealcursor' and switching modes:
test for the case where the new mode behaves differently from the
last one.
- Clarify the special case for horizontal movement within a line when
'concealcursor' is active, now there is an if-statement only for this
and not hidden in larger check mostly for the first point.
- Keep the special case for moving between windows as is.
|
|
|
|
| |
vim-patch:8.1.0726: redrawing specifically for conceal feature
|
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| | |
screen: make update_screen() the only entry point for redrawing
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
update_single_line() was only used for 'concealcursor'. But 'cursorline'
has very similiar characteristics (redraw both lines on move cursor
between lines) and works without its own special entry point to the
redraw subsystem.
Later on 'concealcursor' and 'cursorline' could share more logic, but for
now make the former use standard redrawWinline(). Make sure it is called
before update_screen(), so that it is immediately visible.
Get rid of update_prepare() and update_finish(), and all issues from
them and their callsites not being in sync with changes to
update_screen()
|
| |
| |
| |
| |
| |
| |
| |
| | |
vim-patch:8.0.1336: cannot use imactivatefunc() unless compiled with +xim
vim-patch:8.0.1338: USE_IM_CONTROL is confusing and incomplete
vim-patch:8.1.0646: cannot build with Ruby 2.6.0
vim-patch:8.1.0656: trying to reconnect to X server may cause problems
vim-patch:8.1.0664: configure "fail-if-missing" does not apply to enable-gui
|