3 ms·
I have a similar system but take advantage of prefix-search rather than Ctrl+r For commands that I reuse semi-frequently I set an environment variable so that
by kevincox 5y ago
I have a similar system but take advantage of prefix-search rather than Ctrl+r
For commands that I reuse semi-frequently I set an environment variable so that I can easily find them with prefix searching. So for example I sometimes pin IPFS paths to Infura so I have this command in my history. I can then type pin=<Up> and recall that command (until it drops off the end of my shell history).
pin= r curl -fiXPOST "https://ipfs.infura.io:5001/api/v0/pin/add?recursive=true&arg=$(c)"
- boffinAudio 5y agoUseful, but dangerous! I would have to check if there is already an environment variable in use before I did that ..
- kevincox 5y agoI know this command doesn't depend on a lowercase `pin` variable so there is no danger. Note that this doesn't change the variable in the shell, just the executed command.
- boffinAudio 5y agoYeah, its the 'knowing beforehand' part that makes this dangerous for me. ;) Cute trick though, will work it into my workflow and see how it feels.
- kevincox 5y agoIDK, environment variables get set all of the time, I rarely worry about them breaking programs. Their job is kinda to live in the background and be passed through programs so it doesn't feel like much danger. Especially when I use lowercase and almost all programs use uppercase. But I guess everyone has a different risk level and what feels near-zero to me is meaningful to someone else.