navi-tldr-pages VS ws.sh

Navi[1] is perfect for this! It's both a fuzzy finder of a personal collection of commands, but it's template syntax is flexible enough to be able to have "command builders"

I have a blog on doing exactly this for a subset of strace[2].

1: https://github.com/denisidoro/navi

2: https://kbknapp.dev/strace-navi/

navi repo add denisidoro/navi-tldr-pages Cloning https://github.com/denisidoro/navi-tldr-pages into /home//.local/share/navi/cheats/tmp... Cloning into '/home//.local/share/navi/cheats/tmp'... remote: Enumerating objects: 1841, done. remote: Counting objects: 100% (1841/1841), done. remote: Compressing objects: 100% (1756/1756), done. remote: Total 1841 (delta 83), reused 1839 (delta 83), pack-reused 0 Receiving objects: 100% (1841/1841), 504.71 KiB | 1.95 MiB/s, done. Resolving deltas: 100% (83/83), done. Hey, listen! navi encountered a problem. Do you think this is a bug? File an issue at https://github.com/denisidoro/navi. Caused by: 0: Failed to import cheatsheets from `denisidoro/navi-tldr-pages` 1: Failed to get cheatsheet files from finder 2: Failed to pass data to finder 3: Unable to prompt cheats to import 4: Broken pipe (os error 32)

I made something called shell workspaces[0] for this.

I like to tinker with bash and this has helped me keep all of the commands relevant to a particular project discoverable, accessible, and documented.

It uses a function "," for command execution. So, for instance, if the workspace file defines a function "build", when you're in the workspace, the command `$ , build` will run it.

It's not the most comprehensive solution to this, but it's probably the bit of shell programming that I use almost every day and has saved me tons of time.

[0] https://github.com/nepthar/ws.sh