mesamune@lemmy.world to Programming@programming.devEnglish · 12 days agoOptimize your shell experiencethoughtbot.comexternal-linkmessage-square13fedilinkarrow-up11arrow-down10cross-posted to: linux@lemmy.ml
arrow-up11arrow-down1external-linkOptimize your shell experiencethoughtbot.commesamune@lemmy.world to Programming@programming.devEnglish · 12 days agomessage-square13fedilinkcross-posted to: linux@lemmy.ml
minus-squarebad_news@lemmy.billiam.netlinkfedilinkarrow-up0·12 days agoI make ~/bin scripts that can be saved, then you have a backlog of real, backed up scripts you can add to path anywhere
minus-squareMajorHavoc@programming.devlinkfedilinkarrow-up0·12 days agoI’m an apprentice to both your ways. I create a tidy backed up script in ~/bin, and then I only ever evoke it from my bash history, because otherwise I don’t remember I had it.
minus-squareesa@discuss.tchncs.delinkfedilinkarrow-up0·11 days agoYeah, that’s what I do for complex stuff. Aliases are pretty handy too, but I use them for stuff like “v=nvim” and “vd=nvim -d”. Also one function for fd to “nvim $(rf -l $1)”
I make ~/bin scripts that can be saved, then you have a backlog of real, backed up scripts you can add to path anywhere
I’m an apprentice to both your ways.
I create a tidy backed up script in ~/bin, and then I only ever evoke it from my bash history, because otherwise I don’t remember I had it.
Yeah, that’s what I do for complex stuff. Aliases are pretty handy too, but I use them for stuff like “v=nvim” and “vd=nvim -d”. Also one function for fd to “nvim $(rf -l $1)”