81–90 of 110 posts
Earlier quoted context omitted.
Fish's autocomplete makes life a lot easier, too. It's delightfully well designed.
I head great things about Fish but I never took the dive.
The only plugin I use is for fzf integration because I can't live without it.
Earlier quoted context omitted.
I memorize the flags because it means I'm comfortable on any machine. Issue in production, and your aliases aren't there? No problem.
One could see it as the opposite: Forcing yourself to memorize flags, means you're just equally uncomfortable on any machine: that is, you haven't optimized any particular machine, especially the 1-2-3 machines you use 90% of the time with your aliases. Not to mention in 2023 on doesn't have to memorize anything to have aliases on "any machine". Have your aliases on a file (or GitHub) and just download it and source…
Earlier quoted context omitted.
Everyone does this. Otherwise you'd go bat sh*t crazy trying to remember every intricate details of common tools. also using ctrl+r and filter through older commands (ctrl+r to cycle) is also necessary for good mental health. for example alias ll="lsd --icon never -l" alias lla="lsd --icon never -l -a" # all alias llr="lsd --icon never -l -r -a" # reversed alias lls="lsd --icon never -l -r -a -S" #by size alias llt="…
I used to do this, but with fish shell unless I have very similar commands, I just type part of the whole line to something I (personally) associate it with and that’s it, that’s the command. I press a space before commands with sensitive information so they don’t stay in my history or throwaway commands that I’m 99% sure I won’t use again. Complicated ones I create a function for it, but I no longer carry aliases on…
Earlier quoted context omitted.
I used to do this, but with fish shell unless I have very similar commands, I just type part of the whole line to something I (personally) associate it with and that’s it, that’s the command. I press a space before commands with sensitive information so they don’t stay in my history or throwaway commands that I’m 99% sure I won’t use again. Complicated ones I create a function for it, but I no longer carry aliases on…
history | grep in regular bash
This is a priceless feature, which, as I keep finding out, too many people do not know about, and they waste time faffing about pressing up and down, trying to find that one command their entered ten minutes ago. :)
I think "self-optimize" is the wrong term to focus on. Imo, it's more about self-compassion / a more personal version of "psychological safety." Anecdotally, a few years ago I made a decision to run with my (ADHD driven) impulses when deciding what to spend my time on. It was difficult to let go, but I decided to let myself just fall behind with projects / work for a year or two (or until I was fired.) Long term, the…
Being aware of ADHD might initially seem like a good thing, but then it becomes a constant thing to "optimize" for. It becomes ever-present. "Could this behavior/issue/problem be my ADHD?".
Earlier quoted context omitted.
I actually find it easier to memorize the flags than to memorize the commands I created myself, because they're a lot more descriptive than short commands like in your examples. The few times I do come up with my own stuff, it's a 2+ line function (or full shell script) that can't be duplicated in a single command and can't be done as an alias.
Except for tar. But there I use the mnemonic “xtrackt ze files”
Earlier quoted context omitted.
I actually find it easier to memorize the flags than to memorize the commands I created myself, because they're a lot more descriptive than short commands like in your examples. The few times I do come up with my own stuff, it's a 2+ line function (or full shell script) that can't be duplicated in a single command and can't be done as an alias.
I memorize the flags because it means I'm comfortable on any machine. Issue in production, and your aliases aren't there? No problem.
Earlier quoted context omitted.
One could see it as the opposite: Forcing yourself to memorize flags, means you're just equally uncomfortable on any machine: that is, you haven't optimized any particular machine, especially the 1-2-3 machines you use 90% of the time with your aliases. Not to mention in 2023 on doesn't have to memorize anything to have aliases on "any machine". Have your aliases on a file (or GitHub) and just download it and source…
Optimising the addition of a few flags to a command is alin to optimising the length of variable names. I find that typing out flags gives me plenty of time to think about what I am doing anyway.
or getting them subtly wrong in some production shell script...
Earlier quoted context omitted.
Is there any harm in that?
If you're not a sysadmin or debugging your netork, no. However if you're using it for any reason, you lose a command. This is why I start my local commands with a comma (,) [0]. [0]: https://rhodesmill.org/brandon/2009/commands-with-comma/
Earlier quoted context omitted.
If you're not a sysadmin or debugging your netork, no. However if you're using it for any reason, you lose a command. This is why I start my local commands with a comma (,) [0]. [0]: https://rhodesmill.org/brandon/2009/commands-with-comma/
/bin/ss will still work.