| blob | ab9212cb95fdeb1d754df22478b73b380ec4f460 |
1 ;;; viper-init.el --- some common definitions for Viper
3 ;; Copyright (C) 1997, 98, 99, 2000, 01, 02, 05 Free Software Foundation, Inc.
5 ;; Author: Michael Kifer <kifer@cs.stonybrook.edu>
7 ;; This file is part of GNU Emacs.
9 ;; GNU Emacs is free software; you can redistribute it and/or modify
10 ;; it under the terms of the GNU General Public License as published by
11 ;; the Free Software Foundation; either version 2, or (at your option)
12 ;; any later version.
14 ;; GNU Emacs is distributed in the hope that it will be useful,
15 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
16 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 ;; GNU General Public License for more details.
19 ;; You should have received a copy of the GNU General Public License
20 ;; along with GNU Emacs; see the file COPYING. If not, write to the
21 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
22 ;; Boston, MA 02111-1307, USA.
24 ;;; Commentary:
26 ;;; Code:
30 ;; compiler pacifier
43 ;; end pacifier
46 ;; Viper version
51 ;; Is it XEmacs?
53 ;; Is it Emacs?
55 ;; Tell whether we are running as a window application or on a TTY
57 ;; This is used to avoid compilation warnings. When emacs/xemacs forms can
58 ;; generate compile time warnings, we use this macro.
59 ;; In this case, the macro will expand into the form that is appropriate to the
60 ;; compiler at hand.
61 ;; Suggested by rms.
64 xemacs-form emacs-form))
70 window-system
71 ))
80 )
83 ;; in XEmacs: device-type is tty on tty and stream in batch.
89 "Tells if Emacs is running under an MS-style OS: ms-dos, windows-nt, W95."
94 "Tells if Emacs is running under VMS."
100 "If t, Viper will think that it is running on a display that supports faces.
101 This is provided as a temporary relief for users of graphics-capable terminals
102 that Viper doesn't know about.
103 In all likelihood, you don't need to bother with this setting."
114 \f
115 ;;; Macros
123 ;; (viper-loop COUNT BODY) Execute BODY COUNT times.
127 ,@body
133 ;; return buffer-specific macro definition, given a full macro definition
136 ;; get a pair: (curr-buffer . macro-definition)
139 ;; get macro definition for current buffer
143 ;; return mode-specific macro definitions, given a full macro definition
146 ;; get a pair: (major-mode . macro-definition)
149 ;; get macro definition for the current major mode
153 ;; return global macro definition, given a full macro definition
156 ;; get global macro definition from an elt of macro-alist
160 ;; last elt of a sequence
170 ;; like char-after/before, but saves typing
177 \f
182 \f
183 ;;; Viper minor modes
185 ;; Mode for vital things like \e, C-z.
204 "Minor mode for Ex command macros in Vi state.
205 The corresponding keymap stores key bindings of Vi macros defined with
208 ;; Mode for vital things like \e, C-z.
215 "Auxiliary minor mode for buffer-local user-defined bindings in Insert state.
216 This is a way to overshadow normal Insert mode bindings locally to certain
226 "Minor mode that simulates Vi very closely.
230 "Minor mode for Ex command macros Insert state.
231 The corresponding keymap stores key bindings of Vi macros defined with
237 ;; Mode for vital things like \C-z and \C-x) This is set to t, when viper-mode
238 ;; is invoked. So, any new buffer will have C-z defined as switch to Vi,
239 ;; unless we switched states in this buffer
243 "Minor mode for local user bindings effective in Emacs state.
244 Users can use it to override Emacs bindings when Viper is in its Emacs
248 "Minor mode for global user bindings in effect in Emacs state.
249 Users can use it to override Emacs bindings when Viper is in its Emacs
253 "Minor mode for Vi style macros in Emacs state.
254 The corresponding keymap stores key bindings of Vi macros defined with
255 `viper-record-kbd-macro' command. There is no Ex-level command to do this
259 "Minor mode used to make major-mode-specific modification to Emacs state.
260 For instance, a Vi purist may want to bind `dd' in Dired mode to a function
269 \f
271 ;; Some common error messages
286 ;; Is t until viper-mode executes for the very first time.
287 ;; Prevents recursive descend into startup messages.
291 "User's expert level.
292 The minor mode viper-vi-diehard-minor-mode is in effect when
293 viper-expert-level is 1 or 2 or when viper-want-emacs-keys-in-vi is t.
294 The minor mode viper-insert-diehard-minor-mode is in effect when
295 viper-expert-level is 1 or 2 or if viper-want-emacs-keys-in-insert is t.
298 ;; Max expert level supported by Viper. This is NOT a user option.
299 ;; It is here to make it hard for the user from resetting it.
303 ;;; ISO characters and MULE
305 ;; If non-nil, ISO accents will be turned on in insert/replace emacs states and
306 ;; turned off in vi-state. For some users, this behavior may be too
307 ;; primitive. In this case, use insert/emacs/vi state hooks.
309 ;; Set iso-accents-mode to ARG. Check if it is bound first
314 ;; Internal flag used to control when viper mule hooks are run.
315 ;; Don't change this!
317 ;; If non-nil, the default intl. input method is turned on.
320 ;; viper hook to run on input-method activation
323 ()
325 ;; turn off special input methods in vi-state
334 ))
336 ;; viper hook to run on input-method deactivation
339 ()
352 ;; XEmacs had broken quil-mode for some time, so we are working around
353 ;; it here
361 ))
368 ;; Set quail-mode to ARG
373 ;; activate input method
377 ))
380 ;; VI-style Undo
382 ;; Used to 'undo' complex commands, such as replace and insert commands.
386 ;; A mark that Viper puts on buffer-undo-list. Marks the beginning of a
387 ;; complex command that must be undone atomically. If inserted, it is
388 ;; erased by viper-change-state-to-vi and viper-repeat.
392 "*Non-nil means not to move point while undoing commands.
393 This style is different from Emacs and Vi. Try it to see if
394 it better fits your working style."
399 ;; Replace mode and changing text
401 ;; Hack used to pass global states around for short period of time
404 ;; This is used to pass the right Vi command key sequence to
405 ;; viper-set-destructive-command whenever (this-command-keys) doesn't give the
406 ;; right result. For instance, in commands like c/bla<RET>,
407 ;; (this-command-keys) will return ^M, which invoked exit-minibuffer, while we
408 ;; need "c/"
411 ;; Indicates that the current destructive command has started in replace mode.
415 "If non-nil, Viper will allow multi-line replace regions.
416 This is an extension to standard Vi.
417 If nil, commands that attempt to replace text spanning multiple lines first
418 delete the text being replaced, as in standard Vi."
423 "*Cursor color when Viper is in Replace state."
427 "Cursor color when Viper is in insert state."
431 ;; internal var, used to remember the default cursor color of emacs frames
438 "A string marking the end of replacement regions.
439 It is used only with TTYs or if `viper-use-replace-region-delimiters'
440 is non-nil."
444 "A string marking the beginning of replacement regions.
445 It is used only with TTYs or if `viper-use-replace-region-delimiters'
446 is non-nil."
452 "*If non-nil, Viper will always use `viper-replace-region-end-delimiter' and
453 `viper-replace-region-start-delimiter' to delimit replacement regions, even on
454 color displays. By default, the delimiters are used only on TTYs."
459 "Function to use for prompting the user for a buffer name."
463 ;; XEmacs requires glyphs
472 )
473 nil ; emacs
474 )
478 ;; These are local marker that must be initialized to nil and moved with
479 ;; `viper-move-marker-locally'
480 ;;
481 ;; Remember the last position inside the replace region.
483 ;; Remember the last position while inserting
491 ;; Remember the number of characters that have to be deleted in replace
492 ;; mode to compensate for the inserted characters.
494 ;; This variable is used internally by the before/after changed functions to
495 ;; determine how many chars were deleted by the change. This can't be
496 ;; determined inside after-change-functions because those get the length of the
497 ;; deleted region, not the number of chars deleted (which are two different
498 ;; things under MULE).
501 ;; Insertion ring and command ring
503 "The size of history of inserted text.
504 This is a list where Viper keeps the history of previously inserted pieces of
505 text."
508 ;; The insertion ring.
510 ;; This is temp insertion ring. Used to do rotation for display purposes.
511 ;; When rotation just started, it is initialized to viper-insertion-ring.
516 "The size of history of Vi commands repeatable with dot."
519 ;; The command ring.
521 ;; This is temp command ring. Used to do rotation for display purposes.
522 ;; When rotation just started, it is initialized to viper-command-ring.
525 ;; Fast keyseq and ESC keyseq timeouts
527 "*Key sequence separated by no more than this many milliseconds is viewed as a Vi-style macro, if such a macro is defined.
528 Setting this too high may slow down your typing. Setting this value too low
529 will make it hard to use Vi-style timeout macros."
535 "*Key sequence beginning with ESC and separated by no more than this many milliseconds is considered to be generated by a keyboard function key.
536 Setting this too high may slow down switching from insert to vi state. Setting
537 this value too low will make it impossible to use function keys in insert mode
538 on a dumb terminal."
543 "Allow translation of all key sequences into commands.
544 Normally, Viper lets Emacs translate only those ESC key sequences that are
545 defined in the low-level key-translation-map or function-key-map, such as those
547 treated as ESC command followed by a `/'. This is done for people who type fast
548 and tend to hit other characters right after they hit ESC. Other people like
549 Emacs to translate ESC sequences all the time.
550 The default is to translate all sequences only when using a dumb terminal.
551 This permits you to use ESC as a meta key in insert mode."
555 ;; Modes and related variables
557 ;; Current mode. One of: `emacs-state', `vi-state', `insert-state'
561 ;; Autoindent in insert
563 ;; Variable that keeps track of whether C-t has been pressed.
566 ;; Preserve the indent value, used by C-d in insert mode.
569 ;; Whether to preserve the indent, used by C-d in insert mode.
574 "*Enable autoindent, if t.
575 This is a buffer-local variable."
581 "*If t, electrify Viper.
582 Currently, this only electrifies auto-indentation, making it appropriate to the
583 mode of the buffer.
584 This means that auto-indentation will depart from standard Vi and will indent
585 appropriate to the mode of the buffer. This is especially useful for editing
586 programs and LaTeX documents."
591 "*The value of the shiftwidth.
592 This determines the number of columns by which the Ctl-t moves the cursor in
593 the Insert state."
597 ;; Variables for repeating destructive commands
600 "*If t, don't move point when repeating previous command.
601 This is useful for doing repeated changes with the '.' key.
602 The user can change this to nil, if she likes when the cursor moves
603 to a new place after repeating previous Vi command."
607 ;; Remember insert point as a marker. This is a local marker that must be
608 ;; initialized to nil and moved with `viper-move-marker-locally'.
612 ;; This remembers the point before dabbrev-expand was called.
613 ;; If viper-insert-point turns out to be bigger than that, it is reset
614 ;; back to viper-pre-command-point.
615 ;; The reason this is needed is because dabbrev-expand (and possibly
616 ;; others) may jump to before the insertion point, delete something and
617 ;; then reinsert a bigger piece. For instance: bla^blo
618 ;; If dabbrev-expand is called after `blo' and ^ undicates viper-insert-point,
619 ;; then point jumps to the beginning of `blo'. If expansion is found, `blablo'
620 ;; is deleted, and we have |^, where | denotes point. Next, dabbrev-expand
621 ;; will insert the expansion, and we get: blablo^
622 ;; Whatever we insert next goes before the ^, i.e., before the
623 ;; viper-insert-point marker. So, Viper will think that nothing was
624 ;; inserted. Remembering the orig position of the marker circumvents the
625 ;; problem.
626 ;; We don't know of any command, except dabbrev-expand, that has the same
627 ;; problem. However, the same trick can be used if such a command is
628 ;; discovered later.
629 ;;
633 ;; This is used for saving inserted text.
636 ;; Remembers the last replaced region.
639 ;; Remember com point as a marker.
640 ;; This is a local marker. Should be moved with `viper-move-marker-locally'
643 ;; If non-nil, the value is a list (M-COM VAL COM REG inserted-text cmd-keys)
644 ;; It is used to re-execute last destructive command.
645 ;; M-COM is a Lisp symbol representing the function to be executed.
646 ;; VAL is the prefix argument that was used with that command.
647 ;; COM is an internal descriptor, such as ?r, ?c, ?C, which contains
648 ;; additional information on how the function in M-COM is to be handled.
649 ;; REG is the register used by command
650 ;; INSERTED-TEXT is text inserted by that command (in case of o, c, C, i, r
651 ;; commands).
652 ;; COMMAND-KEYS are the keys that were typed to invoke the command.
655 ;; The character remembered by the Vi `r' command.
658 ;; Name of register to store deleted or yanked strings
662 ;;; Variables for Moves and Searches
665 "Variables that define the search and query-replace behavior of Viper."
669 ;; For use by `;' command.
672 ;; For use by `.' command.
675 ;; For use by `;' command.
678 ;; For use by `;' command.
681 ;; Last search string
685 "String inserted at the beginning of quoted region."
689 ;; If t, search is forward.
693 "*If not nil, search ignores cases."
698 "*If not nil, search is regexp search, otherwise vanilla search."
704 "*If search lands within this threshnold from the window top/bottom,
705 the window will be scrolled up or down appropriately, to reveal context.
706 If you want Viper search to behave as usual in Vi, set this variable to a
707 negative number."
712 "*If t then do regexp replace, if nil then do string replace."
718 "*If t, do regexp replace. nil means do string replace."
724 "*If t, `%' ignores the parentheses that occur inside comments."
730 "*If t, the commands l,h do not cross lines, etc (Ex-style).
731 If nil, these commands cross line boundaries."
737 "*If t, Ex-style behavior while editing in Vi command and insert states.
738 `Backspace' and `Delete' don't cross line boundaries in insert.
739 `X' and `x' can't delete characters across line boundary in Vi, etc.
740 Note: this doesn't preclude `Backspace' and `Delete' from deleting characters
741 by moving past the insertion point. This is a feature, not a bug.
743 If nil, the above commands can work across lines."
749 "*If t, ESC moves cursor back when changing from insert to vi state.
750 If nil, the cursor stays where it was when ESC was hit."
756 "*If t, DEL key will delete characters while moving the cursor backwards.
757 If nil, the cursor will move backwards without deleting anything."
762 "*Key used for buffer-searching. Must be a character type, e.g., ?g."
767 "*If t, search wraps around."
774 "*List of file and buffer names that are considered to be related to the current buffer.
775 Related buffers can be cycled through via :R and :P commands."
780 ;; Used to find out if we are done with searching the current buffer.
782 ;; As above, but global
785 ;; the search overlay
807 ;; These two vars control the interaction of jumps performed by ' and `.
808 ;; In this new version, '' doesn't erase the marks set by ``, so one can
809 ;; use both kinds of jumps interchangeably and without loosing positions
810 ;; inside the lines.
812 ;; Remembers position of the last jump done using ``'.
814 ;; Remembers position of the last jump done using `''.
817 ;; History variables
819 ;; History of search strings.
821 ;; History of query-replace strings used as a source.
823 ;; History of query-replace strings used as replacement.
825 ;; History of region quoting strings.
827 ;; History of Ex-style commands.
829 ;; History of shell commands.
833 ;; Last shell command. There are two of these, one for Ex (in viper-ex)
834 ;; and one for Vi.
836 ;; Last shell command executed with ! command.
839 \f
840 ;;; Face-saving tricks
848 "Hilighting of replace region, search pattern, minibuffer, etc."
856 "*Face used to flash out the search pattern."
858 ;; backward-compatibility alias
860 ;; An internal variable. Viper takes the face from here.
862 "Face used to flash out the search pattern.
863 DO NOT CHANGE this variable. Instead, use the customization widget
864 to customize the actual face object `viper-search-face'
872 "*Face for highlighting replace regions on a window display."
874 ;; backward-compatibility alias
876 ;; An internal variable. Viper takes the face from here.
878 "Face for highlighting replace regions on a window display.
879 DO NOT CHANGE this variable. Instead, use the customization widget
880 to customize the actual face object `viper-replace-overlay-face'
888 "Face used in the Minibuffer when it is in Emacs state."
890 ;; backward-compatibility alias
892 ;; An internal variable. Viper takes the face from here.
894 "Face used in the Minibuffer when it is in Emacs state.
895 DO NOT CHANGE this variable. Instead, use the customization widget
896 to customize the actual face object `viper-minibuffer-emacs-face'
904 "Face used in the Minibuffer when it is in Insert state."
906 ;; backward-compatibility alias
908 ;; An internal variable. Viper takes the face from here.
910 "Face used in the Minibuffer when it is in Insert state.
911 DO NOT CHANGE this variable. Instead, use the customization widget
912 to customize the actual face object `viper-minibuffer-insert-face'
920 "Face used in the Minibuffer when it is in Vi state."
922 ;; backward-compatibility alias
924 ;; An internal variable. Viper takes the face from here.
926 "Face used in the Minibuffer when it is in Vi state.
927 DO NOT CHANGE this variable. Instead, use the customization widget
928 to customize the actual face object `viper-minibuffer-vi-face'
932 ;; the current face to be used in the minibuffer
936 \f
937 ;;; Miscellaneous
943 "Spell function used by #s<move> command to spell."
948 "The tags file used by Viper."
953 "Notify the user when this many lines or characters have been deleted/yanked.
954 For line-deleting/yanking commands (like `dd', `yy'), the value denotes the
955 number of lines. For character-based commands (such as `x', `dw', etc.), the
956 value refers to the number of characters affected."
960 ;; Minibuffer
963 "If t, use vi-style editing in minibuffer.
964 Should be set in `~/.viper' file."
968 ;; overlay used in the minibuffer to indicate which state it is in
972 ;; Hook, specific to Viper, which is run just *before* exiting the minibuffer.
973 ;; This is needed because beginning with Emacs 19.26, the standard
974 ;; `minibuffer-exit-hook' is run *after* exiting the minibuffer
978 ;; Mode line
990 "Viper hooks."
995 "*Hooks run just before the switch to Vi mode is completed."
999 "*Hooks run just before the switch to Insert mode is completed."
1003 "*Hooks run just before the switch to Replace mode is completed."
1007 "*Hooks run just before the switch to Emacs mode is completed."
1012 "Hooks run just after loading Viper."
1029 ;;; Local Variables:
1030 ;;; eval: (put 'viper-deflocalvar 'lisp-indent-hook 'defun)
1031 ;;; End:
1033 ;;; arch-tag: 4efa2416-1fcb-4690-be10-1a2a0248d250
1034 ;;; viper-init.el ends here