clear. Constantly, and for no reason.i’d like to introduce you to your new best friend: reset… it doesn’t everything clear does and a LOT more
haha, I can relate to that :). formerly I had the compulsion to execute sync frequently. Now my compulsion is to push Ctrl-C like 4 times every time I need it. I read somewhere that’s common because of ^C has a lack of feedback to the user, so, a script showing an alert that the clipboard received some information helped with this compulsion.
I like it so much I alised it to
c.Ctrl-L
CMD/CTRL-K for me.
Someone who doesn’t know the benefits of dedicated, unlimited scrollback buffers. This command is useful but has a bad effect (when unintentionally).
No, I do. Clearing the scrollback because I want a new, very clear start point for a new activity and don’t care about the rest is frequently the goal.
If I do care about the history I’ll do something else or possibly been saving history to disk, although that’s far more rare.
Oh. I know. But you don’t understand - I’m compelled to type it out. I must.
I used to, but the terminal clear is better, so I don’t.
Not a command as much as I press the up arrow a lot. I’m.pretty lazy and hitting the up arrow 12 times is easier then retyping a complex rsync command.
If you know it was the most recent rsync command: just type !rsync.
Laughs in fish
I actually use fish on my personal machine. But the servers I manage are pretty basic to save space and all just use stock bash.
you ever use ctrl+r ?
…I do now!
Install the fzf integration for ctrl+r fuzzy finding through your entire shell history:
Thanks friend, will do!
Neofetch
Get on with the times, install fastfetch ;)
history | fzfFzf is so useful its ridiculous. I recreated the functionality of sshs with fzf and a small bash script.
Check out the fzf docs. It ships with helpers that offer better shell integration than you’re getting here.
Awesome, didn’t know fzf yet
Since nobody has said yet, I use screen pretty heavily. Want to run a long running task, starting it from your phone? Run screen to create a detachable session then the long running command. You can then safely close out of your terminal or detach with ctrl a, d and continue in your terminal doing something else. screen -r to get back to it.
I Always forget to run screen first, so I just rely heavily on dtach
Simply change your terminal command to execute the terminal multiplexer of your choice.
man terminal_of_choice, look for (start) command.No thanks, I’m good
I recently switched to tmux and boy, it’s way better. I basically use only tmux now anymore. Creating panes to have two processes in one glance, multiple windows, awesome. Plus all the benefits of screen.
Maybe someone reading wants to now about
prefix+s. This doubles your excitement.Try zellij. Not as popular as tmux, but very intuitive to use.
How does screen / tmux work when detached from a session, how does it keep the session alive (both when running locally, and while ssh:ing to a server)? Is there a daemon involved?
You can find out by running screen and executing pstree, that way you can see how the screen process is run.
Don’t use
screen, but I do usetmuxpretty heavily.In a similar vein,
nohuplets you send tasks to the background and seems to be everywhere.You can’t mention
nohupwithout at least mentioningkill -9orpkillto slay the monster you created you madmanSometimes I’ll just reboot the entire damn machine just to be safe ;)
shutdown -r now
Eyyy, don’t hate, this is how I start all my work programs. That command is really nice and creates all work programs as children of a single terminal session for easy closing later.
No hate! Just need to make sure people know so they don’t create a bazillion threads without realizing it, or how to stop them effectively
I would know this as tmux, is there a difference?
gnu screen is just a different program than tmux. they do the same thing though
no, tmux is a newer screen. some of us havent switched cos we’re too lazy i guess? i think the common wisdom is that it’s better. i havent tried cos i already know enough of screen and it’s fine for me
Or you can learn both and spend the rest of your life trying screen commands in tmux and vice versa.
mmmmmm <3
Also, screen can connect to an UART device or serial or anything that offers up a TTY
nano
The one downvote is from the Vim user
The one downvote is from the Vim user
After using too much WINE, I type
pwd,whoamitouch😏I remember
touch
<Esc>[2J<Esc>[H
Is one of my favorites. Of course, most of you are too young to know what that means.
Is that easier than typing
clear? Also, not sure why you’d say something like that about people’s age. Anyone using terminals today is often going to run into weird quirks of them being around for decades even if they’re young.In the days before *nx, “terminal” meant a VT terminal and “clear” wasn’t a thing.
sudo
doas
Getting cheatsheets via
curl cheat.sh/INSERT_COMMAND_HERENo install necessary, Also, you can quickly search within the cheatsheets via
~. For example if you copycurl cheat.sh/ls~findwill show all the examples oflsthat usefind. If you remove~find, then it shows all examples ofls.I have a function in my bash alias for it (also piped into
morefor readability):function cht() { curl cheat.sh/"$1"?style=igor|more }tldrbecause I am too impatient to read through man pages or google the exact syntax for what I want to do.There are exactly three kinds of manpages:
- Way too detailed
- Not nearly detailed enough
- 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.
grephelps 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.
tldr is the first of 4 ways I rtfm. Then -h, man, and then the arch wiki
i never use man at all. It’s just too confusing.
I can appreciate that. Appologies if you know this already, but just don’t like them. Here are some tips.
It helps a lot to get title/subtitle/flag highlighting. By default man pages are hard to use simply because of how dense they are. It’s much easier to skim when you can separate the parts you are looking for up front from the text.
Don’t forget ‘/’, ‘n’, and ‘N’. First way to use man pages more effectively is to search them easily. And you can search via regex. Often I’m looking for more info on a particular flag. So I’ll press ‘/’ followed by ‘^ *-g’. For a g flag.
Take notes on the side. It saves you time later. Your future self will thank you. And you learn a lot by skimming them.
Man pages can be intimidating/confusing, but, imho, it’s worth training that skill. Even if you are slower up front, it’s totally worth it.
thanks for the advice. I knew about the search feature, but sometimes the stuff you need isn’t even on the page. I have no idea how to find what I need when it’s not in “man cmdname” how am I supposed to know that the feature i want has a dedicated page?
how could I find certain commands if i didn’t already know it was a shell builtin and not a command? It’s not like you get a manpage saying “this is not a command”. And even if i did have the idea to open the bash page, it’s still useless, because builtins are their own dedicated page. That sort of stuff. It rarely ever makes things easier for me.
edit, it is occasionally useful phen I have already found what I want on google and just want some more in depth details.
If something is a bash built-in run
help blahfor it’s “man page”But yeah, man pages tick me off. Wait until you learn that there are sometimes more than one per command. I have to Google which page is which because they’re all for specific things.
man foois the equivalent ofman 1 foo. What’s annoying is that the few times I’ve seen something referenced on another page the entry usually just says something like it’s on “the relevant man page” rather than just telling you exactly which.ok but that still entails trying random things until i find it. If I didn’t already know it was a builtin i wouldn’t know to search there. The bash thing was just an example. I have learned this stuff since i encountered the problem. This is just me recollecting my experience of trying to use man
Unfortunately, sometimes (often) there is no man page for what you are looking for. So if you get a page not found, that’s usually the case. You can usually find associated pages all the way at the bottom. That helps when what you are looking for isn’t a command, but a reference. I don’t remember exactly where it is, but man pages are stored in a directory. Probably /etc or /usr. You can always dump that list into fzf or use grep to search to see if there is a page for what you are looking for. It’s not a perfect system by any means, but it’s a good one to have in your toolbelt.
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.
I use this constantly
i rely on this in my job. if i really need it, i’ll be using it often enough that it’ll always be in ^R distance :)
Ctrl-r with https://github.com/atuinsh/atuin is amazing. Never forget a command you used ever again.
I trigger it with the up arrow.
shred -vzf
