fzy VS zf

> it supports my keystrokes

You know that there is basically a standard set, imposed by Windows in about 1986 or something and also supported in GNOME 2, MATE, Xfce, LXDE, etc etc.? I am more interested in if it supports them. I mean, I don't know what your set are, and I am not for a moment saying there's anything wrong with them, but there are standards for this stuff, used heavily by millions of blind computer users for example.

> Have you considered the possibility you are so set in your ways that you are neglecting new and useful tool?

Could be. I am a professional assessor of, and commentator on, this stuff, though.

I mainly use a desktop I switched to in 2011. :-) Before that, I changed in 2004, after a change in 2001, after a change in 1995, after a change in 1992, after one in 1989, etc. etc.

I mean I am an old pharte, fair call, but I am a reasonably adaptable one, I think. :-D

What is "fzy"?

https://github.com/jhawthorn/fzy

...?

> Then make the panel vertical instead of horizontal

Why don't any of the screenshots show that, then?

I see 6 horizontal panels in the screenies on the homepage and Github, and one with none. From that, I don't think it's unreasonable to conclude this is not a core feature or something.

I've been mostly using fzy which is written in C. I hope skim's matching algorithm is as good as fzy's…

At the time of writing of this comment, the commit history shows that the latest commit 9aa19d3 was added on Jan 23, 2022, so I'd argue that changes are still being made, just at a slower pace.

https://github.com/jhawthorn/fzy/tree/master/src We'd just need to write a c binding to it similar to fzf-native but I don't know if anyone will be motivated enough to do it. Should take an afternoon for anyone interested and want to plug it into fussy.

Fzy: https://github.com/jhawthorn/fzy

Fzy claims to have a more refined algorithm so I switched to the telescope plugin to see if I noticed a difference before I switched my whole shell to use it. I found the native plugin to actually make my telescope unstable and lock up the editor, requiring me to nuke the entire shell so I'm back at fzf native. I'm actually planning to try telescope native since they apparently just merged a massive performance PR.

A while ago there was a post on this sub about a plugin called wilder.nvim which looks absolutely awesome. Wilder seems super configurable and it's README has a bunch of different suggested configurations. However, it is designed to work with both Vim and Neovim, but does have a config for Neovim, but it depends on kinda odd plugins like cpsm (which uses ctrlp.vim) as well as fzy.

You can absolutely make CLI tools, but be prepared for breaking changes in the language with every release. I've been working on a fuzzy finder zf for a couple of years now, and with each Zig release there are a few things to fix. It's not a ton of work, but it is something to be aware of.

I’ve absolutely had satisfaction with my several personal projects written in Zig. And based on an imperfect measurement (GitHub stars) I have also had moderate success in making something useful. It’s a terminal fuzzy finder [0]. I also maintain a Zig Lua bindings package [1], and I’m working on a port of an old Macintosh game [2].

Zig is exactly what I want out of a language though, so take my opinion with a grain of salt :)

[0]: https://github.com/natecraddock/zf

[1]: https://github.com/natecraddock/ziglua

[2]: https://github.com/natecraddock/open-reckless-drivin

This looks awesome! As someone who is already pretty invested in trouble.nvim and native integrations with Telescope and GitSigns (to name just two), what do you feel are the selling points? I wonder how you see integrations evolving too? In example, I use zf via telescope-zf-native.nvim over fzf and have had to do little to let other plugins fallback into that.

I have long preferred the strictness of the fzy algorithm over fzf for fuzzy finding both in my shell and in neovim. But there are things about fzy that have bothered me (like the inability to narrow down results with space-delimited query terms). So I have been working on zf and libzf (written in Zig if you care about that sort of thing) for the shell and integration with neovim.