diff options
| author | Sean Dewar <seandewar@users.noreply.github.com> | 2023-01-16 13:25:11 +0000 |
|---|---|---|
| committer | Sean Dewar <seandewar@users.noreply.github.com> | 2023-01-16 15:30:57 +0000 |
| commit | 7e24c45221b330ccf8ed3808570dab38d212ba2e (patch) | |
| tree | 2a6bc1031ea28b59ad84355d3654f6b80884f3fb /test/functional/api/vim_spec.lua | |
| parent | 60df0c06510cc65d68a2693722577d437264f67d (diff) | |
| download | rneovim-7e24c45221b330ccf8ed3808570dab38d212ba2e.tar.gz rneovim-7e24c45221b330ccf8ed3808570dab38d212ba2e.tar.bz2 rneovim-7e24c45221b330ccf8ed3808570dab38d212ba2e.zip | |
feat(health): detect tmux RGB support via `client_termfeatures`
Problem: On tmux v3.2+, the `terminal-features` option may be used to enable RGB
capabilities over `terminal-overrides`. However, `show-messages` cannot be used
to detect if RGB capabilities are enabled using `terminal-features`.
Solution: Try to use `display-message -p #{client_termfeatures}` instead.
The returned features include "RGB" if either "RGB" is set in
`terminal-features`, or if "Tc" or "RGB" is set in `terminal-overrides` (as
before).
Nothing is returned by tmux versions older than v3.2, so fallback to checking
`show-messages` in that case.
Also, un-Vimscriptify the previous logic a bit, and change the error message to
point to using the `terminal-features` option instead for newer tmux versions.
Diffstat (limited to 'test/functional/api/vim_spec.lua')
0 files changed, 0 insertions, 0 deletions