I have some basic experience but I wanna be proficient and have a cli based workflow; I’m currently on Arch with GNOME
You must log in or # to comment.
deleted by creator
Linuxcommand.org is a great start
I recommend replacing GUI apps that you use one by one with CLI apps, I started by changing my file manager to ranger. Don’t rush or you may get overwhelmed and don’t interrupt your workflow too much. Next I started using media players, video editors, and even steamcmd to launch games, try to find a replacement for GUI apps searching online. This list is a good place to start;
Just start doing things using it and lookup how to do things you don’t know. Enough time and you’ll be good at it.
So there is no like FOSS course on how to be cli proficient
There are a ton of them.
Linux Journey is a good one for the basics. But I would agree with the other commentors here, and say the best thing you can do for yourself is to just use it day to day.
I once heard something about learning other languages. Your brain has two methods of learning, one is the academic, and another is practical. When you learn something purely academic, your brain isn’t prioritizing it as much, but if you’re doing it daily, and you need to be able to do it, then your brain goes “oh man, I better pick this up quick” and starts kicking more of your subconscious power into learning it. I think using the command line is going to be a similar deal.
“cli proficient” depends entirely on what you are doing, other than extremely basic stuff like learning how to use coreutils, really you just gotta try and use it whenever you can to get used to it.
The answer is that it depends what you’re doing. You can have an extremely efficient dev env CLI. You can kinda brows the web cli. You probably don’t want to edit videos and pictures in the CLI.
Because a lot of foss has replaceable building blocks, you’re not going to find a ‘this is how you do things course’. You’re much more likely to find, ‘this is how you use a certain text editor in the CLI’.
So, first, I guess, figure out or articulate what you want to do in the CLI. From reading and sending mail to writing code and building a dev environment to just basic scripting to maintain your install.
After that step, you’ll want to try a couple of the building blocks that do that.
Once you find one that kinda clicks, then you can go become proficient and start to put together the pieces of your workflow.
I run arch/Ubuntu and gnome. I spend about 50-70% of my time every day in a terminal. I spend the rest in a browser. Sometimes I use files, libre office calc, gimp or the calculator app, but even combined their usage is probably a rounding error.
I run gnome term (used to do a lot of urxvt but gnome term seems to work fine these days)
From there, I start tmux. Inside of tmux, I run a few windows. One has email, a couple shells, chat and system monitoring.
The next window has my core dev env, I run nvim with a server so I can upen tabs in nvim from different terminals, in nvim I run the lsp servers for linting and code completion. I use ranger as a file browser/previewer and that’s hooked to nvim so when I select a file there it will open as a tab in nvim, additionally I can run that file in the debug pane in the bottom of the window.
Then I just have windows that I drop into to do additional tasks, ops work on multiple servers at once, a second dev env to make a quick change in a different package, or a new window to scrape up a one line script to parse a log file or data dump for processing else where.
All of this takes time, for me about 15 years probably to say ‘ok, I want(need) to do this thing in the terminal, now what’s the best way to get that done . . .’
And then, you just kinda build it.
Learn to like not having to use your mouse. Only use your mouse as a last resort. One strength of CLI is almost never having to move your hands off of the homerow. Fuzzy finding is your friend.
For example:
- Instead of using a desktop app like GNOME, where you click on stuff to open them on a visual desktop -> Use a window manager like i3. In i3 configs, set a keyboard shortcut to fuzzy find your installed applications and open them. Now, your process for opening Firefox goes from clicking on a desktop icon or scrolling through menus, to pressing a keyboard shortcut and typing in the first few characters of Firefox and pressing enter. Desktops are bloat, you can get all of the functionality of a desktop with just the i3 rust status bar extension and CLI.
- Instead of typing out and remembering long CLI commands with a bunch of flags, use fzf to fuzzy find through your bash history. Fzf uses Ctrl-R for this, and it makes CLI interfaces much faster to navigate once you’ve already used those commands. It also makes searching files and navigating directories in CLI faster.
- Mac and Windows lack keyboard shortcuts to fully manage the layout of things on your screen. I know they have some shortcuts, but they can’t do everything without a mouse. Once again, I recommend a tiling window manager like i3 for moving tiles around, resizing, etc, all from the keyboard.
- Learn vim or similar text editors which not only use the keyboard for typing characters, but also for navigating and editing text. Instead of moving your mouse to the end character of a long word you want to delete and hitting the backspace key 20 times -> In vim, type ‘/’ and the first few characters of the word, press enter, and type ‘dw’ to delete the entire word. Vim mode is also available in bash and a bunch of extensions for other apps, you just have to configure them.
Use it everyday and you just pick things up over time, you don’t need to know everything. Make your terminal pretty colours. Fetishize about keyboards and the simplicity of plain text.
Switch to Gentoo. Either your command-line abilities will improve, or you will run screaming into the night before you manage to get X (or Wayland) up and running. 😜
Trial by fire!
Force yourself to use it. Find the things you do everyday and research how to do them in the terminal
Sure, use it to post to Lemmy.ml - there’s a nice challenge.
First thing I’d do is ditch the GUI file manager: get comfortable with cd, ls, mv, rm, etc.
After that, maybe start with basic text manipulation, like grep, awk, sort, uniq, etc. This ties in nicely with IO redirection, which is essential for a “CLI based workflow.” Get comfortable with pipes and file redirection, it’s extremely powerful!
Writing shell scripts is another super useful exercise: any time you find yourself running the same set of commands multiple times, think about making it a shell script. You may end up with some really useful little custom tools that way.
Start experimenting and break stuff. Set up some good backups and snapshots, learn how to use those well so you aren’t completely screwed when something is unrecoverable, and then go to town on all the experimental software you read about but haven’t tried. Breaking stuff will quickly make you proficient at the command line, and help you to understand how things work underneath your GUI.
And have fun!
This is a bit of a pointless question. Also, not quite making sense… because ‘workflow’ can mean absolutely anything.
I enjoy using Dolphin (KDE) because I have a terminal window at the bottom (F4 toggles it) which is tied to the GUI - so if I do ‘zi’ to jump to one of my video, or document folders, then the GUI follows… best of both worlds… and it means I can manage almost as well without the GUI, though not quite so well without the terminal.
You should aim to do things the most efficient way, without predetermined ideas about whether to use GUI or terminal. I use terminal to listen to radio, but not to edit pictures or videos.
When you get to your desktop, certainly start with a terminal open… I like Kitty - easy tabbing and splitting means I can do tons of stuff in the one window.
You learn by using, researching, and learning. That’s how you can get better. You can also do a lot by trying different shells - for example, I run Konsole (with ZSH) and Kitty with FISH - so they’re quite different to use, and each has benefits.
When i first started woking at a Unix maker… my task for my first 2 months was to know and document every file in /etc, /usr/bin/ and /bin…
After that month, my mentor ask me …
what /usr/bin/ldd does ? and show me an example.
Try to install arch without archinstall and look on the arch wiki and set up everything up in the terminal(sound, wifi, file managment, etc). When you get stuck just use google or the arch wiki(stay away from ubuntu guides bc they are usually copy and paste). If you understand the base tools try writing bash scripts to automate tasks that you do in your workflow. Good luck!
Someone already mentioned The art of command-line. It’s a start.
And just use it… you’ll get better at it with time and practice.
Also, make sure your use of the CLI enhances your workflow, or it won’t work.
My biggest suggestion is to use cli tools, read man pages, start with
man man, install info pages and use a tool liketldr.Like everything else one wants to learn, the best ist to practice and learn through finding better solution for own made failures.
