formatter "path.filename_first" needs different filter than display

[Grueslayer]

Hi,

I can not get this running like (I think) it should work.

Let's assume you've following files

├───dir1
│   ├───doc
│   │       file1.txt
│   │
│   └───src
│           file1.txt
│
└───dir2
    ├───doc
    │       file1.txt
    │
    └───src
            file1.txt

and you go with files and type srcfile1 you get an empty list intead all file1.txt in all src subfolders (excluding the file1.txt in the doc subdirs)

To make this run the "right" way I think you have to make fd ( rg ) creating three columns:

1. filename
2. path
3. path+filename (like normal)

and use --with-nth = 1,2 and --nth = 3 so 1+2 are displayed and 3 is filtered.

[ibhagwan]

You're correct, currently the format of the string is "backwards", file first and then the folder which results in the behavior you're describing.

Althought what you're desribing is desireable I'd have to check if this is possible as you need a delimiter which isn't part of anywhere else in the string to make this work, you can't use a path separator or : as this will break in many cases (not limted to Windows).

[ibhagwan]

This doesn't seem possible with fzf as --with-nth doesn't preserve the match order.

echo "a/b/c/d.txt" | fzf

Now with:

 echo "a/b/c/d.txt" | fzf --delimiter="/" --with-nth="4,1..-2"

When typing the same text adtxt no results are found:

[Grueslayer]

I am thinking about something like this:

echo f.txt;a/b/c/e;a/b/c/e/f.txt; | fzf --delimiter ";" --nth 3 --with-nth "1..2"

BUT it seems --nth only supports fields included in --with-nth (junegunn/fzf#1440) so it doesn't work, too.

[ibhagwan]

I am thinking about something like this:

echo f.txt;a/b/c/e;a/b/c/e/f.txt; | fzf --delimiter ";" --nth 3 --with-nth "1..2"

BUT it seems --nth only supports fields included in --with-nth (junegunn/fzf#1440) so it doesn't work, too.

Yap I tried that as well.

[ibhagwan]

@Grueslayer, FYI, see junegunn/fzf#3854, hopefully the maintainer will consider this scenario.

[ibhagwan]

Doesn’t look like it’s gonna happen: junegunn/fzf#3854 (comment).

[ibhagwan]

@Grueslayer, with the latest commit you can now use the experimental v2 of the formatter:

:lua require("fzf-lua").files({ formatter={"path.filename_first",2} })
-- or
:FzfLua files formatter={"path.filename_first",2}
-- via setup, applied to all
:lua require("fzf-lua").setup({ defaults = { formatter={"path.filename_first",2} } })

Ref: #1255 (comment)

[Grueslayer]

@ibhagwan that seem to work much better. Highlighting of the chars matching the fuzzy word does not work if it is part of path and filename. But I think this isn’t possible without implementing it directly in fzf.

[ibhagwan]

But I think this isn’t possible without implementing it directly in fzf.

You’re correct, this is somewhat of a hack and isn’t solveable without upstream changes.

could you add the formatter to „history“, too?

Not sure what you mean, this works on all pickers where paths are constructed using make_entry.file

:FzfLua oldfiles formatter={"path.filename_first",2}