Hi!

I think this improvement could be quite useful for some users. The file picker is extended with a new property, use_absolute_paths, which simply disables the $HOME replacement with ~ when displaying paths.

I’ve been using this feature for a year already, and it has helped me a lot in scenarios where I have an absolute file path (e.g., generated by a script, linter, or any other external source) and want to open it using the file picker. By default, since all paths start with ~, the results window remains empty even if the file actually exists.

Here’s the current behavior:

1. I have an absolute file path.
2. I try to find this file using the file picker.
3. The result is empty if I search directly.

because all the paths start with ~:

The main issue is that I can’t locate a file using the path I’ve copied from a linter output in another terminal. I either have to convert the path to a relative one or configure the linter (or another tool) to generate relative paths. This can also happen when someone shares an absolute path, and you want to open that file directly.

Here’s how it works when use_absolute_paths is passed to the file picker with a value of true:

require('fzf-lua').files({
        use_absolute_paths = true,
        cmd = get_fd_cmd(), -- fd should be called with --absolute-path . to display full paths
})

Let me know your thoughts. If any other picker could benefit from the same behavior, I’d be happy to update them as well. Personally, I only use the file picker, as this is the only scenario where the issue occurs.