Current state of compatibility with FZF's features

[LoricAndre]

This issue tracks the compatibility of sk with fzf's options.
Please comment with any missing discrepancy that you notice.

Note: even though we aim for roughly the same feature set as fzf, we do allow ourselves to implement the features differently from them.

WIP

Planned

• Missing --info types right, inline-right, etc.
• Missing event trigger binds such as load|start, eg.. --bind=load:reload(...)
• Missing actions bind|unbind to be able to rebind keys dynamically
• no scroll bar option (main fzf window)

Done

• reload action
• index tiebreak
• --tmux option
• Neovim cursorline like highlighting with --highlight-line (added with fzf v0.53) is available using sk --color 'matched_bg=#ffffff' or your preffered hex code.
• first and last actions (move to first and last line of results respectively)
• Case sensitive alt-shift binds , e.g. --bind=alt-g:first,alt-G:last

[vt-alt]

Would be nice to have --highlight-line, at least for compatibility with fzf. But this is better visibility too.

[j-lakeman]

Symlinked fzf to sk. Compatibility issues I'm still experiencing:

• joshuto: search_fzf and subdir_fzf seem frozen, pls also see possibly related Support Wildcards / Chain of Fall Backs for "Smart Search" #411
• zoxide: interactive mode gives error: unexpected value 'sharp' for '--border' found; no more were expected, pls also see Add support for skim ajeetdsouza/zoxide#228

Awesome project guys, cheers!

[LoricAndre]

Symlinked fzf to sk. Compatibility issues I'm still experiencing:

* [joshuto](https://github.com/kamiyaa/joshuto): `search_fzf` and `subdir_fzf` seem frozen, pls also see possibly related [Support Wildcards / Chain of Fall Backs for "Smart Search" #411](https://github.com/skim-rs/skim/issues/411)

* [zoxide](https://github.com/ajeetdsouza/zoxide): interactive mode gives `error: unexpected value 'sharp' for '--border' found; no more were expected`, pls also see [Add support for skim ajeetdsouza/zoxide#228](https://github.com/ajeetdsouza/zoxide/issues/228)

Awesome project guys, cheers!

The part about zoxide was an easy enough fix, it should be done with the latest version.

However, I can't reproduce the issue you're mentioning with jushuto. I've installed it, ran it and tried both :search_fzf and subdir_fzf with sk symlinked to fzf in my PATH, both ran perfectly and I jumped to the entry I selected. Would you be able to elaborate on the issue you're seing ? Which version of skim is it with ?

[LoricAndre]

Would be nice to have --highlight-line, at least for compatibility with fzf. But this is better visibility too.

Sorry for the delay about this, this feature is actually already part of skim, using sk --color 'current_bg=#ffffff' or another hex code.

[ferguscollins]

Could a feature be implemented where the visual string in the TUI can be formatted and/or truncated while keeping the fuzzy search on the entirety of the original string?

One limitation of FZF is that the searchable text is exactly what the displayed text is, i.e. there is no separation of data and visuals so the UI can not display a formatted version of the text without the text itself also being modified. The result of this is features like tables or substring display is not possible in FZF. I have not looked at the source code form skim at all, but seen as you are actively rewriting the TUI, would a feature like this be possible?

I go into more detail about what the implementation could look like in junegunn/fzf#4321, but this example encapsulates the issue in its entirety

No problems for fields with even length values.

$ cat short.csv | column -s, -t | fzf --reverse --header-lines 1 --header

H1         H2          | Edge of screen
Value1     ValueA      | Edge of screen
Value2     ValueB      | Edge of screen
Value3     ValueC      | Edge of screen

For fields with values much larger than their peers, the rest of the row gets cut off. If the columns are aligned then all rows get cut off.

H1                H2   | Edge of screen
Value1            Va...| Edge of screen
Value2            Va...| Edge of screen
ExtraLongValue3   Va...| Edge of screen
Value4            Va...| Edge of screen

A better display solution would be to trim the first column early if it's too long. These fields would be scrolled individually.

H1           H2        | Edge of screen
Value1       ValueA    | Edge of screen
Value2       ValueB    | Edge of screen
ExtraLo...   ValueC    | Edge of screen
Value4       ValueD    | Edge of screen

Setting visual tables like this by formatting the input is only possible by actually trimming the values which prevents fzf from both searching for those characters and returning them if that line is selected.

Not sure if this is where FZF related feature requests should go or not. Please let me know if I should create a separate issue with all of the details in the link instead.