aboutsummaryrefslogtreecommitdiff
path: root/test/functional
Commit message (Collapse)AuthorAge
* defaults: background=dark #2894 (#9205)Justin M. Keyes2018-11-20
| | | | | | | | | | | | | By historical accident, Nvim defaults to background=light. So on a dark background, `:colorscheme default` looks completely wrong. The "smart" logic that Vim uses is confusing for anyone who uses Vim on multiple platforms, so rather than mimic that, pick the (hopefully) most common default. - Since Neovim is dark-powered, we assume most users have dark backgrounds. - Most of the GUIs tend to have a dark background by default. ref #6289
* test: adjust time-sensitive tests (#9220)Justin M. Keyes2018-11-10
| | | | | | | | | | | | | - window_split_tab_spec.lua: Put cursor at bottom of :terminal buffer so that it follows output. - inccommand_spec.lua: Increase timeout to allow 2nd retry. - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms.
* Merge pull request #9211 from bfredl/init_optionsBjörn Linse2018-11-08
|\ | | | | ui_options: also send when starting in --embed mode
| * ui_options: also send when starting or from OptionSetBjörn Linse2018-11-08
| | | | | | | | needed after #9024 to receive options from init.vim
* | jobstart(): Fix hang on non-executable cwd #9204Tommy Allen2018-11-07
|/ | | | | | | * os/fs.c: add os_isdir_executable() * eval.c: fix hang on job start caused by non-executable cwd option * channel.c: assert cwd is an executable directory * test: jobstart() produces error when using non-executable cwd
* test/win: window_split_tab_spec: fix retry()Justin M. Keyes2018-11-05
|
* test/win: window_split_tab_spec: increase retry() timeJustin M. Keyes2018-11-05
| | | | The default timeout of 10s only allows 1 retry.
* test/timer_spec: relax lower-boundJustin M. Keyes2018-11-05
| | | | | | | | | | | | | Test is unreliable on macOS 10.13. The lower-bound isn't central to the purpose of the test, so just relax it. ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms. related: #6829
* test/win: retry unreliable SIGWINCH testJustin M. Keyes2018-11-04
|
* Merge pull request #9183 from bfredl/offset2Björn Linse2018-11-02
|\ | | | | api: make nvim_buf_get_offset independent on platform option
| * api: simplify nvim_buf_get_offset functionBjörn Linse2018-11-01
| |
* | Merge #7506 'deps: update libuv'Justin M. Keyes2018-11-01
|\ \ | |/ |/|
| * win: test: SIGWINCH is noisy #7506Justin M. Keyes2018-11-01
| |
* | api: implement nvim_buf_get_offset_for_lineBjörn Linse2018-11-01
|/ | | | | Like line2byte, but works for any buffer, and uses zero-based indexing (API conventions).
* functionaltest: enable job channel testJan Edmund Lazo2018-10-31
|
* functionaltest: win: enable shada FileWriteCmdJan Edmund Lazo2018-10-31
|
* functionaltest: enable buffered output testsJan Edmund Lazo2018-10-31
|
* functionaltest: enable FilterReadPre,FilterReadPost testJan Edmund Lazo2018-10-31
|
* functionaltest: win: enable diffput,diffget testJan Edmund Lazo2018-10-31
|
* functionaltests: win: enable gzip testJan Edmund Lazo2018-10-31
| | | | Close gzip file handles.
* Merge pull request #9149 from bfredl/virt_culBjörn Linse2018-10-25
|\ | | | | screen: show virt_text when 'cursorline' is set
| * screen: fix glitches with nvim_buf_set_virtual_textBjörn Linse2018-10-25
| | | | | | | | | | - virtual text disappeared when 'cursorline' was set - virtual text was shifted when emtpy line was visually selected.
* | UI: add missing redraw after enter_tabpageBjörn Linse2018-10-25
|/ | | | | | | redraw_all_later() isn't guaranteed to update must_redraw after switching tab, we must do it ourselves. fixes #9152
* Merge #9145 'CI, nodejs fixes'Justin M. Keyes2018-10-22
|\
| * test: fix/speedup scrollback_specJan Edmund Lazo2018-10-22
| | | | | | | | | | - fix: Use "set PROMPT=$" trick to satisfy screen:expect{any='%$'} - speedup: Use cmd.exe instead of powershell.
* | 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.
* api/ui: verify compatibility of UI eventsBjörn Linse2018-10-21
|
* 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
* | Merge #9124 'vim-patch:8.0.1672'Justin M. Keyes2018-10-17
|\ \
| * | functionaltest: map error does not cancel promptJan Edmund Lazo2018-10-14
| |/
* | test: Improve 008_autocommands_spec reliability (#9129)Justin M. Keyes2018-10-17
| | | | | | | | | | | | | | | | | | | | | | | | Sometimes 008_autocommands_spec fails like this: [ RUN ] autocommands that delete and unload buffers: BufUnload, VimLeave: -- Output to stderr: CMake Error at /home/travis/build/neovim/neovim/cmake/RunTests.cmake:53 (message): functional tests failed with error: 1 The final :quit + wait() is a race. Use command() instead, which is synchronous. Use command('silent! ...') everywhere else too, because it's clearer instead of feeding input and clearing the expected errors with CTRL-L.
* | tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|/
* test: adjust timer testsJustin M. Keyes2018-10-13
| | | | | Timer tests are less reliable on Travis CI macOS 10.12 (most egregious). Also somewhat on 10.13.
* Merge pull request #9121 from bfredl/virt_invalidBjörn Linse2018-10-13
|\ | | | | API: make nvim_buf_set_virtual_text handle invalid chars
| * api: make nvim_buf_set_virtual_text handle invalid charsBjörn Linse2018-10-13
| | | | | | | | | | Clients are supposed to supply only valid text, but if it is invalid, translate it rather than messing up the screen
* | signs: Add "numhl" argument #9113Reto Schnyder2018-10-13
|/ | | | | close #9113 ref #9040
* test: replace wait() with pre-assertion in assert_term_colorsBjörn Linse2018-10-06
|
* Fix crash if --embed is used more than onceJames McCoy2018-10-03
|
* ui: reserve the right to split a screen redraw into multiple batches.Björn Linse2018-10-02
|
* ui: rename ext_newgrid to ext_linegridBjörn Linse2018-10-01
|
* swapfile: Always show swap dialog (E325)Justin M. Keyes2018-09-23
| | | | | | | If swapfile dialog prompts for input, it must be displayed to the user. fix #8840 fix #9027
* shortmess+=F: Hide :bnext, :bprev fileinfo messagesJustin M. Keyes2018-09-23
|
* startup: always wait for UI with --embed, unless --headless also is suppliedBjörn Linse2018-09-22
|
* shell/logging: Fix E730 with verbose system({List}) #9009Justin M. Keyes2018-09-21
| | | | | | | | ref https://github.com/neovim/neovim/issues/9001#issuecomment-421843790 Steps to reproduce: :set verbose=9 :call system(['echo']) E730: using List as a String
* startup: don't erase screen on `:hi Normal` during startupBjörn Linse2018-09-20
| | | | | | | | | NB: existing `color default` test was actually enough to trigger the bug, when ext_newgrid=false is used. I created the `:hi Normal` test as I thought the builtin colors wouldn't set Normal (unless 'bg' is changed) But as the root cause actually comes from `:hi Normal`, it makes sense to still add the separate test (if `color default` here gets optimized to become a no-op, or something).
* test: system_spec: remove redundant clear()Justin M. Keyes2018-09-19
|
* startup: wait for embedder before executing startup commands and filesBjörn Linse2018-09-18
| | | | | | Give embeders a chance to set up nvim, by processing a request before startup. This allows an external UI to show messages and prompts from --cmd and buffer loading (e.g. swap files)
* buffer: add support for virtual text annotationsBjörn Linse2018-09-17
|
* vim-patch:8.1.0355 Incorrect adjusting the popup menu (#8996)Ronan Pigott2018-09-16
| | | | | Problem: Incorrect adjusting the popup menu for the preview window. Solution: Compute position and height properl. (Ronan Pigott) Also show at least ten items. (closes vim/vim#3414)
generated by cgit (git 2.34.1) at 2025-06-24 17:30:46 +0000