I have to admit, that -- at some time in the past -- I've even tried to activate vim mode. As a heavy vim user i thought it would make sense.
At the end I'm stuck with the Emacs-inspired (is it really Emacs?) shortcuts.
They seem to be the ones that make most sense in the short living, very interactive, shell command line:
- Arrows for going up/down one or two commands,
- ctrl-r for interactive searching in the history,
- ctrl-a for going back to the beginning of the row,
- ctrl-e to the end,
- del & and backscape for deleting a bunch of chars,
- in some case ctrl-w for deleting words backwards (mostly for deleting the url in the latest wget command),
- and, of course, tab completion.
When I'm in need for more complex interactions:
- I start vim and
- work with a mix of !! commands (shell that outputs the result in the current vim buffer),
- vim manipulations (vertical selections, ctrl-x-f, qq short living macros), A and I with a . repeat),
- join everything in a row and yank it and, finally,
- a :!ctrl-r" to run it.
When the interaction is even more complex, than it's time for a shell script.
Last resort being a Python script.
Now, why would I take the time to write `rm my-file{-01,-02,old}` and risk getting a typo into it, instead of relying on the tab-autocomplete?