alias more=“less -cX”
alias moer=more
alias meor=more
alias meor=more
alias mroe=more
alias More=more

alias grpe=grep
alias gerp=grep
alias gpre=grep

A humble and simple “c” for “clear” in the terminal.

For a few basic things, yes. For a couple of others, I’ve set up a shell function or a script instead.

Obligatory warning before I list a few of my aliases - overriding commands by an alias with the same name can be dangerous, as it can mean that expected behaviour can become destructive behaviour on a foreign system without those aliases. e.g. a common error is aliasing rm to rm -i so that rm always asks if the user is sure. Until that user is on a different machine without the alias and the files vanish without warning, anyway. Oops.

Some of mine are arguably questionable in that regard, but I don’t think any will result in anything particularly destructive if I expect them in the wrong place.

These two override the default which command to deliver slightly more useful output, especially when the command is itself an alias (or an alias override). command is a bash builtin:

alias Which='command -V'
alias which='command -v'

The obligatory ls config override. long-iso formatting ensures that ls’s output is consistent, which is tidy, and also useful for further processing. That said, use of stat is probably a better choice for that sort of thing.). LC_ALL=C setting is so that things sort in “ASCIIbetical” order. My locale mixes upper and lowercase filenames and I’m too old-school for that sort of thing.:

alias ls='LC_ALL=C ls --color=auto --group-directories-first --time-style=long-iso'

Some versions of mtr start in GUI mode. -t prevents that. And of course, Windows muscle memory dies hard:

alias mtr='mtr -t'
alias tracert='echo '\''Use mtr, you ninny.'\'''

Hex dump using the ancient and nearly always present od command (the incantation is right out of the od manual):

alias odx='od -A x -t x1z -v'

Process control. Give either a PID and the process will do as it’s told. Usually. :

alias pause='kill -TSTP'
alias resume='kill -CONT'

How many times do I type the wrong thing? Too many:

alias quit='exit'

Setup for fortune. The first one is self-explanatory. The second one shows which of the fortune files the fortune came from (-c) but does some shenanigans to send that header to STDERR rather than STDOUT. This makes the header vanish when fortune is piped into fun things like cowsay.

alias bofh='fortune bofh-excuses'
alias fortune='fortune -c | while read -r line ; do [[ ! "$A" ]] && echo $line >&2 || echo $line ; [[ "$line" == "%" ]] && A=1; done'

I have a load of silly text cipher filters as scripts, but this one came for free with the bsdgames package

alias rot='caesar'
alias rot13='caesar 13'

And of course, every time I create a new alias (which isn’t very often, I admit), I run this one, which dumps all current aliases into a file that some distros set up by default.

alias save_aliases='alias > ~/.bash_aliases'

Certain aliases related to docker compose, just because it saves 2-3 words which never change.

Don’t overlook functions, they’re more versatile.

Oh boy, my time to shine:

• mkd - Create directory and immediately cd into it
• dei - docker exec -i
• dps - docker ps
• mdocker - Switch to minikube’s docker context
• n - nvim
• n. - nvim .

Node package managers

Exampes use pnpm but I have them for yarn, npm, and bun too

• pi - pnpm install
• pd - pnpm run dev

fzf stuff

• sdh - Search home directory (directories, recursive)

Meme

• fuckyou - git push --force
• nano - nvim

Misc

createpgdb - Create a postgres db on the given container with the given name

Usage: createpgdb "postgres container" "db name"

I have similar ones for dropdb and pg_dump. Here’s the command:

f() { local __user; if [ -z $3 ]; then __user=postgres; else __user=$3; fi; docker exec -i $1 createdb -U $__user $2; unset -f f; }; f'

There’s not enough storage space on the Internet to list all my aliases.

I alias most common git commands because they’re so frequent. Like co for git checkout.

alias ll = ‘ls -l’

alias kk = ‘ls -l’

alias jj = ‘ls -l’

Dyslexia sometimes hits hard.

I don’t know about your other questions but here’s my current list of aliases:

• g: git, also several git aliases in my global gitconfig, so I can type “g s” for git status e.g.
• y: yarn
• b: bun
• fu: flatpak update
• cu: checkupdates
• lg: lazygit
• n: nnn
• e: kak
• shutup: an hdparm incantation to spin down my noisy hard drive.

Also various forms of ls, like ll, la, just l, etc. (I made ls a function wrapping eza in fish shell as well. I like eza over standard ls.)

I use Nala for package management in my Debian systems. I’ve created aliases for ‘apt’ & ‘apt-get’ to use Nala instead.

Also ‘ll’ alias for ‘ls -lah’.

That’s about it though.

hgrep

history | grep

Because I can never remember what parameters to use for things so my history is a quick reference.

no, i make shell scripts for everything in /usr/local/bin/ . i find it more easy to manage and transfer. one liners can become bigger real quick, so i start with a script right away. also, since they have the shell in the hash bang line, they work in multiple shells.

I recently set up an alias since I do some hardware stuff and need to run programs not in my default path as sudo.

’alias sudop=‘sudo env PATH=$PATH’’

And that’s pretty much the extent of my aliasing. I’m interested to see what other people do

I don’t use aliases but I use bash to do common things.

“bash update” will run apt update and upgrade