tldr is great. Basically a crowd-sourced alternative to man with much more concise entries. Example:

$ tldr dhcpcd

  DHCP client.
  More information: <https://roy.marples.name/projects/dhcpcd>.

  Release all address leases:

      sudo dhcpcd --release

  Request the DHCP server for new leases:

      sudo dhcpcd --rebind

As primarily a Windows admin (Yes, we exist on Lemmy ;) ) here are few I use often.

• Enter-PSSesion
• Get-ADUser (also group and computer)
• CLS (aka the superior clear)
• ii . (short for Invoke-Item . which runs the selected object using the default method. For paths (like .) the default is explorer, so ii . opens the current directory using explorer.)
• ft (short for Format-Table formats piped input as a table.)
• fl (short for format-like. Used like ft but for lists.)
• Where-Object
• Select-Object

cd then ls then cd then ls maybe I’ll throw a ls -a

control+R

in bash, it lets you quickly search for previously executed commands.

its very useful and makes things much quicker, i recommend you give it a try.

sudo !! to rerun last command as sudo.

history can be paired with !5 to run the fifth command listed in history.

tldr because I am too impatient to read through man pages or google the exact syntax for what I want to do.

deleted by creator

I use atuin (link) all the time

I’ve recently started using tmux when starting a new SSH session to try to build the habit.

https://github.com/tmux/tmux/wiki

I went a little overboard and wrote a one-liner to accurately answer this question

history|cut -d " " -f 5|sort|uniq -c|sort -nr|head -5

Note: history displays like this for me 20622 2023-02-18 16:41:23 ls I don’t know if that’s because I set HISTTIMEFORMAT='%F %T ' in .bashrc, or if it’s like that for everyone. If it’s different for you change -f 5 to target the command. Use -f 5-7 to include flags and arguments.

My top 5 (since last install)

   2002 ls
   1296 cd
    455 hx
    427 g
    316 find

g is an alias for gitui. When I include flags and arguments most of the top commands are aliases, often shortcuts to a project directory.

Not to ramble, but after doing this I figured I should alias the longest, most-used commands (even aliasing ls to l could have saved 2002 keystrokes :P) So I wrote another one-liner to check for available single characters to alias with:

for c in a b c d e f g h i j k l m n o p q r s t u v w x y z; do [[ ! $(command -v $c) ]] && echo $c; done

In .bash_aliases I’ve added alias b='hx ${HOME}/.bash_aliases' to quickly edit aliases and alias r='source ${HOME}/.bashrc' to reload them.

ls and cd

clear because apparently I am too scatterbrained to comprehend more than one full page of text in the terminal

sl

Sudo !!

It reruns the last command as sudo.

Pretty useful since I’m always forgetting.

I really like how nushell can parse output into it’s native structures called tables using the detect command.

Unlike string outputs, tables allow for easy data manipulation through pipes like select foo will select foo key and you can filter and even reshape the datasets.

This is great if you need to work with large data pipes like kuberneters so you can do something like:

kubectl get pods --all-namespaces | detect columns | where $it.STATUS !~ "Running|Completed" | par-each { |it| kubectl -n $it.NAMESPACE delete pod $it.NAME }

This looks complex but it parses kubectl table string to table object -> filters rows only where status is not running or completed -> executes pod delete task for each row in parallel.

Nushell take a while to learn but having real data objects in your terminal pipes is incredible! Especially with the detect command.

There’s are few more shells that do that though nu is the most mature one I’ve seen so far.