Mercurial > emacs
comparison man/viper.texi @ 71224:b7261e09f8e4
* cc-mode.texi (Getting Started, Indentation Commands, Config Basics)
(Custom Filling and Breaking, Custom Braces, Syntactic Symbols)
(Line-Up Functions, Custom Macros):
* ediff.texi (Window and Frame Configuration)
(Highlighting Difference Regions, Highlighting Difference Regions):
* emacs-mime.texi (Display Customization):
* erc.texi (History):
* eshell.texi (Known problems):
* eudc.texi (Overview, BBDB):
* gnus.texi (NNTP, IMAP, Advanced Scoring Examples)
(The problem of spam, SpamOracle, Extending the Spam package)
(Conformity, Terminology):
* idlwave.texi (Routine Info, Routine Info)
(Class and Keyword Inheritance, Padding Operators)
(Breakpoints and Stepping, Electric Debug Mode)
(Examining Variables, Troubleshooting):
* org.texi (Creating timestamps):
* reftex.texi (Commands, Options, Changes):
* tramp.texi (Inline methods, Password caching)
(Auto-save and Backup, Issues):
* vip.texi (Files, Commands in Insert Mode):
* viper.texi (Emacs Preliminaries, States in Viper)
(Packages that Change Keymaps, Viper Specials, Groundwork):
* xresmini.texi (GTK resources):
Fix various typos.
author | Romain Francoise <romain@orebokech.com> |
---|---|
date | Mon, 05 Jun 2006 11:44:42 +0000 |
parents | 11b616eddda4 |
children | 77266daa9ec9 a8190f7e546e |
comparison
equal
deleted
inserted
replaced
71223:31d9cfc257a4 | 71224:b7261e09f8e4 |
---|---|
234 to commands that operate on text regions, e.g., @kbd{dr} to delete region, | 234 to commands that operate on text regions, e.g., @kbd{dr} to delete region, |
235 etc. | 235 etc. |
236 | 236 |
237 Furthermore, Viper lets Ex-style commands to work on the current region. | 237 Furthermore, Viper lets Ex-style commands to work on the current region. |
238 This is done by typing a digit argument before @kbd{:}. For instance, | 238 This is done by typing a digit argument before @kbd{:}. For instance, |
239 typing @kbd{1:} will propmt you with something like @emph{:123,135}, | 239 typing @kbd{1:} will prompt you with something like @emph{:123,135}, |
240 assuming that the current region starts at line 123 and ends at line | 240 assuming that the current region starts at line 123 and ends at line |
241 135. There is no need to type the line numbers, since Viper inserts them | 241 135. There is no need to type the line numbers, since Viper inserts them |
242 automatically in front of the Ex command. | 242 automatically in front of the Ex command. |
243 | 243 |
244 @xref{Basics}, for more info.@refill | 244 @xref{Basics}, for more info.@refill |
415 search in the index. Note: to search for Ex commands in the index, you | 415 search in the index. Note: to search for Ex commands in the index, you |
416 should start them with a @kbd{:}, e.g., @kbd{:WW}. | 416 should start them with a @kbd{:}, e.g., @kbd{:WW}. |
417 | 417 |
418 In Viper, Ex commands can be made to work on the current Emacs region. | 418 In Viper, Ex commands can be made to work on the current Emacs region. |
419 This is done by typing a digit argument before @kbd{:}. | 419 This is done by typing a digit argument before @kbd{:}. |
420 For instance, typing @kbd{1:} will propmt you with something like | 420 For instance, typing @kbd{1:} will prompt you with something like |
421 @emph{:123,135}, assuming that the current region starts at line 123 and | 421 @emph{:123,135}, assuming that the current region starts at line 123 and |
422 ends at line 135. There is no need to type the line numbers, since Viper | 422 ends at line 135. There is no need to type the line numbers, since Viper |
423 inserts them automatically in front of the Ex command. | 423 inserts them automatically in front of the Ex command. |
424 | 424 |
425 @item Insert state | 425 @item Insert state |
2290 the Shell mode by changing the bindings for @kbd{C-m} and @kbd{C-d} using | 2290 the Shell mode by changing the bindings for @kbd{C-m} and @kbd{C-d} using |
2291 @code{viper-add-local-keys} described in the section on customization | 2291 @code{viper-add-local-keys} described in the section on customization |
2292 (@pxref{Customization}). | 2292 (@pxref{Customization}). |
2293 | 2293 |
2294 In some cases, some @emph{minor} modes might override certain essential | 2294 In some cases, some @emph{minor} modes might override certain essential |
2295 bindings in Vi command state. This is not a big priblem because this | 2295 bindings in Vi command state. This is not a big problem because this |
2296 can happen only in the beginning, when the minor mode kicks in. Typing | 2296 can happen only in the beginning, when the minor mode kicks in. Typing |
2297 @code{M-x viper-mode} will correct the situation. Viper knows about | 2297 @code{M-x viper-mode} will correct the situation. Viper knows about |
2298 several such minor modes and takes care of them, so the above trick | 2298 several such minor modes and takes care of them, so the above trick |
2299 is usually not necessary. If you find that some minor mode, e.g., | 2299 is usually not necessary. If you find that some minor mode, e.g., |
2300 @code{nasty-mode} interferes with Viper, putting the following in | 2300 @code{nasty-mode} interferes with Viper, putting the following in |
2668 placing this command in @code{~/.viper}: | 2668 placing this command in @code{~/.viper}: |
2669 @lisp | 2669 @lisp |
2670 (setq viper-mouse-insert-key '(meta 2)) | 2670 (setq viper-mouse-insert-key '(meta 2)) |
2671 @end lisp | 2671 @end lisp |
2672 If you want to bind mouse-insert to an action even if this action is | 2672 If you want to bind mouse-insert to an action even if this action is |
2673 already taked for other purposes in Emacs, then you should add this command | 2673 already taken for other purposes in Emacs, then you should add this command |
2674 to @code{~/.viper}, after setting @code{viper-mouse-insert-key}: | 2674 to @code{~/.viper}, after setting @code{viper-mouse-insert-key}: |
2675 @lisp | 2675 @lisp |
2676 (viper-bind-mouse-insert-key 'force) | 2676 (viper-bind-mouse-insert-key 'force) |
2677 @end lisp | 2677 @end lisp |
2678 | 2678 |
3234 C, -, h!!!} The @kbd{^} is itself, never used to indicate a | 3234 C, -, h!!!} The @kbd{^} is itself, never used to indicate a |
3235 Control character. | 3235 Control character. |
3236 | 3236 |
3237 Finally, we note that Viper's Ex-style commands can be made to work on the | 3237 Finally, we note that Viper's Ex-style commands can be made to work on the |
3238 current Emacs region. This is done by typing a digit argument before | 3238 current Emacs region. This is done by typing a digit argument before |
3239 @kbd{:}. For instance, typing @kbd{1:} will propmt you with something like | 3239 @kbd{:}. For instance, typing @kbd{1:} will prompt you with something like |
3240 @emph{:123,135}, assuming that the current region starts at line 123 and | 3240 @emph{:123,135}, assuming that the current region starts at line 123 and |
3241 ends at line 135. There is no need to type the line numbers, since Viper | 3241 ends at line 135. There is no need to type the line numbers, since Viper |
3242 inserts them automatically in front of the Ex command. | 3242 inserts them automatically in front of the Ex command. |
3243 @cindex Ex commands | 3243 @cindex Ex commands |
3244 | 3244 |