fzy VS just

> 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.

I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/just

I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.

Define your recipes and then you can compose them as needed.

[0] https://github.com/casey/just

just - https://github.com/casey/just

Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.

I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.

That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]

[0]: https://github.com/casey/just

> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin

I would consider using just for this:

https://github.com/casey/just

Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.

For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.

[1] https://github.com/casey/just

This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:

https://github.com/casey/just/issues/429

I really wish just was included as a package in distributions.

So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.

i've grown to like this for my personal projects. https://github.com/casey/just