mirror of
https://github.com/neovim/neovim.git
synced 2025-09-28 05:58:33 +00:00
64a14026d7
Problem: Default color scheme is suboptimal. Solution: Start using new color scheme. Introduce new `vim` color scheme for opt-in backward compatibility. ------ Main design ideas - Be "Neovim branded". - Be minimal for 256 colors with a bit more shades for true colors. - Be accessible through high enough contrast ratios. - Be suitable for dark and light backgrounds via exchange of dark and light palettes. ------ Palettes - Have dark and light variants. Implemented through exporeted `NvimDark*` and `NvimLight*` hex colors. - Palettes have 4 shades of grey for UI elements and 6 colors (red, yellow, green, cyan, blue, magenta). - Actual values are computed procedurally in Oklch color space based on a handful of hyperparameters. - Each color has a 256 colors variant with perceptually closest color. ------ Highlight groups Use: - Grey shades for general UI according to their design. - Bold text for keywords (`Statement` highlight group). This is an important choice to increase accessibility for people with color deficiencies, as it doesn't rely on actual color. - Green for strings, `DiffAdd` (as background), `DiagnosticOk`, and some minor text UI elements. - Cyan as main syntax color, i.e. for function usage (`Function` highlight group), `DiffText`, `DiagnosticInfo`, and some minor text UI elements. - Red to generally mean high user attention, i.e. errors; in particular for `ErrorMsg`, `DiffDelete`, `DiagnosticError`. - Yellow very sparingly only with true colors to mean mild user attention, i.e. warnings. That is, `DiagnosticWarn` and `WarningMsg`. - Blue very sparingly only with true colors as `DiagnosticHint` and some additional important syntax group (like `Identifier`). - Magenta very carefully (if at all). ------ Notes - To make tests work without relatively larege updates, each one is prepended with an equivalent of the call `:colorscheme vim`. Plus some tests which spawn new Neovim instances also now use 'vim' color scheme. In some cases tests are updated to fit new default color scheme.
86 lines
2.9 KiB
Lua
86 lines
2.9 KiB
Lua
local helpers = require('test.functional.helpers')(after_each)
|
|
local thelpers = require('test.functional.terminal.helpers')
|
|
local luv = require('luv')
|
|
local clear = helpers.clear
|
|
local nvim_prog = helpers.nvim_prog
|
|
local feed_command = helpers.feed_command
|
|
local feed_data = thelpers.feed_data
|
|
|
|
if helpers.skip(helpers.is_os('win')) then return end
|
|
|
|
describe('autoread TUI FocusGained/FocusLost', function()
|
|
local f1 = 'xtest-foo'
|
|
local screen
|
|
|
|
before_each(function()
|
|
clear()
|
|
screen = thelpers.screen_setup(
|
|
0,
|
|
'["'..nvim_prog..'", "-u", "NONE", "-i", "NONE", "--cmd", "colorscheme vim", "--cmd", "set noswapfile noshowcmd noruler"]'
|
|
)
|
|
end)
|
|
|
|
teardown(function()
|
|
os.remove(f1)
|
|
end)
|
|
|
|
it('external file change', function()
|
|
local path = f1
|
|
local expected_addition = [[
|
|
line 1
|
|
line 2
|
|
line 3
|
|
line 4
|
|
]]
|
|
|
|
helpers.write_file(path, '')
|
|
local atime = os.time() - 10
|
|
luv.fs_utime(path, atime, atime)
|
|
|
|
screen:expect{grid=[[
|
|
{1: } |
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{5:[No Name] }|
|
|
|
|
|
{3:-- TERMINAL --} |
|
|
]]}
|
|
feed_command('edit '..path)
|
|
screen:expect{grid=[[
|
|
{1: } |
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{5:xtest-foo }|
|
|
:edit xtest-foo |
|
|
{3:-- TERMINAL --} |
|
|
]]}
|
|
feed_data('\027[O')
|
|
feed_data('\027[O')
|
|
screen:expect{grid=[[
|
|
{1: } |
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{4:~ }|
|
|
{5:xtest-foo }|
|
|
:edit xtest-foo |
|
|
{3:-- TERMINAL --} |
|
|
]], unchanged=true}
|
|
|
|
helpers.write_file(path, expected_addition)
|
|
|
|
feed_data('\027[I')
|
|
|
|
screen:expect{grid=[[
|
|
{1:l}ine 1 |
|
|
line 2 |
|
|
line 3 |
|
|
line 4 |
|
|
{5:xtest-foo }|
|
|
"xtest-foo" 4L, 28B |
|
|
{3:-- TERMINAL --} |
|
|
]]}
|
|
end)
|
|
end)
|