116
submitted 15 hours ago by cybercitizen4@lemm.ee to c/asklemmy@lemmy.ml
top 50 comments
sorted by: hot top controversial new old
[-] Revan343@lemmy.ca 2 points 22 minutes ago

Uhhh...sudo su

Don't be like me

[-] zlatiah@lemmy.world 2 points 33 minutes ago

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

[-] kittenzrulz123@lemmy.blahaj.zone 1 points 33 minutes ago

Btop is an amazing resource monitor

[-] daq@lemmy.sdf.org 1 points 17 minutes ago

Have you tried glances?

[-] pemptago@lemmy.ml 9 points 1 hour ago

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.

[-] flambonkscious@sh.itjust.works 1 points 19 minutes ago

Holy shit, you're a madman

[-] Spider89@lemm.ee 4 points 1 hour ago
[-] LaSirena@lemmy.world 11 points 2 hours ago

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

[-] pixelscript@lemm.ee 6 points 2 hours ago

There are exactly three kinds of manpages:

  1. Way too detailed
  2. Not nearly detailed enough
  3. There is no manpage

I will take 1 any day over 2 or 3. Sometimes I even need 1, so I'm grateful for them.

But holy goddamn is it awful when I just want to use a command for aguably its most common use case and the flag or option for that is lost in a crowd of 30 other switches or buried under some modal subcommand. grep helps if you already know the switch, which isn't always.

You could argue commands like this don't have "arguably most common usecases", so manpages should be completely neutral on singling out examples. But I think the existence of tl;dr is the counterargument.

Tangent complaint: I thought the Unix philosophy was "do one thing, and do it well"? Why then do so many of these shell commands have a billion options? Mostly /s but sometimes it's flustering.

[-] SinkingLotus@lemmy.world 14 points 3 hours ago

Sudo !!

It reruns the last command as sudo.

Pretty useful since I'm always forgetting.

[-] squid_slime@lemm.ee 1 points 1 hour ago

Most commands soon followed by sudo !!

[-] pocopene@lemmy.world 4 points 2 hours ago
[-] plumcreek@lemmy.ml 3 points 2 hours ago

qmv -f do ${dir}

... for quickly moving and renaming files. The default 'qmv' opens up your preferred text editor with a list of the source and destination name of the directory of files you want to move/rename. The '-f do' tells the command we only want to see/edit the [d]estination [o]nly. If you need to rename/move a bunch of files, it's much quicker to do it in vim (at least for me).

[-] drcouzelis@lemmy.zip 1 points 2 hours ago

It sounds similar to one of my favorite commands! vidir ๐Ÿ™‚

[-] squid_slime@lemm.ee 2 points 1 hour ago

du -sh /too/bar to get size of files/folders. sudo !! inserts sudo into previous command when forgotten. yay for full system update if yay is installed. cat reads files.

[-] some_guy@lemmy.sdf.org 7 points 3 hours ago
[-] InternetCitizen2@lemmy.world 2 points 1 hour ago* (last edited 1 hour ago)

You haven't discovered exa? Noob

/s

[-] korthrun@lemmy.sdf.org 4 points 3 hours ago

Seems like an appropriate place to share https://github.com/agarrharr/awesome-cli-apps

I'm a fan of ripgrep and lsd in particular.

[-] x00za@lemmy.dbzer0.com 1 points 23 minutes ago

Big fan of lsd too.

But on a blotter

[-] umbrella@lemmy.ml 13 points 6 hours ago

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.

[-] NaevaTheRat@vegantheoryclub.org 3 points 5 hours ago* (last edited 4 hours ago)

Not a command but bang expansions. For example !? is the args of last command useful for stuff like mkdir foo ; cd !?

https://www.redhat.com/sysadmin/bash-bang-commands learn these. you suck at using your computer if you don't know them.

[-] Andromxda@lemmy.dbzer0.com 1 points 3 hours ago

Is there something similar in fish shell?

[-] Shimon@slrpnk.net 2 points 4 hours ago
[-] papertowels@lemmy.one 38 points 10 hours ago

sudo !! to rerun last command as sudo.

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

load more comments (2 replies)
[-] RagingRobot@lemmy.world 9 points 7 hours ago

CTR + u will delete the whole command. I use that a lot so I don't have to backspace. It's saved me a ton of time

[-] emergencybird@lemmy.world 2 points 1 hour ago

This is great for when you type in your root password incorrectly!

[-] darvit@lemmy.darvit.nl 1 points 1 hour ago

How about ctrl+c to cancel and clear the command you are typing? It's much easier because you only need 1 hand, and does not impact your shell's history.

[-] call_me_xale@lemmy.zip 8 points 6 hours ago

Related: Alt + ., to cycle through arguments used in previous commands

[-] sgtnasty@lemmy.ml 12 points 9 hours ago

pv (Pipe Viewer) is a command line tool to view verbose information about data streamed/piped through it. The data can be of any source like files, block devices, network streams etc. It shows the amount of data passed through, time running, progress bar, percentage and the estimated completion time.

[-] ripcord@lemmy.world 10 points 9 hours ago
[-] ace_garp@lemmy.world 3 points 1 hour ago

ls -ltrc

Show most recently modified files.

load more comments
view more: next โ€บ
this post was submitted on 21 Sep 2024
116 points (98.3% liked)

Asklemmy

43413 readers
1474 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS