rneovim.git/test/functional/ui/embed_spec.lua, branch tmp

refactor(ui): simplify stdin handling

2022-05-02T20:19:41+00:00

tests: fix non-controversial misuse of `pending` (#11247)

2019-10-18T02:46:30+00:00

Ref: https://github.com/neovim/neovim/pull/11184

screen: initialize screen properly with early `set display-=msgsep`

2019-09-02T10:39:03+00:00

Currently `nvim -u NORC --cmd "set display-=msgsep"` will still allocate the
message grid and remove it just afterwards. While inefficient, we must
make sure update_screen() re-validates the default_grid completely when
this happens.

Fix some invalid logic: don't reallocate msg_grid on resize when the grid is not
used.

Elide a too early ui_flush() on startup, which caused an invalid cursor
position to be used.

test/uname(): always lowercase

2019-09-02T05:49:33+00:00

test/OpenBSD: skip some tests

2019-09-02T05:49:33+00:00

Temporary workaround to unblock CI for OpenBSD.

test/ui: update tests for new msg_grid implementation

2019-09-01T13:55:10+00:00

test: clear(): remove `opts.headless` parameter

2019-04-27T14:31:26+00:00

Callers can instead specify `args_rm={'--headless'}`.

TODO: should `nvim_argv` have "--headless" by default? Need to inspect
      some uses of spawn(nvim_argv) ...

functionaltests: vim-patch:8.1.{550,551} fix

2018-12-01T04:35:36+00:00

defaults: background=dark #2894 (#9205)

2018-11-20T09:52:49+00:00

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

ui: rename ext_newgrid to ext_linegrid

2018-10-01T19:24:15+00:00