What’s worse is making a bunch of bash aliases that are easier to remember and then you hit an environment you can’t use your bashrc in for whatever reason. Then you have no idea how to actually do anything.
I try to only use aliases for things that I repeat often but are only going to be used in my specific environment.
Unless you mean
aliasls="ls | sort -V"
Which would be really awful to do for obvious reasons.
That example is indeed what I meant. What’s awful about it?
edit: I use a customized ls alias. Most of the time it’s fine, and when I occasionally need the default output, I can type /bin/ls, no new alias to memorize. The history command suggests I do this pretty infrequently, though ymmv.
Yeah, you’re right - I was thinking of them in isolation like a silly billy
All good. I’m in a piss poor mood too and just rambling.
Its like that thing though, where you introduce someone to a new pet peeve they’ve never noticed - so thanks, I guess…
ls | sort -Vnow that I’ve cursed you.But I’m running out of mental storage space for bash commands. I wish I could clear some space.
Make a bash alias once, get the correct behavior forever.
What’s worse is making a bunch of bash aliases that are easier to remember and then you hit an environment you can’t use your bashrc in for whatever reason. Then you have no idea how to actually do anything.
I try to only use aliases for things that I repeat often but are only going to be used in my specific environment.
Unless you mean
alias ls="ls | sort -V"Which would be really awful to do for obvious reasons.
That example is indeed what I meant. What’s awful about it?
edit: I use a customized
lsalias. Most of the time it’s fine, and when I occasionally need the default output, I can type/bin/ls, no new alias to memorize. Thehistorycommand suggests I do this pretty infrequently, though ymmv.