| Commit message (Collapse) | Author | Age |
... | |
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Why?
- Because we can.
- Because the TUI is just another GUI™
- Because it looks kinda nice, and provides useful context like 1 out of 100
times
Complies with "don't pay for what you don't use".
Some crashes for resizing were unfolded, add tests for those.
|
| | |
| | |
| | |
| | | |
closes #9583
|
|\ \ \
| | | |
| | | | |
UI: always use contrete colors for default_colors_set
|
|/ / /
| | |
| | |
| | |
| | | |
But add an escape hatch needed for external TUI, so it still can use
terminal emulator defaults.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On Travis CI, -Wmissing-prototypes gives strange error:
In file included from ../src/nvim/eval.c:5965:
/home/travis/build/neovim/neovim/build/src/nvim/auto/funcs.generated.h.gperf:215:1: error: conflicting types for 'find_internal_func_gperf'
find_internal_func_gperf (register const char *str, register unsigned int len)
^
../src/nvim/eval.c:5962:20: note: previous declaration is here
const VimLFuncDef *find_internal_func_gperf(register const char *str,
^
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ref #343
Though I don't see a strong benefit, it isn't too much of a burden, and
maybe avoids confusion in some cases.
|
| | | |
| | | |
| | | |
| | | | |
- add_definitions() is preferred to CMAKE_C_FLAGS.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Makes the 'scrollback' option more consistent (same default for all buffers) and future-proof.
- Default to -1 for all buffers, but treat it as an implementation detail.
- Document range of 1 - 100_000.
- New terminal buffer by default sets scrollback=10_000 if the global default is -1.
- Existing terminal buffer: On entering terminal-mode or on refresh, if the user explicitly did `:set[local] scbk=-1`, the local value goes to 100_000 (max). (This is undocumented on purpose. Users should work with explicit values in the range of 1-100_000.)
|
|/ / /
| | |
| | |
| | |
| | | |
..which gets triggered when SIGUSR1 is sent to the nvim process.
Closes #9562
|
|\ \ \
| | | |
| | | | |
popupmenu: fix alignment of kind and extra after #9530
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Default for 'iminsert' is annoying.
Solution: Make the default always zero. (Yasuhiro Matsumoto, closes vim/vim#2071)
https://github.com/vim/vim/commit/4cf56bbc85f77846aeb378cfb071677336dfad6d
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: No debugger making use of the terminal window.
Solution: Add the term debugger plugin. So far only displays the current
line when stopped.
https://github.com/vim/vim/commit/fe386641b0c56c5de2bca8e1f4cd5e2a1f1aea7e
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: May get an endless loop if 'statusline' changes a highlight.
Solution: Do not let evaluating 'statusline' trigger a redraw.
https://github.com/vim/vim/commit/ba2929b6afd2fc20479912a8dec789be26a38244
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Running tests may pollute shell history. (Manuel Ortega)
Solution: Make $HISTFILE empty.
https://github.com/vim/vim/commit/6a8691d483914606213a24356a9124fa41c93b69
|
| |/ / /
|/| | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Implement popupmenu as a floating grid internally to reduce flicker
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Many of these are handled by the compositor. Check that it causes
no glitches.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes it possible for the compositor to compare the old pum with
the new position, and only clear what is necessary.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Initially we will use this for the popupmenu, floating windows will
follow soon
NB: writedelay + compositor is weird, we need more flexible
redraw introspection.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes #9557
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
- Avoid using platform-specific shell, it failed in MINGW_64 env.
- tty-test.c echos our input, which is exactly what we need for this test.
- Test fails correctly if 894f6bee54e8 is reverted.
|
| | |
| | |
| | |
| | |
| | | |
closes #8324
closes #8556
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Showing two characters for tab is limited.
Solution: Allow for a third character for "tab:" in 'listchars'. (Nathaniel
Braun, Ken Takata, closes vim/vim#3810)
https://github.com/vim/vim/commit/83a52171ba00b2b9fd2d1d22a07e38fc9fc69c1e
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously the mouse tests set 'listchars', but not 'list'. Funnily enough, the
space, where the `$` would normally appear, would still use new highlight group.
Set 'list' for good and fix the tests accordingly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using 'listchars' is a nice way to highlight tabs that were included by accident
for buffers that set 'expandtab'.
But maybe one does not want this for buffers that set 'noexpandtab', so now one
can use:
autocmd FileType go let &l:listchars .= ',tab: '
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix :terminal resizing, and some multigrid size cleanup
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
wp->w_height_inner now contains the "inner" size, regardless if the
window has been drawn yet or not. It should be used instead of
wp->w_grid.Rows, for stuff that is not directly related to accessing
the allocated grid memory, such like cursor movement and terminal size
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was changed by mistake in multigrid PR.
default_grid.Rows rather corresponds to the old screen_Rows
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Menu test fails on MS-Windows using gvim.
Solution: First delete the English menus.
https://github.com/vim/vim/commit/a1c8ecfda90c0e0e519762ae0521d7f6e297c32e
|
|\ \ \ \
| | | | |
| | | | | |
fix ":menu Item.SubItem", fix menu_get("foo")
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- 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.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- 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.
|