for _, name in ipairs { "config", "data", "state", "cache" } do
vim.env[("XDG_%s_HOME"):format(name:upper())] = "/tmp/nvim-debug/" .. name
end
--------------------------------------------------------------------------------
local plugins = {
{
"kevinhwang91/nvim-ufo",
dependencies = "kevinhwang91/promise-async",
commit = "4afd483", -- this commit introduced the bug
-- commit = "068053c", -- this commit is still fine
opts = true,
},
{
"uga-rosa/ccc.nvim",
init = function() vim.opt.termguicolors = true end,
},
}
--------------------------------------------------------------------------------
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system {
"git",
"clone",
"--filter=blob:none",
"https://github.com/folke/lazy.nvim.git",
"--branch=stable",
lazypath,
}
end
vim.opt.runtimepath:prepend(lazypath)
require("lazy").setup(plugins)
Open a file with the config.
type something like local color = "#fff222"
Move the cursor to the color and run :CccPick
Expected behavior
Colors in the color picker should be displayed like this. (This is commit 068053c and before)
Actual behavior
The colors in the color picker are broken. This is the case since commit 4afd483.
Nothing else is broken, it is only this interaction between ufo and ccc. Since the break occurred due to a commit from ufo, I am suspecting that the problem lies on ufo's side rather than on ccc's side. (Nonetheless, I will also open a bug report at the ccc repo.)
Neovim version (nvim -v | head -n1)
NVIM v0.9.4
Operating system/version
macOS 14.1 (M1)
How to reproduce the issue
Using this minimal config:
local color = "#fff222"
:CccPick
Expected behavior
Colors in the color picker should be displayed like this. (This is commit
068053c
and before)Actual behavior
The colors in the color picker are broken. This is the case since commit
4afd483
.Nothing else is broken, it is only this interaction between ufo and ccc. Since the break occurred due to a commit from ufo, I am suspecting that the problem lies on ufo's side rather than on ccc's side. (Nonetheless, I will also open a bug report at the ccc repo.)