Lines Matching +refs:switch +refs:to +refs:minibuffer
6 Use Ctrl-D and Ctrl-U to scroll through this help information.
8 Type Ctrl-O to make this the only window on the screen. Type Ctrl-K to get
11 First, to leave vile, use any of the following:
45 bound to the same function, along with a short description of the command,
56 to perform command completion. Hitting a second TAB will pop up a window
65 vile holds text in "buffers". Usually, these correspond to a file that you
66 are editing, but not always. For instance, a buffer might be used to
67 display this help text, or to hold the output of a shell command that you
78 are global to the editor, and not attached to any single buffer. Thus you
81 Undo operations are attached to a buffer, not a window. Thus if you have
82 two windows to the same buffer, and make a change in one, you can undo it
87 help file makes references to modes before the concept is fully described.
90 vile is 8-bit clean, allowing it to be used more easily at non-English
98 with another key, can be bound as a pair to execute any vile function. The
102 | Key: | Bound to dummy function: |
111 If you find any of these keys hard to type, or would prefer that they are
113 binding a new key to the function listed above. See the section on "Key
118 (The '#' key is used in vi to give terminal independent access to function
119 key bindings. This is also true in vile -- if something is bound to '#2',
133 digit to select that buffer, or simply repeat it ("__") to select
135 identical to "_1". If autobuffer mode is off, the buffer which
138 There are many different ways to get the previous file:
155 example, one would type "13_" to visit buffer 13 in the list.
157 Use tab (or back-tab if supported) to scroll the list of 9 buffers
168 will be compared to the existing vile buffer names. Failing that
170 will be stretched into an absolute path, and will be compared to
175 component of filenames. To force vile to edit a file from the
178 if you edit "../Makefile" and later attempt to edit "Makefile",
179 vile will assume you are referring to the _buffer_ named
185 name will change to match it. This command is not as necessary in
190 Identical to '_', except that the selected buffer is placed in the
195 * :e is used to open a new buffer (call this view "C"), which
197 * eventually, you decide to return to "A" and "B".
199 ^X-_1 does the trick (reverts to views "A" and "B"), but _1 simply
203 Go to the next buffer. "Next" means "least recently used" in
210 the filename associated with the buffer. Use ":f" to do that. This
212 to preserve its contents, but run a new command.
215 Set the current window to the specified buffer. This is useful
217 and want to override the automatic layout of "#" and "%" buffers.
220 Go to the first buffer. This is used only in 'noautobuffer'
234 Will ask if changes to the buffer should be discarded. Multiple
253 to create and destroy the list. The buffers are numbered; the
254 numbers correspond to the history numbers shown and used by the
259 setting of "autobuffer" mode (see below). vile attempts to keep
260 the contents of the buffer list window up to date if it is left up
266 will cause the list to include _all_ buffers, even those normally
276 usual way to create a new window.
285 Move to the next window.
288 Move to the previous window.
317 or lower case.) Mnemonically, these correspond to the H, M, and L
318 screen positioning commands, or to "top", "middle", or "bottom" -
332 be forced to move off-screen (which is of course impossible and
349 these give more mnemonic, and faster, access to multiple windows. (These
358 appends one file to another. The ":r" command reads the named file in
362 hosts, backquotes may be used to invoke a shell command that returns the
368 The commands ":ww" and ":wwq" correspond roughly to ":w" and ":wq", but
370 Giving any numeric argument to ":ww" (i.e. "1:ww") will suppress the
371 per-file and "Press return to continue" message. This may be useful when
374 The write-all-buffers command attempts to write all buffers whether marked
391 the specified region to that file. Like all operators, if the
393 10^W^W to write 10 lines.
396 an operator, but writes the specified register to the named file.
402 form "!shell-command". The whole line is handed to the shell, and the read
404 appropriate. Thus you can type ":e !date" to edit a copy of today's date.
412 in a specific buffer, called "[Output]". This is almost identical to ":e
413 !cmd", except that in that case the buffer is named according to the
420 to a TAB character. To actually include a TAB character in the shell
423 completions to the first word of a command line.
427 The "set-environment-variable" (or "setenv") command can be used to export
428 new or changed environment values to spawned programs. (Note that this
435 one directory, cd to another, and write it. You must explicitly write to
436 ./filename in the new directory to accomplish this. ":cd -" will return to
449 Giving an argument to the ": !" (also called "shell-command" when writing
450 macros) will suppress the "Press return to continue" message after the
464 they do in vi, due to the interactive nature of the prompting. And, since
466 slight delay while you're trying to finish typing your complete command.
467 (If the pattern does not exist, you may not get to finish typing your
474 Use ":describe-globals" to see the whole list, or simply use
496 The ":v" counterpart to ":g" is also implemented - it performs the given
499 The substitute command can be followed by any of 'g', a digit, or 'p', to
500 do the substitution for all occurrences, the n'th occurrence, or to print
502 asked to confirm each replacement before it occurs. The text being
509 work on regions: for example use '^A-&}' to "repeat the previous
525 vile also lets you undo all changes made to a buffer since it was first
529 change to the buffer will cause previously undone changes to no longer be
531 command to be an infinite undo, making it easier to type.
534 buffer-modifying command, has special behavior with respect to undo. If
538 command prior to the undo. [ This modification to the behavior of "u."
540 the sequence "u." is (almost) always identical to "uu", and the latter is
541 more easily typed. (Credit goes to the designers of "nvi" for this trick.)
542 (the one case I know of where "u." is not identical to "uu" is when
545 "5, allowing you to choose the "correct" register. This sequence no longer
551 10 changes may be undone. Set the undolimit to 0 for truly infinite undo.
565 motion command ('w'), causing the next word to be deleted. The sequence
567 will delete to the next occurrence of the string "junk". As a special
568 "honorary" type of motion, operators can all be "stuttered" to affect
572 to be affected. This is usually a function of what sort of motion follows
581 Some operators in vile can be "forced" to affect regions of whole lines,
605 case of all characters on the current line, "^A-~w" does it to a
608 If you wish it to be an operator, rebind '~' to the "flip-til"
612 Like ^A-~, but converts the region to upper case.
615 Like ^A-~, but converts the region to lower case.
629 makes it possible to use "3^A-f}" or "^A-fG" to reformat multiple
631 C, C++, and shell comments, and will attempt to do the "right"
633 knows about the '>' character, making it fairly easy to reformat
638 string. This is similar to "s/pattern/replacement/g" over the
642 Is an operator in vile, similar to the traditional & command. It
660 Convert tabs to spaces, using the current tabstop value.
663 Convert as many spaces to tabs as appropriate.
666 Blank out a region. Turns the region to whitespace. Useful with
670 Open up a rectangle. Text to the right of the left edge of the
671 rectangular region will shift to the right by the width of the
684 recommended that you bind it to and easier to type sequence, such
691 obtained, to be inserted after the current line. Usually text that
703 overwrite mode and the (ANSI) arrow keys can be used to give a
708 opposed to blank lines).
727 Does not do a search, but sets the search pattern to the "word"
736 cursor is advanced to the next match with what you've typed so
737 far. Use ^F and ^R to continue the search forward or in reverse,
748 allows you to enter a tagname to locate. The editor opens a buffer
750 supported, so it's possible to type a partial tagname and then
751 press TAB to force vile to complete the name, assuming it's
752 unique. If not unique, press TAB twice to see a list of all
765 - pops to the file and location just previous to the last tag
782 the editor's other windows. To "pin" all locate and pop actions to the
795 Filenames referred to in tags files are expanded, so environment variables
798 The stack of buffer locations waiting to be "popped" to with the '^T' (or
815 people use to generate tags files, does generate exactly this format.
816 (Surprise, surprise.) However, if you attempt to create your own tags
820 For further tags usage examples, refer to the section of this help file
831 that many blank lines to exist at that point, regardless of how
832 many were there before. Moves current location forward, to allow
842 * the feature for forcing blank lines to appear is provided by
846 Force gaps with "empty" lines (no printable characters) to have
853 The "error finder". Goes to the next file/line error pair
865 puts out with the -w switch are honored, so that files are found
868 Tip: I use the following macro to quickly grep a source directory
874 using ^V to escape them. Then I invoke with @g to execute. [NB:
876 since ':' doesn't expand to the word under the cursor on those
877 hosts due to conflicts with filename drive/disk delimiters. For
903 ; example of a macro to add to [Error Expressions]
919 Use the show-error-expressions command to display the contents of
932 Set the local fill-column to be used with ^A-f and auto-wrap mode
944 Count prefix. The first time you type it, it is equivalent to an
945 argument of 4 to the following command. If you repeat it, it
949 In addition to finding matching braces, brackets, and parentheses,
953 it will find "#endif", and on "#endif" it will go back up to the
956 endpoint. (See fence-if, fence-pairs to customize this behavior).
959 Identical to the ` motion, in that the cursor moves to the
960 specified mark (i.e. \a moves to mark 'a'). When used with an
962 "exact". This is similar to the ' motion, which also goes to [the
963 line holding] the mark, and causes regions to become "full line"
974 to delete all of the text between the starting point and the final
985 Most motions will select up to but not including their endpoint.
986 The 'e', 'E', 'f', 't', and '%' commands are exceptions to this.
989 cursor location internally to force the motion to do the "right"
992 (assuming the cursor is on a '(' to start) but which looks wrong,
998 clicked to do the extensions, since it, too, is a motion command.
999 (Of course in xvile or winvile, it is easier to simply "click and
1002 Use the repeat-count to specify types of selection: exact=1
1012 other operator by applying that operator to the ^S motion. As an
1014 Then, from anywhere in that buffer, one can use d^S to delete that
1015 word. ^S used by itself will move the cursor to the start of the
1016 selected region. ^S applied to the selection operator (^A-s) will
1017 extend the current selection to include the current location of
1020 ^S makes it possible to select any region (including rectangular
1021 regions) of text with a mouse, and then apply any vi operator to
1032 selects, highlights, and yanks all text in the current buffer to
1073 displays the list of commands and the keys bound to them.
1102 associated types. To allow it to fit within 80 columns,
1106 Use a repeat count to show data for the wide locale. The default
1108 to see wide characters past the first 256.
1118 displays the strings mapped to represent the terminal's function
1123 from which the ":ta" or '^]' commands have been used, and to which
1132 %variables, and their values. Use a repeat count to show all mode
1138 with associated types. To allow it to fit within 80 columns,
1142 Use a repeat count to show the data for successive "pages" of 256
1152 In addition to the usual "a through "z, and "1 through "9, vile has
1156 been typed by the user. The principle use for this is to make it easier to
1158 useful sometimes when debugging to be able to see what key sequence led to
1167 unnamed register, which is also sometimes referred to as register 0.
1172 Many responses to vile prompts need not be typed in their entirety. vile
1173 can complete the response for you. This applies to command names, file
1181 characters will cause that window to scroll through the choices. The
1186 terminal character) to display a list of the characters that you would
1187 have to type to complete the command. For example, to complete the
1195 that you must type to make the command unique.
1202 interpreted as function keys, and are by default bound to the up, down,
1211 "rectangular". The easiest way to use a rectangular region is with the '\'
1212 motion, which, like '`' and ''', goes to a named mark. The region it
1214 The following operators know how to correctly act on rectangular regions:
1217 Opens up a rectangle. Text to the right of the left edge of the
1221 Shift right. Identical to '^A-r' when region is rectangular.
1224 Deletes the (rectangular) region. Text to the right moves left to
1228 Shift left. Identical to 'd' when region is rectangular.
1261 'put' to be inserted as if it had been rectangular when originally
1265 Note that because it is sometimes hard to manipulate rectangles containing
1268 lines again after the operation. The re-entabing is limited to leading
1285 saying that its value is set to 0 or "", the latter for string types. When
1334 to a specific buffer once a "local" value is independently established. To
1340 edited the file "precious.cpp", which I did not want to modify. There are
1352 :setl view ; "view" mode now bound to precious.cpp
1357 solution works for the stated goal, but makes it impossible to modify any
1362 Similar to buffer modes, window modes are bound to a specific window once
1368 Until the subject of syntax coloring is described, it's not very useful to
1435 not frequently used will drift to the end of the list. If this
1441 Automatic syntax coloring. If set to zero, automatic syntax
1442 coloring is disabled. Otherwise, it should be set to a small
1443 positive integer which represents the number of milliseconds to
1454 to be auto-written. Individual buffers can be forced or prevented
1457 buffers to be written when switching between files. This is
1481 backups, respectively. Files are copied before being written, to
1482 protect links to the original file. Permissions, modification and
1495 is a prefix used to distinguish different types of UTF-encoding.
1508 The "auto" setting tells vile to set the buffer's byteorder-mark
1509 value based on whatever the file-encoding happens to be.
1512 it to accept byteorder-mark values as in "auto", but not to write
1521 Regular expression used for parsing of $bufname, subject to the
1535 tells vile to ensure that it uses only files that you own (or root
1570 buffers (those currently in windows) to have their times checked
1574 must be active to enable the latter behavior.) (B)
1589 indented to column 1. This is a temporary indent;
1599 causes the next line to be indented more, and the right-character
1600 causes the next line to be indented less. (B)
1609 Causes buffer(s) to be decrypted when read, and encrypted when
1628 is used in addition to the "paragraphs" expression (see below)
1643 buffer name does not correspond exactly to a regular expression.
1647 Causes vile to check each name when scanning directories for
1649 information allowing you to distinguish between directory and file
1662 have CR/LF endings for it to automatically treat a buffer in this
1674 to initialize dos mode.
1694 Controls whether %/# are expanded to the full pathname of a
1695 buffer, or just to its basename (i.e. the name with the path
1722 Iteration timeout for complex fences, to limit pathological cases,
1726 Each pair of characters in this string is taken to be a set of
1730 ("{}()[]<>>") to cause angle brackets to be matched as well. See
1746 The "auto" setting tells vile to determine the encoding by
1747 inspecting the buffer contents. The "locale" setting tells vile to
1749 encoding. The "8bit" setting corresponds to the 8-bit locale
1762 syntax-highlighting filters. If set, this mode directs vile to
1764 messages, which can be used with the error-buffer command to step
1769 is used in the filters.rc file, to handle special cases where
1770 different sets of keywords are applicable to a common syntax,
1776 and Unix hosts. For further details, refer to the section of this
1786 specifies whether globbing or regular expressions are used to
1804 in prompts for filenames. Set glob to 'off' to disable expansion,
1805 or to 'on' to use the internal globber. The internal globber will
1809 On UNIX, glob can be set to be a pipe command that will expand
1812 set to a command that will separate filenames with newlines or
1819 buffers. This allows you to disable highlighting for all buffers
1824 buffer [History]. Turning this off causes the buffer to be
1830 sideways to make the cursor position visible. If not set, then
1836 corresponds to the pattern under the cursor used in tags and
1837 "screen-search-pattern-grab", etc., subject to the cursor-tokens
1855 Causes vile to create a buffer when you write to a new file, or
1859 Tells vile to interpret control characters for movement and
1860 undo/redo if they are bound to appropriate functions during insert
1878 where "emacs" is used to denote vi-like-emacs. The setting for
1880 some examples to compare, where "top" and "bot" refer to the
1905 When linewrap mode is set, add blanks in the display to avoid
1909 Displays lines that are too long to fit on one line as a series of
1919 the capture.pl script to show when asynchronous data is loading.
1928 Controls the maximum length of a :map string, to prevent runaway
1949 is typed which is bound to a function, then that function binding
1954 When user toggles editing mode in the minibuffer (^G, mini-edit),
1955 display the minibuffer with the given attribute. These are the
1961 only to the portion of the complete pathname after removing the
1966 corresponding majormode will be set. The expression is applied to
1967 the complete pathname, in contrast to mode-filename. (M)
2004 Controls the number of lines from each end of the buffer to scan
2005 for vi-like mode lines. Defaults to 5 (B)
2027 Modifies the highlighting shown by visual-matches to control
2029 setting this to false will present a more natural view, e.g.,
2040 expanded by ":" (or "&") in the minibuffer, subject to the
2050 desired to use for coloring the buffers. This helps with very
2052 will skip subsequent updates for the buffer, to keep up. When it
2059 Percentage of total lines which must end with CR/LF for vile to
2060 automatically convert buffer's recordseparator to crlf, if dos
2066 is set to "auto", and the match is higher than this threshold,
2068 well for text which is mostly Latin-1; you should set this to a
2069 lower value to work with text which does not follow that pattern.
2075 operations are "pinned" to the current window. (U)
2078 Must be set to one of the following three values:
2085 completion in response to a TAB. "immediate" will force the buffer
2086 to be popped up immediately if no progress is made in forming a
2087 completion. "delayed" will cause vile to wait until TAB is pressed
2092 that was written to the message line. Closing the window clears
2098 to "false". (U)
2101 Must be set to one of the following three values:
2114 may have a majormode "sh", with sh-preamble set to
2115 "^#\s*!\s*\/.*sh\>" to match the lines "# ! /bin/sh", "#!/bin/csh
2120 "high bit" (i.e. 8-bit) characters. Defaults to 0. Most foreign
2121 (relative to me!) users would set this to 160, the first printable
2128 set of "high bit" (i.e. 8-bit) characters. Defaults to 0. Set this
2129 to 255 for ISO 8859/1 compatibility. The printing-low and
2138 mode defaults to "both", which means that the quick method is
2139 tried first, and if it fails to allocate the large chunks needed
2141 Set to "fast" to use only the fast method, and to "slow" for only
2145 Prevent writing a buffer to its associated file. Unlike "view"
2146 mode (see below) which prevents any modifications to a buffer,
2151 Causes "readonly" mode to be set for read-only files. Normally
2152 vile will attempt to write files whether the operating system will
2153 allow it or not. This mode should be turned on to truly mimic vi's
2158 * "auto" (to choose between lf and crlf, override dos mode)
2166 from a pipe, it uses the global value of recordseparator to decide
2167 how to split lines. Files created within vile do not automatically
2176 recordseparator. Set the recordseparator on a given buffer to
2185 remapping control should be subject to remapping (i.e. recursive
2189 Controls whether the first character of a map expanded due to :map
2194 A threshold value that is used to control messages that report the
2195 number of lines deleted, changed, etc. Set it to 0 (zero) to
2201 about symbolic links that provide multiple paths to a given file,
2246 mode, to save space on the modeline (W).
2250 status line. Values are "always", "differs" to show when the local
2251 mode differs from the global, "local" to show whenever a local
2252 mode is set, "foreign" to show when the recordseparator differs
2264 Causes an indicator on the modeline to indicate what mode vile is
2273 "show-variables" command to be updated each time the screen is
2278 allow display of a section of code normally off the screen to the
2283 that vile will try to keep up with your keystrokes instead of
2284 keeping the display up to date. Some keyboards repeat faster than
2285 the screen can keep up causing the screen to jump. If this bothers
2286 you, set smoothscroll to true. Warning: If your keyboard repeats
2288 for vile to catch up. (U)
2302 only to the portion of the filename beginning with the first ".".
2316 turned off ("notabinsert"), and an attempt is made to insert a tab
2319 characters will be inserted instead. Use '^V^I' to insert a real
2321 the '^A-<SP>' operator command to eliminate pre-existing tabs from
2330 Causes tag searches to be done ignoring upper and lower case. (B)
2334 names longer than the taglength value will only attempt to match
2341 Causes files looked up via the tags mechanism to be found relative
2342 to the location of the tags file, rather than relative to the
2343 current directory. This allows the same tags file to be useful
2346 tags file (located in the parent) to be used in a small source
2350 Gives a path of names of file(s) in which to look up tag
2352 Relative pathnames in this list are evaluated with respect to the
2356 When scanning the word to lookup from the cursor position for the
2373 How long to wait for the characters of a :map'd sequence.
2374 Typically needed to resolve the ambiguity between a user-pressed
2377 seeing an ESC, in order to check the next character of input. The
2378 time defaults to 500, or half a second. Users of fast local
2379 screens, like a local xterm, may wish to reduce this to something
2380 like 50 for crisper response to a user-pressed ESC. (U)
2389 minute to type each character of a user-defined :map. Be careful -
2391 machines, i.e, you will probably want to avoid setting
2400 normally enabled, but you may wish to disable it to reduce memory
2405 saved. If set to 0, there is no limit, and all changes are
2415 When vile is asked to read a file into a buffer, it will first
2416 check to be sure that it doesn't already have a copy of that file,
2419 filesystem due to hard or soft links. On UNIX systems vile uses
2420 the combination of filesystem device and inode to check for
2421 uniqueness. vile will represent the file by the first name used to
2422 refer to it. Note that unless "check-modtime" is also set, a file
2441 Causes "view" mode to be set for read-only files. (U)
2446 (in the current buffer) will be emphasized according to the value
2449 used to set the text foreground color using any of the color
2452 The '=' command can be used to clear this sort of highlighting,
2456 since vile will need to scan the entire buffer for matches on any
2457 change to the buffer. (B)
2470 | reverse | on err -> switch screen to normal then reverse |
2473 | normal | on err -> switch screen to reverse then normal |
2481 When prompted for a filename, vile normally allows you to use
2483 this mode if you prefer to be prompted. Vile will then prompt you
2484 if you want the nonprinting characters to be stripped from the
2488 When using ":e" to find a file that has the same name as another
2489 buffer, vile will normally offer for you to edit the proposed
2491 etc. to the end of the name. Turning off "warn-rename" will make
2495 When using ":e!" to reread a buffer from the file on disk, vile
2496 will normally warn you that you are about to clobber a modified
2502 then normally vile will complain, and remind the user to use
2515 on the screen's right margin to reserve before breaking the
2526 Text searches will continue from past the bottom of the file to
2530 Similar to, but different from, vi's auto-wrap mode (i.e.
2531 "wrapmargin"). While inserting, words are moved to the next line
2543 is, it allows vile to receive mouse events. Since this mode
2544 overrides xterm's cut & paste, you will need to use the Shift key
2545 when pressing the mouse buttons to cut and paste between X
2547 string "xterm" for this to work. (U)
2551 time you switch to a different buffer, vile can update the title.
2573 to the printable range of the ISO-Latin-1 character set.
2578 on the system. You can make finer adjustments to those tables as described
2581 If your terminal (and locale) are set up to support UTF-8, vile can
2585 when vile can display wide characters, you can force it to display the
2591 If your terminal and locale are not set up to support UTF-8, vile displays
2592 UTF-8 codes that would map to Latin-1 (8-bit) values with a "\?" rather
2593 than "\x" prefix, to distinguish them from ordinary 8-bit values. It will
2607 they are bound to functions. On an xterm, try "stty cs8 -parenb
2613 UTF-8 suffix from the locale name, e.g., "en_US.UTF-8" to "en_US".
2615 to the 8-bit locale when editing a buffer whose file-encoding is
2619 the ^V prefix (or, more correctly, the key bound to the
2620 "quote-next-character" function), if followed by up to three
2633 If the current buffer's "file-encoding" mode is set to one of the
2639 Perhaps more useful to some people is using a set of ":map!"
2640 commands to aid insertion of 8-bit text. The file "digraphs.rc"
2643 in digraphs.rc allow one to type ^KU" or ^Ku" to get an umlaut
2644 character, ^K12 to get the little '1/2' symbol, ^KY- to get the
2645 Yen currency symbol, or ^K:- to get an arithmetic division symbol.
2647 Users who have no need to enter 8-bit text may want access to the
2649 mode "meta-insert-bindings" controls whether functions bound to meta-keys
2652 bound to a function, then it will be self-inserting when in insert mode.
2653 (To bind to a meta key in the .vilerc file, one may specify it as itself,
2657 (Although it is possible to edit and view all 256 characters, it is
2658 currently impossible to _search_ for a string that contains the NULL
2659 character, since this is used internally to terminate the search string.)
2664 You may scroll through the list of previous replies to the :-prompt by
2676 action to perform on each matching line: p
2682 At each prompt, using the up/down arrows will tell vile to display the
2694 The minibuffer (i.e., the last line on the screen, aka the :-prompt) can
2695 be edited using arrow keys, the delete character, or by toggling to
2697 commands that do not move the cursor to a different line, as well as the
2700 Vile treats the minibuffer specially. Completed lines are written to the
2702 displays the data that correspond to the command which you have entered,
2709 As in vi, the % and # characters typed while responding to a prompt will
2710 expand to the current or "alternate" filename.
2712 Also as in vi, the ~ character will expand to be the previous replacement
2715 In addition, the colon character (":") expands at most prompts to be the
2718 Expansion of ! to the last command run is implemented, but only when a
2729 You may modify the characters in (or corresponding to) the narrow local in
2735 defines a range of characters. The class names (short to allow
2736 "show-printable" to show everything in 80 columns) are
2776 You can also reset the table to its initial state using
2782 There is a key rebinding facility (if vile is built to include it), which
2784 being rebound. Use ":show-commands" or ":apropos string" to find english
2790 '^X', '^A', or '#' followed by a single character) to which the command
2804 Commands can also be bound to meta keys, which are regular ASCII
2808 Commands bound to '#-c' or 'FN-c' key sequences are usually also available
2810 can be bound to as '#-A' or 'FN-A'. Use show-key-names to see a complete
2817 Examples: To cause the / and ? commands to perform incremental searches,
2823 To make ^N and ^P switch windows instead of cause motion by lines, try:
2828 To cause the space bar to move forward by pages, as in the "more" command,
2843 hexadecimal value for a key, you can bind to it like:
2852 equivalent to setting the high bit of the following character, so 'M-e' is
2910 (unmodified) or ^A/^X (modified) keys are bound to a given function. Use a
2911 repeat count before those commands to show data for all 256 codes.
2928 ; bind to function key 5
2931 ; also bind to meta-A
2937 on (or if the meta-key is not bound to any function) then the key's value
2942 To summarize, a key-sequence being bound to is specified with:
2974 represented in this help file as two printable characters, to ensure they
2979 When you bind to a function key, you will see its value printed as a
2980 'poundsign' sequence. And, if you wish to :map a function key, you will
2981 need to use its poundsign sequence. This is explained more fully below.
3028 In addition, #M, #t, and #T are used internally to support mouse
3036 mapping works best if the character sequence being bound corresponds to
3044 Because "map" and "map!" may be used to remap arbitrary sequences, these
3052 vile will reapply mapping to the result of a system-defined map. System
3053 function keys are mapped to "poundsign" sequences, like '#1' for function
3054 key 1, and '#B' for the down-arrow key. The remapping allows one to put
3059 F1 key is pressed. (Otherwise the terminal-specific sequence would have to
3066 mapping to be applied without subsequent remapping, regardless of the
3070 expected to act as a unit, no remapping is done on characters that follow
3078 assumed to be infinite. When such a loop is detected, execution is
3084 first character of the sequence being mapped to is not subject to
3093 and "foobar" are mapped (to presumably different values), then with
3103 When 'z' is pressed by itself it will cause vile to move down one line
3105 rapidly (enough) in succession, vile will move to the previous line.
3123 The "abbr" command is also present in vile. It is similar to, but slightly
3127 buffer, and is more sensitive to their surrounding context.
3148 "word" character. vile allows anything at all to be abbreviated, only
3156 In addition to the above binding mechanism for vile commands, other
3157 keystrokes to the editor are rebindable using the "set-terminal" command.
3159 on entering the editor, but there are a couple of additions related to
3199 still set up with software flow control enabled, to allow the user to
3202 vile normally resets the driver to allow the ^S and ^Q characters to be
3203 bound to commands, since most systems no longer need software flow
3204 control, and since there is usually no reason for a user to wish to
3206 terminals), however, still need to be able to automatically control the
3210 reset the terminal driver to its original state. Software flow-control
3211 will be re-enabled, and commands bound only to the ^S and ^Q characters
3230 are now both bound to the same function. The start/stop capability
3237 Copy recorded keyboard macro to a named register, for saving, or
3241 The vi '@' command is present as well, and can be used to execute the
3248 will load register 'a' with a command to insert the word "hello". (The ^[
3254 which makes the current file writable and writes it. (Again, use ^V to get
3266 solely to use within macros. These directives are often used within a
3267 startup/command file to configure the editor, load registers, etc. ]
3270 execution of those macros to key sequences. For instance, if the following
3280 to be followed by a motion command. Also,
3307 To bind a keystroke to this macro, use this command:
3339 keystroke to this macro, use this command:
3385 There are some built-in variables that can be used in macros to gain
3386 access to parts of vile status, and parts of the current buffer. Built-in
3414 | | | a | autobuffer caused this to be created | |
3435 | $buffer-hook | name of procedure to run when switching to a |
3448 | $cd-hook | name of procedure to run when changing |
3529 | $cmd-encoding | character set to use for minibuffer |
3560 | $error-buffer | buffer name assigned to the error-buffer |
3566 | $error-tabstop | tabstop to use with error-buffer for %C |
3568 | $exec-path | where to find vile (read only) |
3573 | $exit-hook | name of procedure to run when quitting |
3575 | $favorites | path to favorites folder (win32 only) (read |
3627 | $latin1-expr | pattern to match locales using ISO-8859-1 in |
3632 | $libdir-path | appended to $PATH when running filters |
3643 | $majormode-hook | procedure to override suffix/preamble rules |
3655 | $modeline-limit | maximum inline offset to scan for mode lines |
3700 | $read-hook | name of procedure to run after a file is read |
3704 | $return | set within a macro to provide $_ on completion |
3716 | | absolute path to override $startup-path. |
3718 | | where to find the startup file, i.e., a |
3756 | $write-hook | name of procedure to run before a file is |
3759 | $xdisplay | the value to set $DISPLAY when running $xshell. |
3767 In addition to the state variables, you may set and use the values of the
3770 not visible to the expression evaluator.
3775 Response variables (a '@' followed by a prompt-string) cause vile to
3779 of the specified buffer, automatically setting the position to the next
3785 on hard-coded values. Operations are expressed in prefix notation, so to
3786 add to numbers you would say "&add 3 5". You may use any unique
3800 | &ascii | 1 | char to integer conversion |
3804 | &bind | 1 | lookup what function name is bound to key |
3810 | &chr | 1 | integer to char conversion |
3916 | &random | 1 | get a random number from 1 to n |
3929 | &rnd | 1 | get a random number from 1 to n |
3959 | &translate | 3 | translate "from" to "to" for given string. |
3972 "tags"). The second is an initial value to complete.
3975 second is a filename. Keywords may be combined with '+', e.g., r+bin to
3996 and for access type, defaulting to an existence check:
4028 | ~elsewith tokens | alterate tokens to following commands ||
4038 | ~force | force macro to continue even if command fails ||
4040 | ~goto label | jump to a label in the current macro ||
4057 | ~with tokens | prepend tokens to following commands ||
4064 You would jump to this with:
4073 be executed if desired. These points are referred to as "hooks". Hooks are
4074 specified by special variables which hold the name of a procedure to run
4080 write-message &cat &cat &cat "moved from " $ocwd " to " $cwd
4094 | $autocolor-hook | applies syntax coloring to modified buffers when the |
4097 | $buffer-hook | run when switching to a buffer |
4103 | $majormode-hook | procedure to override suffix/preamble rules |
4111 themselves switch buffers is not recommended. In general, all the hooks
4114 cause the hook to be re-executed. (vile keeps the hook procedure itself
4115 from being re-executed, to prevent recursion, but the code surrounding the
4116 call to it may not be safe either.)
4121 macro, you can put "~force" in front of it. So, to write a macro which
4141 And the "screen-search-pattern-grab" command, normally bound to ^A-/,
4174 skip the cursor position when scanning, so as to always find the next
4175 occurrence. The directive ~local is used to avoid disturbing the search
4178 Note that for simple key-remappings, binding is often preferable to
4179 creating a macro. Some people prefer using lower-case 'g' to as an
4180 equivalent to 'G', to goto a specific line. If done as a macro, like this:
4187 then both g and G go to the end of the file, but whereas 1000G goes to
4188 line 1000, 1000g goes to the end of the file 1000 times. It is easier (and
4189 more correct) to do:
4194 to the next (or previous) line of the same (or lesser) indent, skipping
4195 over empty lines. (Thanks to MIURA Masahiro)
4197 ; macro 1 - back to the line of same indent
4219 ; macro 2 - forward to the line of same indent
4241 ; Use "@d" to change cwd to the dir containing the current file
4243 ; explicit CR and that ":cd -" reverts cwd to its previous value.
4272 ; it's not possible to disable the screen clutter of
4287 ; force ustring to align with prev line
4300 ; so that ^X-^X may be used to visit the lines found by grep.
4301 ; (we have to set error-buffer explicitly, since we renamed
4311 As a hint, it is (almost?) never correct to write a ':' command when
4318 (in an attempt to make a buffer writable before editing it), then what you
4334 (Of course you need to replace the ^M's with real carriage-returns.)
4406 regard to upper and lower case.
4408 by '\' to hide their special meaning: * [ . ^ $ These characters
4411 All of the following must be preceded with a '\' to be special,
4417 to 9 such substitutions can be made. The special symbol & will &
4419 The tilde (~) character will expand immediately when it is typed to
4422 immediately, as a default response, but this made it difficult to
4425 special sequences \U and \L, which cause the replacement to be
4426 \U \L forced to uppercase or lowercase until a terminating \E is found;
4437 On startup, in the absence of '@' arguments, vile attempts to read the
4441 the startup file's commands. It is possible to nest such executions. For
4444 which you prefer tabs be set to 4 spaces:
4449 The quotes surrounding the filename are necessary to protect the name from
4454 Refer to the file doc/macros.doc which is distributed with vile for more
4457 Nesting of source'd files is limited to a depth of ten, to prevent
4462 separate lines to be safe.
4484 set when vile was configured prior to
4499 vile commands to initialize the editor. As a not-very-useful example of a
4517 environment variable at runtime will cause vile to abort (and dump
4518 core) rather than attempt to cleanup and exit with an error code
4528 variable, which is appended to your $PATH variable when running
4532 override the pattern used to associate wide/narrow locales. vile
4533 uses this to compute a possible 8-bit "narrow" locale which
4534 corresponds to the current locale, thereby supporting editing of
4539 example, "en_US.UTF-8" would be converted to "en_US". If your
4541 pattern to help vile find the narrow locale value that works.
4552 on platform) in the ShowFormatted macro (^X-n). You may want to
4553 set this to "groff" if your system has groff installed, for
4573 if set, indicates that "tbl" is available. Set this to "cat" if
4574 you do not want to use "tbl", but do want to use "nroff", etc (see
4580 may set $PATH. One solution (other than adding /usr/local/lib/vile to
4581 $PATH) is to set the vile variable $shell to /bin/sh, assuming you have no
4582 Bourne shell ".profile" to set $PATH. Then vile's modification of $PATH
4589 options to support the commonly used '+400' to go to line 400 and '+/foo'
4590 to search for foo. Command files can be explicitly executed on startup by
4609 vile will edit the correct file and move the cursor to the
4617 Invokes vile in "view" mode - no changes are permitted to the
4631 vile implements an interface to the UNIX crypt function, like standard vi,
4632 and can apply this to your buffers either automatically (via a mode
4645 prompted for the encryption key to use if none has yet been set. If
4647 will be encrypted when read. In practice this means you need to read the
4651 As an alternative to UNIX crypt, the collection of macros in the file
4658 The "vi -r" option, used to recover an edited buffer after a system crash,
4660 infrequently :-) due to a bug, but perhaps due to an externally applied
4661 signal), it attempts to save any modified buffers in a temporary directory
4662 and, on a Unix host, sends mail to the user to that affect. The selection
4675 Saved buffers are written to disk using the path ./V<buffername> .
4694 in reverse video or via other means in order to visually separate windows
4695 and to distinguish the mode line from text displayed in the window.
4697 The editor variable "modeline-format" is set to a string which controls
4699 used to customize the display of mode lines. The format specifiers which
4722 | %l | line number to be displayed if "ruler" is set |
4745 | | rough position of window with respect to buffer (top, bot, |
4750 | %= | string. This indicates where to separate the left and right |
4769 associated file name to be displayed when the buffer is of the appropriate
4771 from the buffer name. It is desirable at times to cause a prefix string
4772 and/or a suffix string to be emitted along with the string obtained after
4776 used to display the line and column number for "ruler" mode. Note that
4786 Mode lines for some versions of vile previous to version 4.7 can be
4789 indicator to the far right in the mode line.
4796 The editor's support of color varies from host to host. On some hosts,
4799 Prior to discussing the ins and outs of syntax coloring, it helps to first
4817 underlying display hardware, vile supports a palette of up to 16 colors.
4857 arbitrary RBG values to the above color names, thus permitting the
4863 colors are modified by changing the editor's color resources (refer to the
4865 line in an .Xdefaults or .Xresources file maps "gray" above to red:
4876 command. Mirroring the example above, map "gray" to red like so:
4883 These attributes may be used to modify/enhance any of the existing colors
4885 configure the editor to highlight all matched search strings in the
4895 Note that on some unix hosts it's possible to run standard vile in a color
4896 xterm and thereby gain access to an expanded color palette (albeit often
4897 limited to 8 colors). However, this is only possible when:
4910 instead, vile's color palette is limited to black and white (i.e., no
4912 force the editor to use that library:
4934 color may be set to a simple color value (no attribute modifiers allowed).
4949 cause the editor to render text in arbitrary color/attribute sequences.
4958 It's possible to mix colors and attribute as well:
4967 detailed discussion of attribute control sequences, refer to the topic
4976 maps classes of language keywords/elements to user-specified colors
4980 3. the filter writes its results to stdout, which vile reads back and
4981 uses as control information to color the buffer.
5016 "coloring" is limited to the use of attributes like bold, underline, etc.
5022 many languages and text file formats, including (but not limited to):
5030 "xxx" is usually the same name assigned to vile's corresponding builtin
5048 file formats, refer to the file doc/config.doc in the editor's source
5060 to the help topic "Majormodes" in this help file, as well as the file
5064 actually applied color attributes to a target buffer, thereby damaging the
5071 description of syntax coloring configuration, as well as pointers to
5082 require preprocessing with flex (not a standard Windows tool) prior to
5092 The simplest install copies the editor to a directory in the system PATH
5094 macro files to /usr/local/share/vile. The following commands accomplish
5103 1) add the following to their $HOME/.vilerc startup files:
5114 configuration". With regard to the remainder of this discussion, the term
5115 "COLORDIR" refers collectively to the list of directories where vile
5145 The simplest install copies the editor and all data and macros file to a
5157 1) add the following to the $HOME/.vilerc startup file:
5166 3) add $HOME/local/bin to $PATH (if not already specified)
5170 configuration". With regard to the remainder of this discussion, the term
5171 "COLORDIR" refers collectively to the directories $HOME/.vile or
5176 You may choose to not use the winvile install/setup program, or else you
5182 1) create a directory (hereafter referred to as COLORDIR) to store the
5196 a) copy *.rc to COLORDIR. Note that the most important of these files is
5199 b) copy vile.exe, vile.hlp, and winvile.exe to a directory in your PATH.
5234 | set-highlighting | <none> | Attach a major mode to a buffer and |
5247 happened, skip down to the troubleshooting section.
5252 the editor to take over this task, add this line to your startup file:
5258 buffer's contents change, which brings us to the next topic.
5265 It's possible to automatically initiate syntax coloring when the editor
5267 sounds appealing, add the following to your startup file:
5269 ; change autocolor mode value to suit individual tastes
5278 To disable this feature, set autocolor to 0 (zero).
5282 inappropriate. That is, type ":setl autocolor=0" to disable the automatic
5291 Depending on the speed of your hardware, you may wish to make this
5335 The "Comment" class defines the color attribute applied to a language's
5337 to string literals, which will be shown as "U"nderlined "C"olor "5".
5338 "Keyword" applies to a language's reserved words (e.g., "if", "while",
5346 tokens (e.g., "int", "static", "while") to vile.keyword's generic classes
5352 or want to edit these files.
5356 From time to time, users upgrade to the latest release of vile. If the
5360 not a happy event if you've spent time tweaking this file to suit your
5361 tastes (the author speaks from experience). Word to the wise:
5363 Once vile.keywords is edited to your satisfaction, make a backup copy
5371 ":show-colors" to list current capabilities. If colors/attributes
5372 appear to be missing, reread the "Color basics" topic in this help
5393 attached to the file's buffer and appropriate syntax coloring ensues. But
5398 use the "set-highlighting" macro to explicitly specify the desired
5402 main.cpp, which has been renamed to main.cpp.old . In this scenario, vile
5403 will not attach a majormode to main.cpp.old's buffer and consequently will
5411 It's also possible to syntax color Unix man pages, although the procedure
5412 is not tied to a majormode. Refer to the help topic entitled 'Filtering
5420 add this line to your startup file:
5434 Syntax highlighting applies to buffers which are loaded from files. vile
5435 can also generate buffers to show its internal state. Those can be colored
5456 type, followed by a combination of color and attributes. Use '+' to join
5485 Prior to studying majormodes, it helps to be familiar with the "Editor
5489 assigns to new buffers. When the vile distribution file "filters.rc" is
5492 file formats. The majormode assigned to a particular buffer is dependent
5543 As an actual example, suppose someone wanted to edit this help file and
5544 subsequently submit patches to vile's developers. In the spirit of
5549 8. Also, it appears that the right margin is set fairly close to 80. To
5576 For example, suppose it was desirable to edit all text files with
5606 1) Use the command "show-majormodes" to display the list of majormodes and
5611 3) To override the majormode that vile assigns to a buffer, use either the
5625 his/her time to C++ coding), simply add something like this to the vile
5636 are presumed to be C++ files.
5647 This change adds ".h" to the list of C++ files and since vile tests
5652 Long before Tom Dickey added majormodes to vile, there existed "cmode", a
5677 file to suit your needs/taste, like so:
5690 file filters/manfilt.c), either vile or xvile may be used to filter and
5696 portions copied below) contains a macro which is bound to ^X-m. It will
5704 This assumes that you have moved the manpage.rc file to a directory known
5705 to vile (automatically handled by "make install" on Unix or,
5706 alternatively, by pointing the VILE_STARTUP_PATH env var to the directory
5711 The manual page filtering program may also be used to look at other text
5722 command "attribute-cntl_a-sequences-til" (bound to ^A-A) may be used to
5725 attributed text into one which is more pleasing to look at.
5730 to any man page displayed in the editor's current buffer.
5735 vile includes several features that enable quick access to many files
5752 argument to kill the buffer. "dirs-clear" clears the stack and
5753 kills the scratch buffer. "dirs-add" adds a directory to stack[top
5759 removes the top directory from the stack and performs a cd to the
5769 adds a directory to the top of the directory stack or rotates the
5783 adds dir to the directory stack at the top, making it
5801 the ctags program), vile's tags interface provides quick access to the
5804 interface to access the C/C++ files in the aforementioned directories when
5813 1) cd to the project root dir and issue this ctags command:
5821 2) modify the vile startup file (vile.rc or .vilerc) to include this
5827 vile's tags lookup features now provide one-keystroke access to symbols in
5831 It's important to note that Exuberant Ctags has been ported to many hosts
5839 1) cd to the project root dir and issue this ctags command:
5847 2) modify the vile startup file (vile.rc or .vilerc) to include this
5858 vile's capture-command (bound to ^X-!) includes an interface to the Unix
5859 find command (or equivalent clone) that permits the user to access a large
5872 Next, use find-cfg mode to enable the traversal feature. This mode's
5893 solely to files of type "d" (i.e., directories). The "f" option adds a
5894 "-follow" operand to the commandline, which directs find to follow
5907 "Hierarchical tags" above. Assume also that the path to the project root
5930 The net result is that capture-command has been used to find the string
5934 binding. Note that the above shell commands are crafted to ignore files
5935 stored in RCS/CVS directories and to ignore the files created by ctags.
5937 If it's preferable to use a nonrecursive find operation and the GNU find
5962 this feature won't work. The workaround is simple-upgrade to the GNU
5967 Suppose all you really desire is access to the names of the directories
5969 who want to manipulate a directory's contents with specialized scripts. To
6002 script is an example of a filter which uses the vile's interface to Perl.
6004 Regardless, the goal of the filter is to embed in the text a control
6014 (See above for examples of how to use this command.)
6021 following the ':' to be attributed.
6023 <Attr> is a sequence of characters which indicates how to attribute the
6041 example, you could use the following to make some text appear both bold
6051 space bar to be bound to a macro which will follow a hypertext link when
6053 the normal default action of advancing one character to the right is
6059 ~force forward-character-to-eol
6064 [ TODO: Maybe we should just add a little bit of code to make this the
6066 any event, it'll only take 7 or 8 lines to do the job... ]
6075 hypertext command to be executed. If no hypertext command is associated
6084 text written to the editor's message line. This mode, when used in
6086 mechanism for debugging macros. Type ":se nopm" to disable
6090 use vile's builtin macro tracing to see what the macros really do.
6092 whether vile appends to the [Trace] buffer a copy of each line
6111 displays the full path that the editor's shell will use to exec
6120 Note 3: Specify a numeric argument to force vile to popup a buffer
6142 displays the full path that will be used to source <file>>.
6147 Note 2: Specify a numeric argument to force vile to popup a buffer
6187 line). Clicking on a mode line will set the keyboard focus to the
6189 the above in addition to clearing the highlighting associated with
6194 selection to be yanked and made available (if desired) for
6195 pasting. The region selected may be forced to be rectangular by
6198 text will be scrolled in the appropriate direction if possible to
6201 it practical to select large regions of text quickly.
6214 wiping with it. Selections may be extended in any window open to
6226 operator to the selected region. For example, after selecting text with
6227 the mouse, it can be converted to uppercase with ^A-u^S. Remember that
6238 selection to exchange data between applications. On many Sun keyboards,
6239 selected text is moved to the clipboard by pressing the "Copy" key and
6247 copy-to-clipboard and paste-from-clipboard. When copy-to-clipboard is
6248 executed, the contents of the current selection are copied to the special
6254 Users of Sun systems may want to put the following key bindings in their
6255 .vilerc file in order to make use of the Copy and Paste keys found on
6258 bind-key copy-to-clipboard #-^
6263 The X toolkit version of xvile provides default translations similar to
6265 know how to use xterm's scrollbars, you know how to use these scrollbars.)
6271 bottom will scroll by a larger amount up to a whole page. Holding either
6275 buffer to a position proportional to the location of the pointer on the
6276 scroll bar. Button two may be held down to "drag" the slider from one
6277 place to another causing text to scroll continuously.
6285 the arrows. Motif's slider is solid with size varying to indicate the size
6286 of the window with respect to the size of the buffer. Any portion of it
6288 of the scroll bar which may be clicked upon to cause scrolling by one
6291 additional control areas; the buffer position may be set to either the
6299 versions wait until after a position is selected to resize the windows.
6301 indication (other than the position of the mouse pointer) to indicate
6315 | -fn fontname | Font to use (or -font). |
6321 | -display disp | Display to run xvile on. |
6331 | -title name | Name to be displayed in titlebar. |
6337 | -xrm Resource | Specify or change an X resource internal to |
6346 | -fork | to spawn xvile immediately on startup |
6348 | +fork | to force xvile to not spawn on startup |
6357 Some systems and/or some shells and display managers seem to want xvile to
6358 run in its own process group, to help isolate its signals and actions from
6362 file. Using this will cause a call to "setpgrp()" or "setsid()". This
6368 to fork(), and the parent to exit before the new process group is set by
6379 | font | Font to use. |
6389 | charClass | selections. The format is identical to that |
6393 | | to be accepted as a multi-click. |
6404 | | will cause the cursor to maintain constant |
6406 | | make it easier to see when it appears in a |
6414 | modeline.focusBackground | line corresponding to the window with |
6418 | modeline.foreground | corresponding to windows without the |
6427 | | necessary to change windows. |
6445 | scrollbar.background | slider to be only the foreground color, you |
6446 | | should set sliderIsSolid to true. (X |
6450 | | pixmap should be used to simulate grey. |
6454 | | the foreground color, shaded to look |
6458 | | Amount of time in milliseconds to wait |
6463 | | Amount of time to wait between repeating |
6474 | | is pressed to set the cursor position. A |
6481 | | restored to its previous position prior to |
6489 | | milliseconds to wait before blinking the |
6491 | | cursor to always blink. Setting |
6492 | | blinkInterval to zero will cause the cursor |
6493 | | to never blink which may be useful on some |
6494 | | display servers connected to very slow |
6495 | blinkInterval | networks. The disadvantage of setting it to |
6496 | | zero is that it is sometimes hard to tell |
6500 | | cause the cursor to blink only when |
6507 | | (bound to ^A-A), the attribute may be of |
6519 | | corresponding to the ANSI convention, while |
6520 | | bcolorN default to the window background. |
6521 | | If you wish to set bcolorN for special |
6522 | | effect, you should add this to your .vilerc |
6523 | | file set bcolor=fcolor to tell xvile to use |
6529 | menuHeader | The names given to the menu header and |
6537 | inputMethod | input method to use (default: "") |
6541 | wheelScrollAmount | Amount to scroll for a wheel mouse, per |
6547 You may or may not want to use the following as a starting point for the
6549 monochrome display server, you will probably not want to use any of the
6550 color specifications. You may, however, wish to set up a blinking cursor,
6569 The $font variable corresponds to the X11 font resource. To change the
6570 font on the fly, use the ':setv' command to set the $font variable, with
6575 a dash-separated list of attributes, or an alias to one of the known
6586 which is meant to be italic. The program xfontsel is quite useful for
6595 In this case, xvile uses the Xft and fontconfig libraries to derive
6598 Here are some tips on using xfontsel to find an appropriate font.
6600 1. Set rgstry (registry) to iso8859
6601 2. Set spc (spacing) to either "c" (cell font) or "m" (monospaced font).
6602 You will be more likely to find a font which will work as italic if
6606 (oblique). If neither of these are available, go back to step 2 and
6610 5. Set wght (weight) to medium. If you have a hard time seeing the
6611 characters, you might want to choose bold, but xvile will not be able
6612 to use the bold font for displaying bold text. It will be forced to
6613 overwrite text that it wants to be bold with the text shifted by one
6615 6. Set fmly (family) to a value according to personal taste. By this
6618 matter that much. Otherwise set these according to taste.
6619 8. Go back to the slant menu and change either the "i" or "o" to "r".
6621 This will be the font to use. xvile will be attempt to get the italic font
6625 (on many display servers) is pretty close to the size of the default font
6631 xvile. For longer term use, you will probably want to put it in your
6637 however, as you lose the ability to choose a different font from the
6638 command line or resource file. It may also cause the xvile window to be
6646 vile is perfectly happy (and even tries very hard) to use the UNIX-style
6650 strings. As an example setting "tags" to "tags ..\tags" will not have the
6654 unless you explicitly change it to a different mode with a "set sres="
6655 line in your vile.rc, or if you use a command line option to change it.
6657 selectors (these are the same values that can be assigned to "sres").
6672 to the "word under the cursor", is suppressed for DOS, due to the conflict
6690 Reading from a pipe works; writing to a pipe is not implemented.
6693 not supported due to conflicts with filename syntax delimiters. Use '&'
6700 completion only works for UNIX-style pathnames, since those allow us to
6715 vile accepts these command-line options in addition to the standard ones:
6730 | | Show all versions of files in response to filename |
6735 | flash | video to reverse color and then normal. If this |
6740 | record-format | undefined, vile will attempt to use the format of an |
6745 | record-attrs | If undefined, vile will attempt to use the format of |
6759 | $sres | setting this variable to either NORMAL or WIDE (e.g., :setv |
6765 With respect to VT100 and later terminal types, the editor assumes a vt220
6766 keyboard and maps special keys to their closest vile counterpart (e.g.,
6767 "Remove" mapped to vile's "Delete"). Some vt220 keyboard special keys have
6779 remainder of this section of the help file, a generic reference to "vile"
6780 refers to both the console and GUI editor, unless otherwise stated.
6791 Winvile accepts these command-line options in addition to the standard
6804 | | $pagelen and $pagewid may be used to change |
6810 | | directory to match this filename. This is used to |
6831 to and from the shell. One mechanism uses temporary files and the other
6839 mode is disabled by default and the editor falls back to temp files. Take
6842 appropriate and highly desirable to manually enable "w32pipes" (e.g., "se
6850 | See the "Shell" topic below to learn how to specify the editor's |
6876 Finally, it may be necessary to pass one or more flags to the shell
6879 Instead, use a macro similar to the following that supersedes the builtin
6883 ; pass -L (login) flag to MKS shell, assumes sh is
6894 In the example, the "1" preceding "shell-command" tells winvile to
6897 press any key to continue
6900 prompt, the console window which winvile opens to run a shell command will
6908 As it turns out, bash's signal handling is crafted to work best with other
6930 Selecting and dragging with the left mouse button yanks text to the
6931 unnamed register. Press a control key during the selection to sweep out a
6965 | Favorites | are added to the Favorites folder via the Windows |
6968 | | "Favorites" menu provides two-click access to the |
6975 | Menu | the unnamed register to the clipboard. When the popup |
6978 | | highlighted blocks of text to the clipboard. |
6980 | Undo | Bound to undo-changes-backward. |
6982 | Redo | Bound to redo-changes-forward. |
6985 | | copies same to clipboard. |
6987 | Copy | copies the current text selection to both the unnamed |
6997 The first six popup menu entries are added to the system menu (in the
7008 equivalent to executing ":cd <foldername>". This feature is disabled
7015 There are several ways to copy to/from the clipboard:
7017 * Copy data from the unnamed register to the windows clipboard via the
7018 copy-unnamed-reg-to-clipboard command (bound to Alt+Insert).
7019 * Copy data from a named register or region to the clipboard (a la
7020 vile's ^W operator) via the copy-to-clipboard-til command (bound to
7022 * The paste-from-clipboard command copies data from the clipboard to the
7023 current buffer (bound to Shift+Insert).
7024 * Finally, the cut-to-clipboard command deletes the current text
7025 selection and copies same to both the clipboard and the unnamed
7026 register (bound to Shift+Delete).
7030 4yy<AI> ;copy 4 lines from unnamed reg to clipboard
7031 "a<CI> ;copy register 'a' to clipboard
7032 "b<CI> ;copy register 'b' to clipboard
7033 <CI>3w ;copy 3 words to clipboard
7035 The swap-clipboard-keys command swaps the commands bound to Ctrl+Insert
7041 controlled by an OLE client. Refer to the file doc/oleauto.doc for further
7043 for substituting winvile as the default Developer Studio editor. Refer to
7048 Winvile's font may be set via a command-line switch or from within the
7086 Winvile uses the system registry to store persistent user settings. If you
7105 to a nonzero value.
7110 unreliable for installers to set environment variables directly on
7128 Delete the current text selection to the unnamed register. Bound
7129 to Alt+Delete.
7140 Set red/green/blue values to their initial state. If you give a
7141 parameter, this is used to specify a single color number.
7159 Launches the Windows common open dialog box to open one or more
7163 then Windows (and vile) implicitly change the cwd to match that of
7171 command to set page attributes before invoking winprint.
7178 Launches the Windows common save dialog box to save the current
7182 Windows (and vile) implicitly change the cwd to match that of the
7190 echo-to-clipboard
7191 all text selected with the mouse is automatically copied to the
7198 With respect to console vile, this string either specifies a
7205 Specifying 0 reverts to the cursor height in effect at editor
7209 With respect to winvile, this string specifies an integer in the
7232 An integer indicating the time in milliseconds to wait after
7244 Some vile commands and modes apply only to winvile and some only to
7245 console vile. If you plan to run both winvile and console vile in the
7246 context of a single startup file, you'll need to include code similar to
7267 argument, and will present it as the default reply to their prompt.
7274 '#' and '%' are recognized and expanded to the previous or current
7280 complex, to support the traditional nroff and troff boundaries. If you are
7281 just editing code, you may want to replace them:
7290 Of course, ex and open mode aren't there. (Too bad. I'd love to have a
7299 moves the cursor to the start of the Nth next line, where N is the
7300 argument given, less 1. So '2_' takes you to the start of the next line.
7302 always exactly equivalent in those cases to "stuttering" the operator, as
7312 Here's a sample .vilerc, to help get you started with the syntax and style
7332 ; position the cursor to add to the string
7344 ; for "goto-line" is to go to the end of file.
7350 ; it to be read back in.
7354 ; suppress "press return" with "1" argument to shell-command
7379 to the TERM variable. In addition, vile will attempt to support the
7380 SIGWINCH signal, which allows it to track changes to the size of the
7385 should be able to scroll okay, then the problem is almost certainly your
7405 attempt to use dl and al, and will scroll by deleting and inserting a
7411 Here is the terminfo entry equivalent to the above termcap entry:
7441 (kevin@buettner.to) and Paul Fox (pgf@foxharp.boston.ma.us).
7454 coloring infrastructure. On an ongoing basis, Tom continues to fix bugs
7462 interface to the editor. Rick Sladkey has done great stuff making vile
7469 inspired by code from the 'notgnu' editor, by Julie Melbin. Patches to
7476 vile commands to Perl subroutines. Better still, he also found a way to
7477 bind operators and motions to same. Kuntal Daftary added several Perl
7478 modules. Clark Morgan and Greg McFarlane seem to run full regression tests
7479 on each new release, and always seem to find something to report. In
7486 Thanks to Jukka Keto for contributing the c-filt.c code, which served as
7489 The initial changes to create vile from micro-Emacs were all done by Paul
7496 Where to Get It
7501 Up-to-date copies of vile, including executables for DOS, Win32 and OS/2
7529 Subscribing to the mailing list is also the best way to keep informed of