diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2016-02-03 00:49:32 -0500 |
|---|---|---|
| committer | Justin M. Keyes <justinkz@gmail.com> | 2016-02-03 01:21:59 -0500 |
| commit | 79a6983c0c40c5f4ad62550c0b43ed100e862a2e (patch) | |
| tree | e0e4ae5ea2132d38f944a512947b0c83527e8958 /test/functional/eval/json_functions_spec.lua | |
| parent | 3d15cab29d2dc2448066e6b839a04d88859ab0db (diff) | |
| download | rneovim-79a6983c0c40c5f4ad62550c0b43ed100e862a2e.tar.gz rneovim-79a6983c0c40c5f4ad62550c0b43ed100e862a2e.tar.bz2 rneovim-79a6983c0c40c5f4ad62550c0b43ed100e862a2e.zip | |
ui: revert "gui_running" hack
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
Diffstat (limited to 'test/functional/eval/json_functions_spec.lua')
0 files changed, 0 insertions, 0 deletions