| blob | 58472936c998cf42dbcdd6db74f4fa26575d606c |
1 ;;; viper-init.el --- some common definitions for Viper
3 ;; Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
4 ;; 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Free Software Foundation, Inc.
6 ;; Author: Michael Kifer <kifer@cs.stonybrook.edu>
8 ;; This file is part of GNU Emacs.
10 ;; GNU Emacs is free software: you can redistribute it and/or modify
11 ;; it under the terms of the GNU General Public License as published by
12 ;; the Free Software Foundation, either version 3 of the License, or
13 ;; (at your option) any later version.
15 ;; GNU Emacs is distributed in the hope that it will be useful,
16 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
17 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 ;; GNU General Public License for more details.
20 ;; You should have received a copy of the GNU General Public License
21 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
23 ;;; Commentary:
25 ;;; Code:
27 ;; compiler pacifier
39 ;; end pacifier
42 ;; Viper version
47 ;; Tell whether we are running as a window application or on a TTY
52 window-system))
61 ;; in XEmacs: device-type is tty on tty and stream in batch.
67 "Tells if Emacs is running under an MS-style OS: ms-dos, windows-nt, W95."
73 "If t, the message notifying about changes in the input method is not displayed.
74 Normally, a message is displayed each time on enters the vi, insert or replace
75 state."
80 "If t, Viper will think that it is running on a display that supports faces.
81 This is provided as a temporary relief for users of graphics-capable terminals
82 that Viper doesn't know about.
83 In all likelihood, you don't need to bother with this setting."
94 \f
95 ;;; Macros
103 ;; (viper-loop COUNT BODY) Execute BODY COUNT times.
107 ,@body
113 ;; return buffer-specific macro definition, given a full macro definition
116 ;; get a pair: (curr-buffer . macro-definition)
119 ;; get macro definition for current buffer
123 ;; return mode-specific macro definitions, given a full macro definition
126 ;; get a pair: (major-mode . macro-definition)
129 ;; get macro definition for the current major mode
133 ;; return global macro definition, given a full macro definition
136 ;; get global macro definition from an elt of macro-alist
140 ;; last elt of a sequence
150 ;; like char-after/before, but saves typing
157 \f
162 \f
163 ;;; Viper minor modes
165 ;; Mode for vital things like \e, C-z.
184 "Minor mode for Ex command macros in Vi state.
185 The corresponding keymap stores key bindings of Vi macros defined with
188 ;; Mode for vital things like \e, C-z.
195 "Auxiliary minor mode for buffer-local user-defined bindings in Insert state.
196 This is a way to overshadow normal Insert mode bindings locally to certain
206 "Minor mode that simulates Vi very closely.
210 "Minor mode for Ex command macros Insert state.
211 The corresponding keymap stores key bindings of Vi macros defined with
217 ;; Mode for vital things like \C-z and \C-x) This is set to t, when viper-mode
218 ;; is invoked. So, any new buffer will have C-z defined as switch to Vi,
219 ;; unless we switched states in this buffer
223 "Minor mode for local user bindings effective in Emacs state.
224 Users can use it to override Emacs bindings when Viper is in its Emacs
228 "Minor mode for global user bindings in effect in Emacs state.
229 Users can use it to override Emacs bindings when Viper is in its Emacs
233 "Minor mode for Vi style macros in Emacs state.
234 The corresponding keymap stores key bindings of Vi macros defined with
235 `viper-record-kbd-macro' command. There is no Ex-level command to do this
239 "Minor mode used to make major-mode-specific modification to Emacs state.
240 For instance, a Vi purist may want to bind `dd' in Dired mode to a function
249 \f
251 ;; Some common error messages
266 ;; Is t until viper-mode executes for the very first time.
267 ;; Prevents recursive descend into startup messages.
271 "User's expert level.
272 The minor mode viper-vi-diehard-minor-mode is in effect when
273 viper-expert-level is 1 or 2 or when viper-want-emacs-keys-in-vi is t.
274 The minor mode viper-insert-diehard-minor-mode is in effect when
275 viper-expert-level is 1 or 2 or if viper-want-emacs-keys-in-insert is t.
278 ;; Max expert level supported by Viper. This is NOT a user option.
279 ;; It is here to make it hard for the user from resetting it.
283 ;;; ISO characters and MULE
285 ;; If non-nil, ISO accents will be turned on in insert/replace emacs states and
286 ;; turned off in vi-state. For some users, this behavior may be too
287 ;; primitive. In this case, use insert/emacs/vi state hooks.
289 ;; Set iso-accents-mode to ARG. Check if it is bound first
294 ;; Internal flag used to control when viper mule hooks are run.
295 ;; Don't change this!
297 ;; If non-nil, the default intl. input method is turned on.
300 ;; viper hook to run on input-method activation
303 ()
305 ;; turn off special input methods in vi-state
315 ))
317 ;; viper hook to run on input-method deactivation
320 ()
334 ;; XEmacs had broken quail-mode for some time, so we are working around
335 ;; it here
343 ))
350 ;; Set quail-mode to ARG
355 ;; activate input method
359 ))
362 ;; VI-style Undo
364 ;; Used to 'undo' complex commands, such as replace and insert commands.
368 ;; A mark that Viper puts on buffer-undo-list. Marks the beginning of a
369 ;; complex command that must be undone atomically. If inserted, it is
370 ;; erased by viper-change-state-to-vi and viper-repeat.
374 "*Non-nil means not to move point while undoing commands.
375 This style is different from Emacs and Vi. Try it to see if
376 it better fits your working style."
381 ;; Replace mode and changing text
383 ;; Hack used to pass global states around for short period of time
386 ;; This is used to pass the right Vi command key sequence to
387 ;; viper-set-destructive-command whenever (this-command-keys) doesn't give the
388 ;; right result. For instance, in commands like c/bla<RET>,
389 ;; (this-command-keys) will return ^M, which invoked exit-minibuffer, while we
390 ;; need "c/"
393 ;; Indicates that the current destructive command has started in replace mode.
397 "If non-nil, Viper will allow multi-line replace regions.
398 This is an extension to standard Vi.
399 If nil, commands that attempt to replace text spanning multiple lines first
400 delete the text being replaced, as in standard Vi."
405 "*Cursor color when Viper is in Replace state."
410 "Cursor color when Viper is in insert state."
414 ;; viper-emacs-state-cursor-color doesn't work well. Causes cursor colors to be
415 ;; confused in some cases. So, this var is nulled for now.
416 ;; (defcustom viper-emacs-state-cursor-color "Magenta"
418 "Cursor color when Viper is in Emacs state."
422 ;; internal var, used to remember the default cursor color of emacs frames
425 ;; Frame-local variables are obsolete from Emacs 22.2 onwards, so we
426 ;; do it by hand with viper-frame-value (qv).
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 ;; These are local marker that must be initialized to nil and moved with
473 ;; `viper-move-marker-locally'
474 ;;
475 ;; Remember the last position inside the replace region.
477 ;; Remember the last position while inserting
485 ;; Remember the number of characters that have to be deleted in replace
486 ;; mode to compensate for the inserted characters.
488 ;; This variable is used internally by the before/after changed functions to
489 ;; determine how many chars were deleted by the change. This can't be
490 ;; determined inside after-change-functions because those get the length of the
491 ;; deleted region, not the number of chars deleted (which are two different
492 ;; things under MULE).
495 ;; Insertion ring and command ring
497 "The size of history of inserted text.
498 This is a list where Viper keeps the history of previously inserted pieces of
499 text."
502 ;; The insertion ring.
504 ;; This is temp insertion ring. Used to do rotation for display purposes.
505 ;; When rotation just started, it is initialized to viper-insertion-ring.
510 "The size of history of Vi commands repeatable with dot."
513 ;; The command ring.
515 ;; This is temp command ring. Used to do rotation for display purposes.
516 ;; When rotation just started, it is initialized to viper-command-ring.
519 ;; Fast keyseq and ESC keyseq timeouts
521 "*Key sequence separated by no more than this many milliseconds is viewed as a Vi-style macro, if such a macro is defined.
522 Setting this too high may slow down your typing. Setting this value too low
523 will make it hard to use Vi-style timeout macros."
527 ;; This function determines if ESC key sequences are to be translated into
528 ;; commands.
532 ;; Modes and related variables
534 ;; Current mode. One of: `emacs-state', `vi-state', `insert-state'
538 ;; Autoindent in insert
540 ;; Variable that keeps track of whether C-t has been pressed.
543 ;; Preserve the indent value, used by C-d in insert mode.
546 ;; Whether to preserve the indent, used by C-d in insert mode.
551 "*Enable autoindent, if t.
552 This is a buffer-local variable."
558 "*If t, electrify Viper.
559 Currently, this only electrifies auto-indentation, making it appropriate to the
560 mode of the buffer.
561 This means that auto-indentation will depart from standard Vi and will indent
562 appropriate to the mode of the buffer. This is especially useful for editing
563 programs and LaTeX documents."
568 "*The value of the shiftwidth.
569 This determines the number of columns by which the Ctl-t moves the cursor in
570 the Insert state."
574 ;; Variables for repeating destructive commands
577 "*If t, don't move point when repeating previous command.
578 This is useful for doing repeated changes with the '.' key.
579 The user can change this to nil, if she likes when the cursor moves
580 to a new place after repeating previous Vi command."
584 ;; Remember insert point as a marker. This is a local marker that must be
585 ;; initialized to nil and moved with `viper-move-marker-locally'.
589 ;; This remembers the point before dabbrev-expand was called.
590 ;; If viper-insert-point turns out to be bigger than that, it is reset
591 ;; back to viper-pre-command-point.
592 ;; The reason this is needed is because dabbrev-expand (and possibly
593 ;; others) may jump to before the insertion point, delete something and
594 ;; then reinsert a bigger piece. For instance: bla^blo
595 ;; If dabbrev-expand is called after `blo' and ^ undicates viper-insert-point,
596 ;; then point jumps to the beginning of `blo'. If expansion is found, `blablo'
597 ;; is deleted, and we have |^, where | denotes point. Next, dabbrev-expand
598 ;; will insert the expansion, and we get: blablo^
599 ;; Whatever we insert next goes before the ^, i.e., before the
600 ;; viper-insert-point marker. So, Viper will think that nothing was
601 ;; inserted. Remembering the orig position of the marker circumvents the
602 ;; problem.
603 ;; We don't know of any command, except dabbrev-expand, that has the same
604 ;; problem. However, the same trick can be used if such a command is
605 ;; discovered later.
606 ;;
610 ;; This is used for saving inserted text.
613 ;; Remembers the last replaced region.
616 ;; Remember com point as a marker.
617 ;; This is a local marker. Should be moved with `viper-move-marker-locally'
620 ;; If non-nil, the value is a list (M-COM VAL COM REG inserted-text cmd-keys)
621 ;; It is used to re-execute last destructive command.
622 ;; M-COM is a Lisp symbol representing the function to be executed.
623 ;; VAL is the prefix argument that was used with that command.
624 ;; COM is an internal descriptor, such as ?r, ?c, ?C, which contains
625 ;; additional information on how the function in M-COM is to be handled.
626 ;; REG is the register used by command
627 ;; INSERTED-TEXT is text inserted by that command (in case of o, c, C, i, r
628 ;; commands).
629 ;; COMMAND-KEYS are the keys that were typed to invoke the command.
632 ;; The character remembered by the Vi `r' command.
635 ;; Name of register to store deleted or yanked strings
639 ;;; Variables for Moves and Searches
642 "Variables that define the search and query-replace behavior of Viper."
646 ;; For use by `;' command.
649 ;; For use by `.' command.
652 ;; For use by `;' command.
655 ;; For use by `;' command.
658 ;; Last search string
662 "String inserted at the beginning of quoted region."
666 ;; If t, search is forward.
670 "*If not nil, search ignores cases."
675 "*If not nil, search is regexp search, otherwise vanilla search."
681 "*If search lands within this threshnold from the window top/bottom,
682 the window will be scrolled up or down appropriately, to reveal context.
683 If you want Viper search to behave as usual in Vi, set this variable to a
684 negative number."
689 "*If t then do regexp replace, if nil then do string replace."
695 "*If t, do regexp replace. nil means do string replace."
701 "*If t, `%' ignores the parentheses that occur inside comments."
707 "*If t, the commands l,h do not cross lines, etc (Ex-style).
708 If nil, these commands cross line boundaries."
714 "*If t, Ex-style behavior while editing in Vi command and insert states.
715 `Backspace' and `Delete' don't cross line boundaries in insert.
716 `X' and `x' can't delete characters across line boundary in Vi, etc.
717 Note: this doesn't preclude `Backspace' and `Delete' from deleting characters
718 by moving past the insertion point. This is a feature, not a bug.
720 If nil, the above commands can work across lines."
726 "*If t, ESC moves cursor back when changing from insert to vi state.
727 If nil, the cursor stays where it was when ESC was hit."
733 "*If t, DEL key will delete characters while moving the cursor backwards.
734 If nil, the cursor will move backwards without deleting anything."
739 "*Key used for buffer-searching. Must be a character type, e.g., ?g."
744 "*If t, search wraps around."
751 "*List of file and buffer names that are considered to be related to the current buffer.
752 Related buffers can be cycled through via :R and :P commands."
757 ;; Used to find out if we are done with searching the current buffer.
759 ;; As above, but global
762 ;; the search overlay
784 ;; These two vars control the interaction of jumps performed by ' and `.
785 ;; In this new version, '' doesn't erase the marks set by ``, so one can
786 ;; use both kinds of jumps interchangeably and without loosing positions
787 ;; inside the lines.
789 ;; Remembers position of the last jump done using ``'.
791 ;; Remembers position of the last jump done using `''.
794 ;; History variables
796 ;; History of search strings.
798 ;; History of query-replace strings used as a source.
800 ;; History of query-replace strings used as replacement.
802 ;; History of region quoting strings.
804 ;; History of Ex-style commands.
806 ;; History of shell commands.
810 ;; Last shell command. There are two of these, one for Ex (in viper-ex)
811 ;; and one for Vi.
813 ;; Last shell command executed with ! command.
816 \f
817 ;;; Face-saving tricks
820 "Hilighting of replace region, search pattern, minibuffer, etc."
828 "*Face used to flash out the search pattern."
830 ;; An internal variable. Viper takes the face from here.
832 "Face used to flash out the search pattern.
833 DO NOT CHANGE this variable. Instead, use the customization widget
834 to customize the actual face object `viper-search'
840 "*Face for highlighting replace regions on a window display."
842 ;; An internal variable. Viper takes the face from here.
844 "Face for highlighting replace regions on a window display.
845 DO NOT CHANGE this variable. Instead, use the customization widget
846 to customize the actual face object `viper-replace-overlay'
852 "Face used in the Minibuffer when it is in Emacs state."
854 ;; An internal variable. Viper takes the face from here.
856 "Face used in the Minibuffer when it is in Emacs state.
857 DO NOT CHANGE this variable. Instead, use the customization widget
858 to customize the actual face object `viper-minibuffer-emacs'
864 "Face used in the Minibuffer when it is in Insert state."
866 ;; An internal variable. Viper takes the face from here.
868 "Face used in the Minibuffer when it is in Insert state.
869 DO NOT CHANGE this variable. Instead, use the customization widget
870 to customize the actual face object `viper-minibuffer-insert'
876 "Face used in the Minibuffer when it is in Vi state."
878 ;; An internal variable. Viper takes the face from here.
880 "Face used in the Minibuffer when it is in Vi state.
881 DO NOT CHANGE this variable. Instead, use the customization widget
882 to customize the actual face object `viper-minibuffer-vi'
885 ;; the current face to be used in the minibuffer
889 \f
890 ;;; Miscellaneous
896 "Spell function used by #s<move> command to spell."
901 "The tags file used by Viper."
906 "Notify the user when this many lines or characters have been deleted/yanked.
907 For line-deleting/yanking commands (like `dd', `yy'), the value denotes the
908 number of lines. For character-based commands (such as `x', `dw', etc.), the
909 value refers to the number of characters affected."
913 ;; Minibuffer
916 "If t, use vi-style editing in minibuffer.
917 Should be set in `~/.viper' file."
921 ;; overlay used in the minibuffer to indicate which state it is in
925 ;; Hook, specific to Viper, which is run just *before* exiting the minibuffer.
926 ;; This is needed because beginning with Emacs 19.26, the standard
927 ;; `minibuffer-exit-hook' is run *after* exiting the minibuffer
931 ;; Mode line
943 "Viper hooks."
948 "*Hooks run just before the switch to Vi mode is completed."
952 "*Hooks run just before the switch to Insert mode is completed."
956 "*Hooks run just before the switch to Replace mode is completed."
960 "*Hooks run just before the switch to Emacs mode is completed."
965 "Hooks run just after loading Viper."
982 "*Key sequence beginning with ESC and separated by no more than this many milliseconds is considered to be generated by a keyboard function key.
983 Setting this too high may slow down switching from insert to vi state. Setting
984 this value too low will make it impossible to use function keys in insert mode
985 on a dumb terminal."
994 ;; Local Variables:
995 ;; eval: (put 'viper-deflocalvar 'lisp-indent-hook 'defun)
996 ;; End:
998 ;; arch-tag: 4efa2416-1fcb-4690-be10-1a2a0248d250
999 ;;; viper-init.el ends here