- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
/
to search man pages was a gamechanger
deleted by creator
tldr is very useful
Also, knowing vim keys is useful because a lot of terminal programs use them.
Breaking things.
I’ve done this. It had the opposite effect.
Well, it’s easy… just be born in the early 80s and grow up with home micros!
For me, it was having a cool-looking and user-friendly terminal app.
How do you get a terminal app that’s cool and user-friendly? Any recommendations?
Konsole and yakuake. Bear in mind that the terminal I was comparing them to was Windows’ CMD.EXE, and anything is better than that.
Yakuake is a Quake-style terminal, which means that you can open and close it with an F-key, and it scroll down from the top of the screen. This is both cool-looking and convenient. I like to have some window transparency, so that I can see through the terminal window somewhat. I also like to use a nerd font like Fantasque Sans Mono.
Install some terminal apps
Examples:
https://github.com/clangen/musikcube
https://github.com/yorukot/superfile
This is the font I use
https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/Meslo/M-DZ
I also use ghostty because it’s themeable, I found adding transparency helped me because i can have whatever I need to see under the terminal (helps for command cheatsheets)
SuperFile looks cool, just installed it!
These do look nice 🤩 Thanks!
Kitty is also a good example ! Very customizable but maybe less user friendly to begin with.
Good cushions
What helps me is to understand what commands acronym means. For instance cp for copy, mkdir for make directory, blkid for block id, ls for list (not too sure about actual meaning for s) and so on!
Nice tips about ctrl+r to search in command history. Was not aware it existed!
pwd for password, man for mansplain, and dd for destroy disk
Hey, the first two don’t sound quite right
works for common flags too, like in
df -h
, the h stands for human readable, I always find myself mumbling “human” while typing that one‘ls’ is an abbreviation for ‘list’, not an acronym. Like copy -> cp, and the other keystroke saving abbreviations.
Step 1: Use a youtube tutorial for the basic commands. Don’t worry, you’ll forget about them soon enough. But doing them once, helps with muscle memory.
Step 2: When in need to do something, copy/paste from Q&A/forums various commands that they suggest for your problem. Your basic knowledge from step1 will come back as you do that.
After a few days, you’ll be understanding what’s going on and how the whole thing works in an abstract level.
I would recommand to never copy paste but retype so you have the commands on your finger memory.
Also don’t be afraid to
--help
everything. It give more option for commands you know quicker than theman
.
C:[Enter]
###
Maybe controversial, but the fish shell. I know it’s not strictly bash syntax, but the OOTB features are just so user-friendly. The most helpful features for learning: the autocomplete (with descriptions of subcommands and flags!) and the fuzzy history search.
I write bash scripts all the time, and am significantly more knowledgeable than anyone else on my team (admittedly frontend) because I got comfortable in fish.
I use Fish sometimes, even when I know exactly what I need to type, but just don’t feel like having to type out entire file names.
Virtual environment? Taking notes of what they did?
Anyway, tell them it’s okay you experiment and mess things up. Show them how to backup their important work. Then walk them through inevitably having to reinstall their distro.
They’ll learn that you can just keep moving forward, fixing and learning as you go.
Working in a remote environment
In my experience repetition helped. Not memorization, but more like muscle memory.
Also, ensuring to never copy and paste commands but to type them in manually yourself. It’s hard to enforce this on yourself, but worth it.
I appreciate that this article started with “ways to reduce risk” because that’s an extremely valid concern and tied to why you shouldn’t ever copy and paste. The one time in my early Linux forays where I copied and pasted I wiped the wrong drive. It definitely taught me to always manually type it in and not get too lazy, because what you copied might not match what you want to do exactly.
Also, ensuring to never copy and paste commands but to type them in manually yourself. It’s hard to enforce this on yourself, but worth it.
“Command: sido not found…”
As a fan of german rap this gave me a good chuckle. Thx.
Knowing:
- pwd, ls, cd, cat/less, cp, mv, rm, rmdir, rm -rf, ls -lah
- command --help
- man command | grep thing I care about
- bonus points if you have tldr command installed
if the avg enduser has to temper in a commandline, your program is ass.
Have someone on Google doing the thing I need to do.