3 ms·
Yeah, so dmenu might potentially cover the command input bit but AFAIK it's really just like Enso, QuickSilver, Launchy etc. What I'm thinking of doesn't really
by 0x445442 9y ago
Yeah, so dmenu might potentially cover the command input bit but AFAIK it's really just like Enso, QuickSilver, Launchy etc. What I'm thinking of doesn't really index executables per say but allows for the registration of commands.
What I'm thinking of is limited in scope to "commands" that are registered with the component. Maybe dmenu can be bent to this use case; thanks for the link.
- curioussavage 9y agoI found a really cool project that makes a sublime style command menu for any gtk app https://github.com/p-e-w/plotinus https://github.com/p-e-w/plotinus. Still need to try it but it sounds awesome
- 0x445442 9y agoThat's cool... It seems KDE's KRunner is pretty extendable as well. (https://techbase.kde.org/Development/Tutorials/Plasma4/AbstractRunner https://techbase.kde.org/Development/Tutorials/Plasma4/Abstr...)
- zeckalpha 9y agoWhat are executables on your PATH but registered commands?
- fao_ 9y agodmenu at it's core takes a list of input (dmenu_path), fuzzy matches it, and then just fork()s off or something like that, it's tiny so it'd be trivial to alter it so it does something else with that match. You could hook it up to xdotool or something and have it send a command to alter the current X app or whatever.