| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
- Any long symbol is intentional and should never be hardwrapped.
- Vim help tags are often hyphenated, and hardwrapping on hyphens breaks
the Vim help syntax parser.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- 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
|
|
|
|
|
|
| |
Test case:
LANG= LC_ALL= LC_CTYPE= tmux
nvim -u NORC +'checkhealth nvim'
|
|\
| |
| | |
Lua: format multiline messages / emsgf_multiline()
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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)
|
| |
| |
| | |
fixes #9529
|
|\ \
| |/
|/| |
Fix api doc nvim_buf_lines_event example
|
|/
|
|
| |
when send_buffer=true, the first nvim_buf_lines_event will come with
lastline=-1 instead of 0.
|
|
|
| |
closes #9522
|
|
|
|
|
|
| |
To validate:
cat codecov.yml | curl --data-binary @- https://codecov.io/validate
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|
|
|
|
| |
Since this was added, codecov has been adding comments to every PR, even
though we have specified `comment: off`.
|
|\
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reverts previous experiment. PVS root is working correctly, one can
observe this in the PVS-studio.err file, for example:
/usr/local/clang-7.0.0/lib/clang/7.0.0/include/stddef.h:51:1: warning: V677 ...
/usr/local/clang-7.0.0/lib/clang/7.0.0/include/stddef.h:132:1: warning: V677 ...
./src/nvim/fileio.c:1382:1: warning: V1026 ...
./src/nvim/fileio.c:1388:1: warning: V1026 ...
The "./src/nvim/…" paths are correctly rooted, yet PVS somehow still
thinks it should analyze "/usr/local/clang-7.0.0/…".
See also: https://stackoverflow.com/q/44906903
|
|/
|
|
|
| |
System headers should be ignored by PVS, but somehow aren't.
See also: https://stackoverflow.com/q/44906903
|
|\ |
|
| |
| |
| |
| |
| | |
This system header should be ignored by PVS.
See also: https://stackoverflow.com/q/44906903
|
| |
| |
| |
| | |
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
|