A text editor is a must-have application for any operating system. We have no dearth of the best modern editors for Linux.But those are GUI based editors. But, for a lot of good reasons, you still need to utilize the command-line. This is the complete configuration that I added to my /.zshrc to get the same behavior from bash: export VISUAL=vim autoload edit-command-line; zle -N edit-command-line bindkey -M vicmd v edit-command-line.
Bash provides two modes for command line editing - emacs and vi. Emacs editing mode is the default and I already wrote an article and created a cheat sheet for this mode.
This time I am going to introduce you to bash's vi editing mode and give out a detailed cheat sheet with the default keyboard mappings for this mode.
The difference between the two modes is what command each key combination (or key) gets bound to. You may inspect your current keyboard mappings with bash's built in bind command:
Air manager 2 1 download. To get into the vi editing mode type
in your bash shell (to switch back to emacs editing mode, type set -o emacs).
If you are used to a vi text editor you will feel yourself at home. Latest version of excel.
The editing happens in two modes - command mode and insert mode. In insert mode everything you type gets output to the terminal, but in the command mode the keys are used for various commands.
Here are a few examples with screenshots to illustrate the vi editing mode.
Let '[i]' be the position of cursor in insert mode in all the examples and '[c]' be the position of cursor in command mode.
Examples:
Once you have changed the readline editing mode to vi (by typing set -o vi), you will be working in insert mode.
The example will be performed on this command:
Example 1:
Suppose you have typed a command with a few arguments and want to insert another argument before an argument which is three words backward.
Hit 'ESC' to switch to command mode and press '3' followed by 'B':
Alternatively you could have hit 'B' three times: 'BBB'.
Now, enter insert mode by hitting 'i' and type 'arg5 '
Example 2:
Suppose you wanted to change arg2 to arg5:
To do this, you can type 'cw' which means 'change word' and just type out 'arg5':
Or even quicker, you can type 'f2r5', where 'f2' moves the cursor right to next occurrence of character '2' and 'r5' replaces the character under the cursor with character '5'.
Example 3:
Suppose you typed a longer command and you noticed that you had made several mistakes, and wanted to do the correction in the vi editor itself. You can type 'v' to edit the command in the editor and not on the command line! Compress pdf preview.
Example 4:
Suppose you typed a long command and remembered that you had to execute another one before it. No need to erase the current command! You can switch to command mode by hitting ESC and then type '#' which will send the current command as a comment in the command history. After you type the command you had forgotten, you may go two commands back in history by typing 'kk' (or '2k'), erase the '#' character which was appended as a comment and execute the command, this makes the whole command look like 'ESC 2k0x ENTER'.
These are really basic examples, and it doesn't get much more complex than this. You should check out the cheat sheet for other tips and examples, and try them out!
Path finder 8 3 8. To create the cheat sheet, I downloaded bash-2.05b source code and scanned through lib/readline/vi_keymap.c source code file and lib/readline/vi_mode.c to find all the default key bindings. Bookreader mac.
It turned out that the commands documented in vi_keymap.c were all documented in man 3 readline and I didn't find anything new.
After that I checked bashline.c source file function initialize_readline to find how the default keyboard shortcuts were changed. I found that 'CTRL-e' (which switched from vi mode to emacs) got undefined, 'v' got defined which opens the existing command in the editor, and '@strong>@</strong' which replaces a macro key (char) with the corresponding string.
The cheat sheet includes:
My next post will be the definitive guide to bash history. See you then!
0 
Star