Skip to content

Commit c13fe0f

Browse files
committed
Improve checkhealth output
- Don't list all bad highlight groups, they might be too many to list. Instead tell the user how to list them - The colorscheme may not be at fault for bad highlight groups, instead they may come from plugins that define their own highlight groups. Therefore avoid naming the current colorscheme specifically.
1 parent 0fcbe14 commit c13fe0f

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

lua/tpipeline/health.lua

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,7 @@ M.check = function()
2424
end
2525

2626
if info.bad_colors > 0 then
27-
local groups = vim.fn['tpipeline#debug#get_bad_hl_groups']()
28-
local colorscheme = vim.api.nvim_exec2("colorscheme", {output = true}).output
29-
vim.health.report_warn(string.format("The colorscheme %s contains %d highlight groups that don't properly support truecolor. These colors might not render correctly in tmux.\nBad highlight groups are: %s", colorscheme, info.bad_colors, vim.inspect(groups)))
27+
vim.health.report_warn(string.format("The current colorscheme contains %d highlight groups that don't properly support truecolor.\nThese colors might not render correctly in tmux.\nYou can list them with \":echom tpipeline#debug#get_bad_hl_groups()\".", info.bad_colors))
3028
else
3129
vim.health.report_ok("Colorscheme has true color support")
3230
end

0 commit comments

Comments
 (0)