Seems like a good introduction. I'm an amateur who's been using IDEs up until now. I'm just starting to become dimly aware of the power at the command line, and slowly learning in a haphazard way. This could be very helpful.
The Art of Command Line
11–20 of 134 posts
Re: The Art of Command Line
#12> To disable slow i18n routines and use traditional byte-based sort order, use export LC_ALL=C (in fact, consider putting this in your ~/.bashrc). Do not. Having a non-utf8 locale means you won't be able to handle utf-8 sanely ("that's why it's faster") and it will break at the most inexplicable times. Any non-latin1 character appearing in your prompt or command line with this will mess its spacing up for example. Do…
Some environments support a locale named "C.UTF-8" - with the same familiar sorting and formatting rules as the C locale, but with proper UTF-8 support.
Re: The Art of Command Line
#13There's no reason to learn vi if you know Emacs. If you claim that Emacs isn't installed everywhere, guess what: Neither is vi. If you want an "installed everywhere" editor, learn ed. If you're willing to take an editor with you (or otherwise make sure a specific editor is everywhere you are), there's no reason it has to be vi.
vi is a posix requirement, emacs is not. If the system you're working on has ed, it'll have some version of vi or vim as well.
and not having to know ed is an excellent reason to learn vi :)
obCompulsoryEdJoke: https://www.gnu.org/fun/jokes/ed-msg.html
Re: The Art of Command Line
#14> Fluency on the command line is a skill that is in some ways archaic...
I don't see this to be the case at all. Plus, having this be the opening line may cause people to equate archaic=I don't need this.
I'd suggest (would pull request but afk) that you remove "is a skill that is in some ways archaic".
Re: The Art of Command Line
#15If you learn bash, and you learn vi, then the next most glorious addition is:
set -o vi
Then you have vi keys in your shell. And it is marvelous.
Re: The Art of Command Line
#16I'm glad the author took time to mention sl - every sysadmin should make sure that its installed on all the boxes they manage.
Re: The Art of Command Line
#17The new csysdig curses CLI [1] unifies and replaces a bunch of the system debugging tools listed here.
[1] https://github.com/draios/sysdig/wiki/Csysdig%20Overview
Re: The Art of Command Line
#18Earlier quoted context omitted.
vi is a posix requirement, emacs is not. If the system you're working on has ed, it'll have some version of vi or vim as well.
and not having to know ed is an excellent reason to learn vi :) obCompulsoryEdJoke: https://www.gnu.org/fun/jokes/ed-msg.html
That was pretty damm amusing.
Re: The Art of Command Line
#19pretty good writeup. Learning nohup was a life changing experience for me.
Re: The Art of Command Line
#20> To disable slow i18n routines and use traditional byte-based sort order, use export LC_ALL=C (in fact, consider putting this in your ~/.bashrc). Do not. Having a non-utf8 locale means you won't be able to handle utf-8 sanely ("that's why it's faster") and it will break at the most inexplicable times. Any non-latin1 character appearing in your prompt or command line with this will mess its spacing up for example. Do…
The question is, do you need to handle UTF-8? In most cases of sever management having LATIN1 would suffice, or appropriate localized 8-byte encoding.
You can apply the same argument to any other obscure encoding scheme, not just UTF-8. The answer is really to pick the encoding which will suite the most usecases and won't be painful to use.