Hacker News Reader

Comment by keyle | Hacker News Reader

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="lsd --icon never -l --tree" #tree
    alias lld="lsd --icon never -l -d -a --tree" #directories tree

    alias m='micro'
    alias ss="git status"
    alias diff="git diff --color | cat"
    alias log="git log --graph --pretty=oneline --abbrev-commit"
    alias lz="lazygit"
    alias dc="docker-compose"

    # rust
    alias cr='RUST_BACKTRACE=1 cargo run'
    alias clippy='cargo clippy'
    ... many others

Soon enough, when you start piping these, you end up with your own bash language, cca. of that time you thought it was a good idea to augment C with macros (sic!)

View on HN

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.

I'm curious, how much time would you say you spend on a set of personal machines, versus connecting to random hosts?

My conceptualization of "personal computing" is something more akin to a home or a garden. It's a place where I should feel comfortable and relaxed. Familiar. It's a refuge of sorts, a place where I will inevitably spend an inordinate amount of time, and actually have a lot of real life experiences reflected (through the form of personal writing). Whether working, reading or writing, I tend to think of these machine contexts really as extensions of and foils for my mind. A discoverable mind palace, if you will.

I'm not the OP, but I'm on the same boat with the OP.

For me it's 50/50. The good thing is, when you memorize the commands, and not customize your "base stations" extensively, the difference melts away.

My brain works in "contexts". I remember my native keyboard layout and US one, and I operate in one of these contexts. Same for the spoken/written language. When I switch completely, the mental load disappears, however it's not completely free in terms of brainpower.

So, removing a context is highly beneficial. When I connect to a remote system, I don't care about the commands, aliases, even the place I'm in. Look to the hostname, remember the task I need to do and let my brain loose on the subject.

There are no roadblocks, errors or anything to think about while working. As a result the whole fleet is my home base. I change machines like I change directories. Completely effortless, invisible in fact.

Also, extensive aliasing is limiting. When I know the flags to a command, I can compose and flex on the fly, which I do a lot, as the circumstances and needs arise.

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 it to whether you are.

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.

Yes, nothing says productivity like spending half and hour to find the right flags every time you need to use something outside the most common unix userland...

or getting them subtly wrong in some production shell script...

So what you're saying that you're putting your own home-grown script wrappers from local machine to production deployment scripts?

Eshell in Emacs let's you use TRAMP to access remote systems as simply as cd'ing to the remote directory. By doing that, you have all of the features of your local shell to work on the remote system.

Awww, you can put the aliases inside your script and source it, then you can keep the aliases in prod!

You could even have your script automatically add the line to source itself to the profile, so you source it once and then it happens automatically!

Except for tar. But there I use the mnemonic “xtrackt ze files”

That may work, but I can never for the life of me remember what on earth each flag was for.

Doesn't help that '-a' basically means 'all the flags', meaning you have to know them all to figure out what on earth it's doing. Or just hope it is enough.

For tar, I have memorized: x, c, z, j, v, f

The trick with tar that people seem to have issues with is the ordering with "f" - since it takes an argument, if you're using the combined short form it has to be last with the filename immediately following.

Since a few years I only use dtrx. https://github.com/dtrx-py/dtrx/ I never have to learn this kind of stuff anymore.

Neat. Now do rsync.

tab trailing slash

  alias lsa=“grep ^alias $HOME/.zshrc | sort”

Just the “alias” command will list all your aliases, there’s no need to define a separate alias apart from convenience.

The problem is some stuff I just don’t do often enough to remember. Like clean up my old git branches.

> alias ss="git status"

ss is actually a 'socket stats' and will list all active connections while resolving their reverse dns name, be careful

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/

/bin/ss will still work.

Why should I need to write a longer command for something I routinely use, while ",[tab][tab]" would bring all my aliases/custom commands?

... then don't use the alias.

You said:

> you lose a command

I showed you how you do not lose a command. That is all.

This is what I do. I don't use aliases.

> I showed you how you do not lose a command. That is all.

I know. I understand your point, but yours is a very pedantic (sorry, was unable to find a gentler word) take on the issue.

