aboutsummaryrefslogtreecommitdiff
path: root/test/functional/ui/highlight_spec.lua
Commit message (Collapse)AuthorAge
* highlight: Fix missing .rgb_sp_color in initializers (#9287)Justin M. Keyes2018-11-30
| | | | | | | terminal_get_line_attributes() had this bug for a long time, though it likely had no effect visible to users. ref #9028 ref 60f845ca55a1
* diff/highlight: Fix GUI highlight for low-priority CursorLine (#9281)Justin M. Keyes2018-11-28
| | | | ref #9028 ref 0653ed63a508
* diff/highlight: Show underline for low-priority CursorLineJustin M. Keyes2018-11-27
|
* ui: disable clearing almost everywhereBjörn Linse2018-10-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid clearing the screen in most situations. NOT_VALID should be equivalent to CLEAR unless some external force messed up the terminal, for these situations <c-l> and :mode will still clear the screen. Also eliminate some obsolete code in screen.c, that dealt with that in vim drawing window 1 can mess up window 2, but this never happens in nvim. But what about slow terminals? There is two common meanings in which a terminal is said to be "slow": Most commonly (and in the sense of vim:s nottyfast) it means low bandwidth for sending bytes from nvim to the terminal. If the screen is very similar before and after the update_screen(CLEAR) this change should reduce bandwidth. If the screen is quite different, but there is no new regions of contiguous whitespace, clearing doesn't reduce bandwidth significantly. If the new screen contains a lot of whitespace, it will depend of if vsplits are used or not: as long as there is no vsplits, ce is used to cheaply clear the rest of the line, so full-screen clear is not needed to reduce bandwith. However a left vsplit currently needs to be padded with whitespace all the way to the separator. It is possible ec (clear N chars) can be used to reduce bandwidth here if this is a problem. (All of this assumes that one doesn't set Normal guibg=... on a non-BCE terminal, if you do you are doomed regardless of this change). Slow can also mean that drawing pixels on the screen is slow. E-ink screens is a recent example. Avoiding clearing and redrawing the unchanged part of the screen will always improve performance in these cases.
* Merge #9086 'vim-patch:8.1.0448'Justin M. Keyes2018-10-18
|\
| * vim-patch:8.1.0448: cursorline not removed when using 'cursorbind'Justin M. Keyes2018-10-16
| | | | | | | | | | | | Problem: Cursorline not removed when using 'cursorbind'. (Justin Keyes) Solution: Store the last cursor line per window. (closes vim/vim#3488) https://github.com/vim/vim/commit/4a5abbd6138240d109278fe1f0b45489d22f712d
* | tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|/
* shortmess+=F: Hide :bnext, :bprev fileinfo messagesJustin M. Keyes2018-09-23
|
* highlight: refactor to use stateful representationBjörn Linse2018-07-21
| | | | | This allows us to keep track of the source higlight groups, and not only the final combined highlights.
* highlight: high-priority CursorLine if fg is set. #8578Yichao Zhou2018-06-28
| | | | | | | | | | | | closes #7383 closes #7715 This implements the compromise described in #7383: * low-priority CursorLine if foreground is not set * high-priority ("same as Vim" priority) CursorLine if foreground is set ref d1874ab2821d076397290cc154d87ec2dc352c79 ref 56eda2aa17c80ba380b606f9466f288fb8162dd3
* screen: winhl=Normal:Background should not override syntax (#8093)Björn Linse2018-04-02
| | | fixes #7375
* msg: do not scroll entire screen (#8088)Björn Linse2018-03-31
|
* TUI: implement "standout" attribute #8081Nimit Bhardwaj2018-03-27
| | | | closes #8054
* 'fillchars': fix defaults logic; handle ambiwidth=double #7986Matthieu Coudron2018-02-23
| | | | Update tests.
* defaults: sidescroll=1Justin M. Keyes2018-02-09
| | | | ref #6289
* lintJustin M. Keyes2017-11-27
|
* tui: expose terminal type in 'term' optionJustin M. Keyes2017-11-27
| | | | | | | | | | Since "builtin" terminfo definitions were implemented (7cbf52db1bdf), the decisions made by tui.c and terminfo.c are more relevant. Exposing that decision in the 'term' option helps with troubleshooting. Also: remove code that allowed setting t_Co. `:set t_Co=…` has never worked; the highlight_spec test asserting that nvim_set_option('t_Co') _does_ work makes no sense, and should not have worked.
* syntax: 'cursorline': revert priority change (#7400)Justin M. Keyes2017-10-16
| | | | | ref #7383 reverts d1874ab2821d076397290cc154d87ec2dc352c79 ref #6380
* syntax: 'cursorline': low priority #6380Justin M. Keyes2017-10-07
|
* screen.c: make more highlights window specificBjörn Linse2017-06-14
|
* tests: add basic test for 'winhighlight`Björn Linse2017-05-08
|
* test: Cursor after `:hi clear|syntax reset`Justin M. Keyes2017-04-17
| | | | Also enable tests on Windows.
* functests: Replace execute with either command or feed_commandZyX2017-04-09
| | | | | | | | | | Hope this will make people using feed_command less likely: this hides bugs. Already found at least two: 1. msgpackparse() will show internal error: hash_add() in case of duplicate keys, though it will still work correctly. Currently silenced. 2. ttimeoutlen was spelled incorrectly, resulting in option not being set when expected. Test was still functioning somehow though. Currently fixed.
* 'listchars': `Whitespace` highlight group #6367Yichao Zhou2017-04-03
|
* highlight: :match should override 'list' (#6343)Yichao Zhou2017-03-26
| | | Closes #4946
* api: Establish API naming convention. (#5344)Justin M. Keyes2016-09-17
| | | | | | | | | | | | | | | | | | | | | old name: new name: -------------------------------------------------- nvim_name_to_color nvim_get_color_by_name nvim_get_current_buffer nvim_get_current_buf nvim_get_current_window nvim_get_current_win nvim_get_buffers nvim_list_bufs nvim_get_tabpages nvim_list_tabpages nvim_get_windows nvim_list_wins nvim_set_current_buffer nvim_set_current_buf nvim_set_current_window nvim_set_current_win nvim_change_directory nvim_set_current_dir nvim_tabpage_get_window nvim_tabpage_get_win nvim_tabpage_get_windows nvim_tabpage_list_wins nvim_win_get_buffer nvim_win_get_buf nvim_report_error nvim_err_writeln Helped-by: Björn Linse <bjorn.linse@gmail.com> Helped-by: ZyX <kp-pav@yandex.ru> Helped-by: James McCoy <jamessan@jamessan.com>
* Mark some functional tests as pending in WindowsRui Abreu Ferreira2016-08-26
|
* tests: don't ignore highlights in highlight_specBjörn Linse2016-08-14
|
* tests: remove deprecated hl_colorsBjörn Linse2016-08-14
|
* test/highlight_spec: Test "gui" arg of synIDattr().Justin M. Keyes2016-06-18
| | | | Also use less "regular" values for cterm colors.
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
* test/syntax: foo=NONE clears hi groupAdnoC2016-05-21
|
* test: listcharsYichao Zhou2016-05-20
|
* test: cursorline, listcharsYichao Zhou2016-05-20
|
* Merge #4633: support "special" highlight (undercurl)Justin M. Keyes2016-05-19
|\ | | | | | | | | Closes #2040 Closes #3370
| * test: Screen also checks 'special' when testing attribute equalityAdnoC2016-05-17
| |
| * test: Edit the special color testAdnoC2016-05-17
| |
| * test: Add a test for the new guisp highlighting feature.KillTheMule2016-05-17
|/ | | | Screen.lua needed a little cosmetical adjustment to print out the color nicely.
* test/syntax: Add testing for linking to cleared highlight groupsAdnoC2016-05-10
|
* vim-patch:7.4.1236pips.linux2016-04-28
| | | | | | | | | | | Problem: When "syntax manual" was used switching between buffers removes the highlighting. Solution: Set the syntax option without changing the value. (Anton Lindqvist) https://github.com/vim/vim/commit/885f24fbcae2a39ae496ffb3a1e139379be8fae1 Patch applied cleanly to the nvim sources except for version.c.
* ui: revert "gui_running" hackJustin M. Keyes2016-02-03
| | | | | | | | | | | | | | | | | | Plugins (YCM, dispatch.vim) use gui_running to decide behavior; so do some colorschemes. Up to now, nvim lied about gui_running for the benefit of colorschemes and the detriment of all _other_ plugins that check this condition. That's counterproductive: a user employs at most _one_ colorscheme but may use many other plugins which expect the Vim legacy semantics of gui_running. Moreover, colorschemes usually don't _need_ to check gui_running: they can instead set cterm{fg,bg} and gui{fg,bg} in the same :highlight call. It is reasonable for users who want "true color" to modify their colorscheme once (or request upstream to do so) in order to avoid running into quirks in any other plugins. Closes #2782
* test/functional: clean up according to luacheck (part 1)Marco Hinz2015-11-23
|
* tests/ui: Also test character at cursorBjörn Linse2015-03-09
|
* api/vim: allow guis and tests to retrieve the entire color tableBjörn Linse2015-02-02
|
* test/ui: enable strict mode by default (and in existing tests)Björn Linse2015-02-02
|
* tests/ui: strict modeBjörn Linse2015-01-23
|
* test: Add more functional test to cover new codeThiago de Arruda2015-01-15
| | | | | | | | | - emulate gui_running and terminal colors - scrolling/clearing regions - mouse wheel scrolling - setting icon/title - :stop/:suspend - screen resize
* test: Remove unnecessary command from highlight_specThiago de Arruda2015-01-13
|
* Revert "[WIP] "abstract_ui" fixes and improvements"Justin M. Keyes2015-01-12
|
* test: Remove unnecessary command from highlight_specThiago de Arruda2015-01-12
|
generated by cgit (git 2.34.1) at 2025-08-02 12:32:38 +0000