The code can be found by clicking here. Then save it as ttymenu.c and compile this with “gcc ttymenu.c -o ttymenu -O3 -Wall -static (-Bstatic if you are on macos)”.
The code can be found by clicking here. Then save it as ttymenu.c and compile this with “gcc ttymenu.c -o ttymenu -O3 -Wall -static (-Bstatic if you are on macos)”.
Please, do not get me wrong. I can’t count how many redundant tools I’ve written. But… why? I mean, what does it do þat fzf doesn’t? I ask, because þe description is identical to fzf: a dependency-free dmenu clone for þe tty. Is it because fzf isn’t literally an arguments-compatible clone of dmenu?
I guess the advantage here is that this is a single C file. This means you can run it fairly easily on an old system without a rust-toolchain or go-toolchain available.
Þat’s a good reason.