In the heat of debugging some prod problems, the need to remember which commands are overridden by aliases and the effort required to remember full paths is an extra mental load. This is why it's better to not use aliases or be super careful, or at least prefix them with a common character is useful.

There's something called scaling cost. It's not only valid for infrastructure or software architecture. The customization you do, or the procedures you follow need to be able to scale too. I recently had to abandon Tiddly Wiki for Obsidian, because the work required to maintain that corpus of information became accidentally quadratic, and started to eat into my productivity and time. Aliases and terminal customization are also affected by this phenomena.

the swath of dns-requests from calling ss on a machine with a lot of connections can trigger rate-limiting from the dns-server which in turn can disrupt other things.

i wish this was hypothetical

thanks, I know :)

This is why I prefer community standard aliases like Oh-my-zsh. All the conflicts get caught sooner by multiple people.

Ctrl+R is nice, and was a big quality of life improvement when I first found out about it.

Recently I've found a similar improvement going from "plain old" ctrl+r for history to a set of zsh extensions plus fzf - my current set of extensions is zsh-autocomplete, zsh-autosuggestions, zsh-syntax-highlighting, zsh-history-substring-search, zsh-histdb, and fzf-histdb.

That sounds super similar my setup ( https://github.com/bbkane/dotfiles/tree/master/zsh ). I'll check out a few of those I haven't yet.

Some interesting ones there and sounds like you have a similar philosophy to me - don't customize to the point that context-switching to bash is a pain.

For tab-completion I actually prefer the builtin zsh completer set to use the menu mode - this is one of the big improvements you get with zsh over bash / etc to my mind. I have in .zshrc

  zstyle ':completion:*' menu select=2 select=long interactive

You can set it to use your ls colors with something like

  zstyle ':completion:*' list-colors ${(s.:.)LS_COLORS}"

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 my shell configuration, and I prefer the legibility of my commands/history.

history | grep in regular bash

Or ^Rpartofcommand to do an interactive history search.

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. :)

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.

I recommend it! Fish, starship.rs and `fzf` with the Ctrl+R and Alt+C keybindings continue to be my personal 80/20 for feeling comfy at the shell. Installing nvim and reloading my ~/.config using `chezmoi` gets me like 95% of the way there.

Being very obviously not Bash is a feature, not a bug, imo. It's usually pretty easy to turn Bash commands into Fish commands with the help of ChatGPT if you get stuck.

My Fish shell is pretty indistinguishable from my Zsh one but it has 5% of the config. You get amazing completion, themes, highlighting, etc out of the box.

The only plugin I use is for fzf integration because I can't live without it.

Ctrl+R is insane but sometimes I have a hard time remembering flags due to overusing it. Especially when crafting new pipelines/solving new problems.

But I'd always alias some uncommon tasks and usages. Especially my quirky git ones:

  # get default branch
  alias gdefault='git remote show origin|grep -E HEAD|cut -d" " -f5'

  # cd to git root
  alias groot='cd "$(git rev-parse --show-toplevel)"'

  # Revert last unpushed commit to the state before commiting
  alias uncommit="git reset HEAD~1 --soft"

  # Show all commits between head and main as one-liner
  alias gl1="git log --reverse --oneline HEAD...\`gdefault\`"

Funny, I was just learning about Git revision ranges the other day, to get to something like the last one! Thanks for sharing.

> Everyone does this

I disagree, experienced *nix users probably remember a TON of commands outright, after going through multiple distros/*nixes over the years.

Personally I have maybe ~30 aliases that are actually used. There's almost no point in inventing aliases that will go unused or be rapidly forgotten etc.

git has it's own alias config which I prefer to use instead. some examples: st=status, co=checkout, ci=commit, cp = cherry-pick, mod=add -u.

so that means I do 'g st' instead of 'ss', yeah, a couple extra keypresses but I'm okay with that.

Everyone is definitely not doing this. I would say the vast majority doesn't even know how to set up an alias.

How did I not know about ctrl+r? Feeling slightly more optimized

Wait until you try the `fzf` style Ctrl+R ;) total game changer for me.

> Everyone does this. Otherwise you'd go bat sh*t crazy trying to remember every intricate details of common tools.

I've got some bad news for you...

hehe same https://github.com/paprikka/dotfile-paella

Reply on news.ycombinator.com