Change color of filepath/filename based on file being in gitignore

[ogrish55]

Hi

I'm trying to replicate a few features from JetBrains, mainly their way of identifying files that is ignored by .gitignore pattern.

Is there a way to intercept the files populating the picker and run each file through a git check-ignore {file_path} and then adding a different color or background color to the entry in the picker, based on the result of running git check?

I would use this for live_grep, files and buffers.

[ibhagwan]

You’d need to write your custom formatted for that, take a look at the implantation of path.filename_first if you wish to do that:

fzf-lua/lua/fzf-lua/defaults.lua

Lines 255 to 280 in fc8c0e6

	_to = function(o, v)
	local _, hl_dir = utils.ansi_from_hl(o.hls.dir_part, "foo")
	local _, hl_file = utils.ansi_from_hl(o.hls.file_part, "foo")
	local v2 = tonumber(v) ~= 2 and "" or [[, "\xc2\xa0" .. string.rep(" ", 200) .. s]]
	return ([[
	return function(s, _, m)
	local _path, _utils = m.path, m.utils
	local _hl_dir = "%s"
	local _hl_file = "%s"
	local tail = _path.tail(s)
	local parent = _path.parent(s)
	if #_hl_file > 0 then
	tail = _hl_file .. tail .. _utils.ansi_escseq.clear
	end
	if parent then
	parent = _path.remove_trailing(parent)
	if #_hl_dir > 0 then
	parent = _hl_dir .. parent .. _utils.ansi_escseq.clear
	end
	return tail .. "\t" .. parent %s
	else
	return tail %s
	end
	end
	]]):format(hl_dir or "", hl_file or "", v2, v2)
	end,

[ibhagwan]

I'm at my wits end on this after having spent a lot of hours trying to make it work.
Do you have any insight in what could be wrong? If not, I'll probably resolve back to the string:find method for basic filtering.

buffers preview expects the buffer number to appear in the line inside brackets, like so [<bufnr>] <rest of line>, if you don’t wish for the bufnr to be displayed you can easily hide it with fzf_opts.--delimiter=] and fzf_opts.--with-nth=2..

[ogrish55]

Alright.. I'm just curious how vim.system({}) breaks all the pickers. Does that make sense? The only difference between the working formatter and the formatter not working, is returning the strings inside the vim.system callback function.

My knowledge of lua and async/callbacks are not skilled enough to tell what's making it break.

[ibhagwan]

Alright.. I'm just curious how vim.system({}) breaks all the pickers. Does that make sense? The only difference between the working formatter and the formatter not working, is returning the strings inside the vim.system callback function.

My knowledge of lua and async/callbacks are not skilled enough to tell what's making it break.

It might be due to neovim not allowing the call inside a coroutine / uv callback, in such case you need to run it in a vim.schedule and wait for it to finish with coroutine.yield.

[ogrish55]

Thank you for the hint. I will look into it :)

[ibhagwan]

Thank you for the hint. I will look into it :)

You can also run commands with multiprocess=false if you want to debug on the main thread so you can see exceptions, prints, etc.