in which Kevin realises how difficult it is to explain how to use Linux at the command line
"I get so far and then think 'Oh, I should mention commandline completion, or aliases!' and it's a bloody mess"
—
I'm in the process of writing up Using the Linux command line, the idea being to give some basics on how to use command line efficiently and effectively, whilst not being too informationally dense. It turns out to be a larger and wider project than I initially believed. The command line has so much power, even for day-to-day use by plebs. SYadmins and developers who work with it every day recognise this power and seek mastery. For my part, mastery is a long way ff, all I really need is to use it effectively without it becoming a chore. i will therefore give an overview and create writeups to act as cheatsheets.
Part of it is that I've been working with Linux exclusively for around ten years, have absorbed a lot about how Linux works. I understand the directory structure, I know how to use vi (really vim) well enough for my purposes, I know how to use command history, aliases and brace expansion, how to use command arguments and so on, because I'm using them every day. Writing a "how-to" guide is beyond me for the reasons given above; I'm stuck in the process of deciding how much to expose a CLI noob to, and in what order. WHat was going to be a fun beginning to the CLI has become a nightmare. At what point do I introduce each element of commandline mastery?
The bggest problem is that I've been using it for so long that I have forgotten what th elearning curve even looked like for me. I remember reading countless articles on each of the elements I've mentioned, including the one that finally demystified using Vim, which was a huge leap forward in my gaining confidence to press on further.
I need your help!
So, I'm asking for your help. If you've ever needed to the the command line, on any Linux box or on MacOS, I would love to know what problems you faced, which issues came up for you, and what you wish that someone had explained to you.
I believe I've bitten off to much to include in one writeup; perhaps I need to start by breaking it up into some smaller components rather than trying for One Node to Rule Them All. So, I need your suggestions and experiences so that I can approach the project more intelligently and produce something of value.
Please pm me or email (my username at pm.me) with your experiences or any thoughts you have, I really would love to get your thoughts.
Meanwhile…
As if I needed another new project, I have decided to install Linux From Scratch, so that I can understand even more how it all works. I have put the book on my wishlist and hope to get around to buying it for myself, along with a new 10-inch rackmount server setup, once i am up to date with rent.
_____________________________________
/ Today is Pungenday, the 25th day of \
\ Discord in the YOLD 3191 /
-------------------------------------
\
\
.--.
|o_o |
|:_/ |
// \ \
(| | )
/'\_ _/`\
\___)=(___/
$ xclip -o | wc -w
520