aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | UI: implement 'pumblend' option for semi-transparent popupmenuBjörn Linse2019-02-07
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | man.vim: set 'linebreak'Justin M. Keyes2019-02-06
| | | | | | | | | | | | closes #9583
* | | Merge pull request #9581 from bfredl/alwaysrgbBjörn Linse2019-02-05
|\ \ \ | | | | | | | | UI: always use contrete colors for default_colors_set
| * | | UI: always use contrete colors for default_colors_setBjörn Linse2019-02-05
|/ / / | | | | | | | | | | | | But add an escape hatch needed for external TUI, so it still can use terminal emulator defaults.
* | | Merge #9560 from justinmk/Wmissing-prototypesJustin M. Keyes2019-02-04
|\ \ \
| * | | build: PRAGMA_DIAG_PUSH_IGNORE_MISSING_PROTOTYPESJustin M. Keyes2019-02-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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, ^
| * | | build: -Wmissing-prototypesJustin M. Keyes2019-02-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | build: set compiler options in one placeJustin M. Keyes2019-02-04
| | | | | | | | | | | | | | | | - add_definitions() is preferred to CMAKE_C_FLAGS.
* | | | options: set 'scrollback' to -1 by default #9563Marco Hinz2019-02-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.)
* | | | events: add "Signal" event #9564Marco Hinz2019-02-04
|/ / / | | | | | | | | | | | | ..which gets triggered when SIGUSR1 is sent to the nvim process. Closes #9562
* | | Merge pull request #9579 from bfredl/pum_fixBjörn Linse2019-02-03
|\ \ \ | | | | | | | | popupmenu: fix alignment of kind and extra after #9530
| * | | popupmenu: fix alignment of kind and extra after #9530Björn Linse2019-02-03
| | | |
* | | | Merge #9578 'vim-patch:8.0.{1045,1073,1077,1114}'Justin M. Keyes2019-02-03
|\ \ \ \
| * | | | vim-patch:8.0.1114: default for 'iminsert' is annoyingJan Edmund Lazo2019-02-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | vim-patch:8.0.1077: no debugger making use of the terminal windowJan Edmund Lazo2019-02-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | vim-patch:8.0.1073: may get an endless loop if 'statusline' changes a highlightJan Edmund Lazo2019-02-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | vim-patch:8.0.1045: running tests may pollute shell historyJan Edmund Lazo2019-02-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Running tests may pollute shell history. (Manuel Ortega) Solution: Make $HISTFILE empty. https://github.com/vim/vim/commit/6a8691d483914606213a24356a9124fa41c93b69
* | | | | rename ui_is_external to ui_has (#9576)Justin M. Keyes2019-02-03
| |/ / / |/| | |
* | | | Merge pull request #9530 from bfredl/pum_floatBjörn Linse2019-02-02
|\ \ \ \ | |/ / / |/| | | Implement popupmenu as a floating grid internally to reduce flicker
| * | | multigrid: reset win scrolling after swap messageBjörn Linse2019-02-02
| | | |
| * | | tests/ui: add test for popupmenu redrawing in various situationsBjörn Linse2019-02-02
| | | | | | | | | | | | | | | | | | | | Many of these are handled by the compositor. Check that it causes no glitches.
| * | | ui/compositor: add redraws needed due to intersected doublewidth chars.Björn Linse2019-02-02
| | | |
| * | | vim-patch:8.1.0792: bad display if opening cmdline window from Insert completionBjörn Linse2019-02-02
| | | |
| * | | Reduce pum redraws from edit.c by delaying undisplay of pumBjörn Linse2019-02-02
| | | | | | | | | | | | | | | | | | | | This makes it possible for the compositor to compare the old pum with the new position, and only clear what is necessary.
| * | | UI: add "compositor" layer to merge grids for TUI use in a correct wayBjörn Linse2019-02-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Initially we will use this for the popupmenu, floating windows will follow soon NB: writedelay + compositor is weird, we need more flexible redraw introspection.
* | | | inccommand: auto-disable if folding is slow #9568KillTheMule2019-02-01
| | | | | | | | | | | | | | | | | | | | Fixes #9557
* | | | Merge #9565 from justinmk/testJustin M. Keyes2019-01-31
|\ \ \ \ | |/ / / |/| | |
| * | | test: adjust timer_specJustin M. Keyes2019-01-31
| | | |
| * | | test: improve reliability of ":terminal topline" testJustin M. Keyes2019-01-31
|/ / / | | | | | | | | | | | | | | | - 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.
* | | :terminal : set topline based on window height #8325Andrew Pyatkov2019-01-29
| | | | | | | | | | | | | | | closes #8324 closes #8556
* | | Merge #9539 "options: make 'listchars' and 'fillchars' local to window"Marco Hinz2019-01-28
|\ \ \
| * | | tests: 'fcs' and 'lcs' are local to the windowMarco Hinz2019-01-26
| | | |
| * | | vim-patch:8.1.0759: showing two characters for tab is limitedMarco Hinz2019-01-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | linter: fix issuesMarco Hinz2019-01-26
| | | |
| * | | tests: fix mouse tests that use lcs=eol:$Marco Hinz2019-01-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | options: make 'fillchars'/'listchars' local to windowMarco Hinz2019-01-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: '
* | | | doc [ci skip] (#9553)Justin M. Keyes2019-01-27
| | | |
* | | | Merge pull request #9551 from bfredl/multitermBjörn Linse2019-01-27
|\ \ \ \ | | | | | | | | | | Fix :terminal resizing, and some multigrid size cleanup
| * | | | screen: simplify wp->w_lines allocation logicBjörn Linse2019-01-27
| | | | |
| * | | | terminal: handle size when switching buffers in windowBjörn Linse2019-01-27
| | | | |
| * | | | window/ui: reorganize size variables, fix terminal window size with multigrid.Björn Linse2019-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | screen: remove superfluous default_grid indirection for global sizeBjörn Linse2019-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | This was changed by mistake in multigrid PR. default_grid.Rows rather corresponds to the old screen_Rows
| * | | | terminal: simplify sizing logicBjörn Linse2019-01-27
|/ / / /
* | | | vim-patch:8.0.0413: menu test fails on MS-Windows #8173ckelsel2019-01-27
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Menu test fails on MS-Windows using gvim. Solution: First delete the English menus. https://github.com/vim/vim/commit/a1c8ecfda90c0e0e519762ae0521d7f6e297c32e
* | | | Merge #8194 from justinmk/fix-menuJustin M. Keyes2019-01-27
|\ \ \ \ | | | | | | | | | | fix ":menu Item.SubItem", fix menu_get("foo")
| * | | | menu_get(): fix query behaviorJustin M. Keyes2019-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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.
| * | | | menu_get(): Do not include empty itemsJustin M. Keyes2019-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | Caused by a typo: `dict` instead of `dic`. Renamed variable to `d` to make it less similar.
| * | | | fix ":menu Item.SubItem"Justin M. Keyes2019-01-27
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :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.
* | | | Merge #9478 from justinmk/docJustin M. Keyes2019-01-26
|\ \ \ \
| * | | | gen_api_vimdoc.py: Do not wrap on hyphens, long wordsJustin M. Keyes2019-01-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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.