The Art of Command Line
github.com
The Art of Command Line
1–10 of 134 posts
Re: The Art of Command Line
#2https://github.com/jeroenjanssens/data-science-at-the-comman...
Re: The Art of Command Line
#3Thanks for this!
Re: The Art of Command Line
#4If 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.
Re: The Art of Command Line
#5Do 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 not do not do not.
Hell I even check for it in my .zshrc: https://github.com/jleclanche/dotfiles/blob/master/.zshrc#L3...
Good post otherwise.
Re: The Art of Command Line
#6> 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…
It's not worth the "performance improvement".
Re: The Art of Command Line
#7Every time you have an issue with the shell, go there.
Re: The Art of Command Line
#8Re: The Art of Command Line
#9There'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.