Using complete_file/complete_path to generate relative paths

[FooSoft]

I'm working a lot in markdown files, and building correct relative paths for links can be very tedious. I'm hoping to use fzf-lua to help insert a relative path to a file I locate while I'm in insert mode.

I've tried the following:

1. Call complete_file with cwd set to the directory of the current buffer. This works fine for the current directory and descendants, but I'm unable to navigate to ancestor directors (to builds paths like ../../../foo.md.

2. Call complete_file with cwd set to the git root. I can browse the entire repository, but selecting a path immediately inserts it into the buffer. I was hoping to capture the path and do my fixups in lua (make the repo-relative path relative to the directory of the current buffer), but complete_file function does not appear to return the path. The fact that it updates the buffer is also a problem.

Could someone please recommend a solution here? Happy to script something custom here, but not sure how to approach this problem so far :)

[nenahp]

why dont't use blink-cmp with path/markdown-lsp source

or obsidian.nvim

[FooSoft]

I'm trying to keep a light neovim configuration without too many unnecessary plugins (I'm currently using LSP without any additional plugins). It seems like fzf-lua has all the necessary pieces, just need to figure out how to use them all together.

[ibhagwan]

The file manipulation logic is part of the complete_file options but the completion action is less than 20 lines of code:

fzf-lua/lua/fzf-lua/actions.lua

Line 1063 in 758173f

M.complete = function(selected, opts)

Replicate this code as a custom action, the manipulated file path should be the result of calling opts.complete, you’ll need to modify newline/col to your liking.

fzf-lua/lua/fzf-lua/actions.lua

Lines 1073 to 1074 in 758173f

	if type(opts.complete) == "function" then
	newline, newcol = opts.complete(selected, opts, opts.__CTX.line, col)

[FooSoft]

Thank you @ibhagwan! I will make this change for my setup.

Is there any interest for a PR? I will have to look more closely at the code, but I think it would come down to an option for preventing insertion of the result and always returning the resulting path from complete_file and complete_path. Seems like something generally useful useful :)

[ibhagwan]

Is there any interest for a PR? I will have to look more closely at the code, but I think it would come down to an option for preventing insertion of the result and always returning the resulting path from complete_file and complete_path. Seems like something generally useful useful :)

Not sure I still understand the need and I generally try to avoid adding “over customizations” as there are so many already, once you’re done link the resulting code and we can explore the use case further.

[FooSoft]

Understood completely, I'll follow up later here as a solution. Thanks again for the awesome project!

[ibhagwan]

Understood completely, I'll follow up later here as a solution. Thanks again for the awesome project!

Ty for the kind words @FooSoft, will keep an eye for your solution :)

[FooSoft]

@ibhagwan got everything working as an action without an issues, no need to change anything in fzf-lua since it provided all the tools needed to make this happen:

https://git.sr.ht/~foosoft/dotvim/tree/master/item/lua/config/plugins.lua#L65

I did notice that git_files provides a selected entry that includes what appears to be formatting characters in the callback, but I'm successfully working around this just using files. Not sure if that is unexpected, but thought I'd mention it.

[ibhagwan]

@ibhagwan got everything working as an action without an issues, no need to change anything in fzf-lua since it provided all the tools needed to make this happen:

https://git.sr.ht/~foosoft/dotvim/tree/master/item/lua/config/plugins.lua#L65

I did notice that git_files provides a selected entry that includes what appears to be formatting characters in the callback, but I'm successfully working around this just using files. Not sure if that is unexpected, but thought I'd mention it.

Two ways to work around this:

• disable git_icons, :FzfLua git_files git_icons=false
• Use _G.FzfLua.path.entry_to_file(selected[1], opts) (returns a table with parsed .path, no icons , etc).