Its table of contents doesn't do it justice. this is a great deck! super dense and straightforward.
my tiny tip to contribute:
for those who could never be bothered to remember the ctrl-commands for traversing words, but are familiar with `vi`-style movements: you can go one step above the suggestion in this deck with `set -o vi`.
I'm a heavy vim user, but I still prefer the emacs-style key bindings for bash. If I want to do vim-style editing on the command line, I sometimes use Ctrl-X Ctrl-E to edit the line in my default editor (which is vim).
`.inputrc` is your friend. I have `v` (in normal mode) configured to open the line in an editor, because muscle memory sometimes makes me try to enter visual mode when editing a command.
I do the same. This might be overboard to some, but I went a step further and installed a vim plugin that brought many of the emacs-style key bindings into vim.
Thanks for the praise. The slides are kind of a summary of everything I learned here at HN over the years. Feels great to be on the front page. Definitely going to brag about it for a few years :).
> you can go one step above the suggestion in this deck with `set -o vi`
Highly recommended if you use Vim regularly (and you can define the same escape key(s) for your terminal and vim instance). For me that was one of the biggest productivity boosts when doing editing and command line work.
vi mode plus swapping my capslock and escape keys are by far the best thing I've ever done for terminal productivity. it kind of sucks on shared dev servers though.
my tiny tip to contribute:
for those who could never be bothered to remember the ctrl-commands for traversing words, but are familiar with `vi`-style movements: you can go one step above the suggestion in this deck with `set -o vi`.