Debian Codegraph @

doc/cmds.nr

raw
1 .\"##########################################################################
2 .\"# This program is Copyright (C) 1986-2002 by Jonathan Payne. JOVE is #
3 .\"# provided by Jonathan and Jovehacks without charge and without #
4 .\"# warranty. You may copy, modify, and/or distribute JOVE, provided that #
5 .\"# this notice is included in all the source files and documentation. #
6 .\"##########################################################################
7 .\"
8 .\" cmds.nr: descriptions of each JOVE command and variable.
9 .\"
10 .\" This nroff/troff text is used for two purposes:
11 .\" it is the second portion of the JOVE manual (combine with intro.nr), and
12 .\" it is used to produce cmds.txt, the text used by the describe-command
13 .\" and describe-variable commands.
14 .\" Take note of the .IQ and .BQ macros used in this file to put text in
15 .\" italic or bold, and that their effect when producing cmds.txt is to
16 .\" enclose the relevant text within quotes. Do not use any other means of
17 .\" italicising or emboldening in this file.
18 .
19 .dc "abort-char" "(variable)"
20 This variable defines \s-2JOVE\s0'S abort character. When JOVE
21 reads this character from the keyboard, it stops what it is doing
22 (unless the character is quoted in some way). Unfortunately, JOVE
23 won't notice the character until it reads from the keyboard. The
24 default value is ^G. See also
25 .IQ interrupt-character .
26 .dc "add-lisp-special" "Not Bound"
27 This command is to tell \s-2JOVE\s0 what identifiers require special
28 indentation in lisp mode. Lisp functions like
29 .IQ defun
30 and
31 .IQ let
32 are two of
33 the default functions that get treated specially. This is just a kludge
34 to define some of your own. It prompts for the function name.
35 .dc "allow-^S-and-^Q" "(variable)"
36 This variable, when set, tells \s-2JOVE\s0 that your terminal will not need
37 to use the characters ^S and ^Q for flow control, in which case \s-2JOVE\s0
38 will instruct the system's tty driver to pass them through as normal
39 characters. Otherwise, if the tty driver was already using these characters
40 for flow control, it will continue to do so. Certain terminals and
41 communications systems require that this variable be set
42 .IQ off ;
43 in other circumstances it is better set
44 .IQ on .
45 .dc "allow-bad-characters-in-filenames" "(variable)"
46 If set, this variable permits the creation of filenames which contain
47 \*Qbad\*U characters
48 such as those from the set \(**&%!"`[]{}. These files are harder to deal
49 with, because the characters mean something to the shell. The default
50 value is
51 .IQ off .
52 .dc "append-region" "Not Bound"
53 This appends the region to a specified file. If the file does not
54 already exist it is created.
55 .dc "apropos" "Not Bound"
56 This types out each command, variable and macro with the specified
57 string in its name (\*Q?\*U matches every name).
58 For each command and macro that contains the
59 string, the key sequence that can be used to execute the command or macro is
60 printed; with variables, the current value is printed. So, to find all the
61 commands that are related to windows, you type
62 .DS
63 : apropos window<Return> .
64 .DE
65 .dc "auto-case-abbrev" "(variable)"
66 When this variable is
67 .IQ on
68 (the default), word abbreviations are adjusted for
69 case automatically. If the abbreviation is typed with no uppercase letter,
70 the expansion is not changed; if it is typed with one or more uppercase
71 letters, the first character in the expansion is capitalized;
72 additionally, if the abbreviation is typed with more than one uppercase letter,
73 each letter in the expansion immediately preceded by whitespace or \-
74 is capitalized.
75 For example, if \*Qjove\*U were the abbreviation for
76 \*Qjonathan's own version of EMACS\*U, the following table shows how the
77 abbreviation would be expanded.
78 .DS I
79 .ta \w'JOVE111'u
80 jove jonathan's own version of EMACS
81 Jove Jonathan's own version of EMACS
82 JOVE Jonathan's Own Version Of EMACS
83 JoVe Jonathan's Own Version Of EMACS
84 .DE
85 When this variable is
86 .IQ off ,
87 upper and lower case are
88 distinguished when looking for the abbreviation, i.e., in the example above,
89 \*QJOVE\*U and \*QJove\*U would not be expanded unless they were defined
90 separately. See also the
91 .IQ word-abbrev-mode
92 command.
93 .dc "auto-execute-command" "Not Bound"
94 This tells \s-2JOVE\s0 to execute a command automatically when a file whose
95 name matches a specified pattern is read. The first argument is the
96 command you wish to have executed.
97 The second argument is the pattern, a regular expression
98 that is matched against the start of the file name.
99 If you wish to match a suffix, start the pattern with \*Q.\(**\*U;
100 to match every file, use that as the whole pattern.
101 Any numeric argument
102 will be passed on to the command when it is executed (this is
103 useful when combined with commands that adjust a minor mode).
104 For example, if you want
105 to be in
106 .IQ show-match-mode
107 when you edit C source files (that is, files
108 that end with
109 .BQ .c
110 or
111 .BQ .h )
112 you can type
113 .DS
114 : auto-execute-command show-match-mode .\(**\^\e\^.[ch]$
115 .DE
116 Actually, this command toggles the Show Match minor mode,
117 but since it is initially off, it will have the desired effect. For
118 more certain control, give the
119 .IQ auto-execute-command
120 a non-zero numeric
121 argument: this will be passed on to the
122 .IQ show-match-mode .
123 .dc "auto-execute-macro" "Not Bound"
124 This is like
125 .IQ auto-execute-command
126 except you use it to execute macros
127 automatically instead of built-in commands.
128 .dc "auto-fill-mode" "Not Bound"
129 This turns on or off the Auto Fill minor mode in the selected buffer.
130 Without a numeric argument, the command toggles the mode; with a
131 zero argument, the mode is turned off; with a non-zero argument,
132 the mode is turned on. When \s-2JOVE\s0 is in Auto Fill mode it
133 automatically breaks lines for you when you reach the right margin
134 so you don't have to remember to hit Return. \s-2JOVE\s0 uses 78 as
135 the right margin but you can change that by setting the variable
136 .IQ right-margin
137 to another
138 value.
139 .dc "auto-indent-mode" "Not Bound"
140 This turns on or off Auto Indent minor mode in the selected buffer.
141 Without a numeric argument, the command toggles the mode; with a
142 zero argument, the mode is turned off; with a non-zero argument,
143 the mode is turned on. When \s-2JOVE\s0 is in Auto Indent mode,
144 the
145 .IQ newline
146 command (which is normally bound to Return) acts identically to
147 .IQ newline-and-indent :
148 the new line is indented to the same position as the line you
149 were just on. This is useful for lining up C code (or any other
150 language (but what else is there besides C?)).
151 Furthermore, if a line is broken because of Auto Fill mode, and
152 Auto Indent mode is on, the new line will be indented as the old line was.
153 .dc "backward-character" "^B"
154 This moves point backward over a single character or line-separator.
155 Thus if point is at the
156 beginning of the line it moves to the end of the previous line.
157 .dc "backward-list" "ESC\ ^P"
158 This moves point backward over a list, which is any text between properly
159 matching (\^...\^), [\^...\^] or {\^...\^}.
160 It first searches backward for a \*Q)\*U and then moves to the
161 matching \*Q(\*U.
162 This is useful when you are trying to find unmatched parentheses in a program.
163 Arguments are accepted, and negative arguments search forwards.
164 See also
165 .IQ backward-s-expression .
166 .dc "backward-paragraph" "Usually Not Bound"
167 This moves point backward to the beginning of the current or previous
168 paragraph. Paragraphs are bounded by lines that match
169 .IQ paragraph-delimiter-pattern
170 (by default, those that are empty or look like troff or TeX commands).
171 A change in indentation may also signal a break
172 between paragraphs, except that \s-2JOVE\s0 allows the first line of a
173 paragraph to be indented differently from the other lines.
174 Arguments are accepted, and negative arguments search forwards.
175 .dc "backward-s-expression" "ESC\ ^B"
176 This moves point backward over an s-expression, that is over a Lisp atom or
177 a C identifier (depending on the major mode) ignoring punctuation and
178 whitespace; or, if the nearest preceding significant character is one of
179 \*Q)]}\*U, over a list as in
180 .IQ backward-list .
181 Arguments are accepted, and negative arguments search forwards.
182 .dc "backward-sentence" "ESC\ A"
183 This moves point backward to the beginning of the current or previous
184 sentence. \s-2JOVE\s0 considers the end of a sentence to be the characters
185 \*Q.\*U, \*Q!\*U or \*Q?\*U followed by a Return or by one or more spaces.
186 Arguments are accepted, and negative arguments search forwards.
187 .dc "backward-up-list" "ESC\ ^U"
188 This is similar to
189 .IQ backward-list
190 except it backs up and OUT of the enclosing list. In other
191 words, it moves backward to whichever of \*Q([{\*U would match one of
192 \*Q)]}\*U if you were to type it right then.
193 Arguments are accepted, and negative arguments search forwards as in
194 .IQ down-list .
195 .dc "backward-word" "ESC\ B"
196 This moves point backward to the beginning of the current or previous
197 word.
198 Arguments are accepted, and negative arguments search forwards.
199 .dc "bad-filename-extensions" "(variable)"
200 This contains a list of words separated by spaces which are to be
201 considered bad filename extensions, and so will not be included in
202 filename completion. The default contains, amongst much else,
203 .BQ .o
204 so if you have
205 .BQ jove.c
206 and
207 .BQ jove.o
208 in the same directory, the filename completion will not complain
209 of an ambiguity because it will ignore
210 .BQ jove.o .
211 .dc "begin-kbd-macro" "^X\ ("
212 This starts defining the keyboard macro by remembering all your key
213 strokes until you execute
214 .IQ end-kbd-macro ,
215 by typing \*Q^X\ )\*U. Because of a bug in \s-2JOVE\s0 you shouldn't
216 terminate the macro by typing \*QESC\ X end-kbd-macro\*U;
217 .IQ end-kbd-macro
218 must be bound to \*Q^X\ )\*U in order to make things work correctly.
219 The
220 .IQ execute-kbd-macro
221 command will execute the remembered key strokes.
222 Sometimes you may want a macro to accept different input each time it runs.
223 To see how to do this, see the
224 .IQ make-macro-interactive
225 command.
226 .dc "beginning-of-file" "ESC\ <"
227 This moves point backward to the beginning of the buffer. This sometimes
228 prints the \*Q[Point pushed]\*U message to indicate that
229 \s-2JOVE\s0 has set the mark so you can go back to where you were
230 if you want.
231 See also the variable
232 .IQ mark-threshold .
233 .dc "beginning-of-line" "^A"
234 This moves point to the beginning of the current line.
235 .dc "beginning-of-window" "ESC\ ,"
236 This moves point to the beginning of the active window. If there
237 is a numeric argument, point moves that many lines below the top
238 line. With the default bindings, the sequence \*QESC\ ,\*U is the same as
239 \*QESC\ <\*U (\c
240 .IQ beginning-of-file )
241 but without the shift key on the \*Q<\*U,
242 and can thus easily be remembered.
243 .dc "bind-keymap-to-key" "Not Bound"
244 This is like
245 .IQ bind-to-key
246 except that you use it to attach a key sequence to a named keymap.
247 The only reasonable use is to bind some extra key to
248 .IQ ESC-map
249 for keyboards that make typing ESC painful.
250 .dc "bind-macro-to-key" "Not Bound"
251 This is like
252 .IQ bind-to-key
253 except you use it to attach a key sequence to a named macro.
254 .dc "bind-macro-to-word-abbrev" "Not Bound"
255 This command allows you to bind a macro to a previously defined word
256 abbreviation. Whenever you type the abbreviation, it will first be
257 expanded as an abbreviation (which could be empty, of course), and then
258 the macro will be executed.
259 Note that if the macro moves point around, you should first
260 .IQ set-mark
261 and then
262 .IQ exchange-point-and-mark .
263 .dc "bind-to-key" "Not Bound"
264 This attaches a key sequence to an internal \s-2JOVE\s0 command so
265 that future hits on that key sequence invoke that command. This is
266 called a global binding, as compared to local bindings and process
267 bindings. Any previous global binding of this key sequence is
268 discarded. For example, to make \*Q^W\*U erase the previous word, you
269 type
270 .DS
271 : bind-to-key kill-previous-word ^W .
272 .DE
273 It isn't possible to have two globally bound key sequences where one
274 is a prefix of the other: \s-2JOVE\s0 wouldn't know whether to obey
275 the shorter sequence or wait for the longer sequence. Normally, when
276 the
277 .IQ bind-to-key
278 command is issued interactively, the key sequence is taken to end
279 one keystroke after the longest sequence matching any proper prefix
280 of another binding (thus no new prefix can be created). If the command
281 is given a numeric argument, the key sequence is taken up to the
282 next Return keystroke (kludge!); bindings to any prefix of the
283 sequence are discarded. When the command is issued from a
284 .IQ source d
285 file, the
286 key sequence is taken up to the end of the line (it is also
287 processed so that control characters can and should be entered using
288 the ^A notation).
289
290 Note that neither process nor local bindings are changed by
291 this command, although they can be eclipsed. Given a choice between
292 bindings, the shortest is executed; if there is still a choice,
293 a process binding is preferred to a local binding, and a local
294 binding is preferred to a global binding.
295 .dc "buffer-position" "Not Bound"
296 This displays the current file name, current line number, total number
297 of lines, current character number, total number of characters,
298 percentage of the way through the file, and the position of
299 the cursor in the current line.
300 .dc "c-argument-indentation" "(variable)"
301 This variable describes how to indent lines which are part of nested
302 expressions in C. The default is \-1, which means to indent a continued
303 line by lining it up with the first argument of the current expression.
304 Otherwise, the line will be indented by
305 .IQ c-argument-indentation
306 characters
307 past the indent of the first line of the expression. For example, the
308 default value produces:
309 .DS
310 .nr TY \w'Typeout('
311 Typeout(fmt, itoa(bcount++), line_cnt(b, nbuf),
312 \h'\n(TYu'TypeNames[b->b_type],
313 \h'\n(TYu'IsModified(b) ? "\(**" : b->b_ntbf ? "+" : NullStr,
314 \h'\n(TYu'buf_width, b->b_name, filename(b));
315 .DE
316 .dc "c-indentation-increment" "(variable)"
317 This defines a set of tabstops independent of the value of
318 .IQ tab-width .
319 This value will be used in C
320 mode, and \s-2JOVE\s0 will insert the correct number of Spaces and Tabs to
321 get the right behavior. For programmers that like to indent with 4 spaces,
322 set this value to 4. Some people prefer to set this to 4 and leave
323 tab-width set to 8. This will create files whose indentation steps in
324 4-space increments, and which look the same anywhere that tabs are expanded
325 to 8 spaces (i.e. in most settings). Others prefer to have one tab
326 character per indentation level, then fiddle the tab expansion width to get
327 the appearance they like. They should set both
328 .IQ c-indentation-increment
329 and
330 .IQ tab-width
331 to 4. Whenever using a non-standard tab width
332 (\c
333 .IQ tab-width )
334 you should only use tabs for indentation, and use
335 spaces for all columnar alignment later in the lines.
336 .dc "c-mode" "Not Bound"
337 This turns on the C major mode in the currently selected buffer.
338 When in C or Lisp mode, Tab, \*Q}\*U, and \*Q)\*U behave a little differently
339 from usual: They are indented to the \*Qright\*U place for C (or Lisp)
340 programs. In \s-2JOVE\s0, the \*Qright\*U place is simply the way the author
341 likes it (but I've got good taste).
342 .dc "case-character-capitalize" "Not Bound"
343 This capitalizes the character after point, i.e., the character under
344 the cursor. If a negative argument is supplied that many characters
345 before point are upper cased.
346 .dc "case-ignore-search" "(variable)"
347 This variable, when
348 .IQ on ,
349 tells \s-2JOVE\s0 to treat upper and lower case
350 the same when searching. Thus \*Qjove\*U would match \*QJOVE\*U, and
351 \*QJoVe\*U would match either. The default value of this variable is
352 .IQ off .
353 .dc "case-region-lower" "Not Bound"
354 This changes all the upper case letters in the region to their lower
355 case equivalents.
356 .dc "case-region-upper" "Not Bound"
357 This changes all the lower case letters in the region to their upper
358 case equivalents.
359 .dc "case-word-capitalize" "ESC\ C"
360 This capitalizes the current word by making the current letter upper
361 case and making the rest of the word lower case. Point is moved to
362 the end of the word. If point is not positioned on a word it is first
363 moved forward to the beginning of the next word. If a negative
364 argument is supplied that many words
365 before point are capitalized.
366 This is useful for correcting the word just typed without having to
367 move point to the beginning of the word yourself.
368 .dc "case-word-lower" "ESC\ L"
369 This lower-cases the current word and leaves point at the end of it.
370 If point is in the middle of a word the rest of the word is
371 converted. If point is not in a word it is first moved forward to the
372 beginning of the next word. If a negative argument is supplied that
373 many words before
374 point are converted to lower case. This is useful
375 for correcting the word just typed without having to move point to the
376 beginning of the word yourself.
377 .dc "case-word-upper" "ESC\ U"
378 This upper-cases the current word and leaves point at the end of it.
379 If point is in the middle of a word the rest of the word is
380 converted. If point is not in a word it is first moved forward to the
381 beginning of the next word. If a negative argument is supplied that
382 many words before
383 point are converted to upper case. This is useful
384 for correcting the word just typed without having to move point to the
385 beginning of the word yourself.
386 .dc "cd" "Not Bound"
387 This changes the current directory.
388 .dc "character-to-octal-insert" "Not Bound"
389 This inserts a Back-slash followed by the ascii value of the next
390 character typed. For example, \*Q^G\*U inserts the string \*Q\^\e\^007\*U.
391 .dc "clear-and-redraw" "ESC\ ^L"
392 This clears the entire screen and redraws all the windows. Use this
393 when \s-2JOVE\s0 gets confused about what's on the screen, or when the screen
394 gets filled with garbage characters or output from another program.
395 .dc "comment-format" "(variable)"
396 This variable tells \s-2JOVE\s0 how to format your comments when you run the
397 command
398 .IQ fill-comment .
399 Its format is this:
400 .ID
401 <open pattern>%!<line header>%c<line trailer>%!<close pattern>
402 .DE
403 The %!, %c, and %! must appear in the format; everything else is optional.
404 A newline (represented by %n) may appear in the open or close patterns. %%
405 is the representation for %. The default comment format is for C comments.
406 See
407 .IQ fill-comment
408 for more details.
409 .dc "compile-it" "^X\ ^E"
410 This compiles your program by running the
411 .B UNIX
412 command
413 .IQ make
414 into a buffer,
415 and automatically parsing the error messages that are created (if any). See
416 the
417 .IQ parse-errors
418 command.
419 If
420 .IQ compile-it
421 is given a numeric argument, it will prompt for a command to run in
422 place of the plain make and the command you enter will become the new
423 default. See also
424 .IQ error-format-string
425 which makes it possible to parse errors of a different format and
426 see also the variable
427 .IQ error-window-size .
428 .dc "continue-process" "Not Bound"
429 This sends the signal SIGCONT to the interactive process in the current
430 buffer, IF the process is currently stopped.
431 .dc "copy-region" "ESC\ W"
432 This takes all the text in the region and copies it onto the kill ring
433 buffer. This is just like running
434 .IQ kill-region
435 followed by the
436 .IQ yank
437 command. See the
438 .IQ kill-region
439 and
440 .IQ yank
441 commands.
442 .dc "current-error" "Not Bound"
443 This moves to the current error in the list of parsed errors. See the
444 .IQ next-error
445 and
446 .IQ previous-error
447 commands for more detailed
448 information.
449 .dc "date" "Not Bound"
450 This prints the date on the message line.
451 .dc "dbx-format-string" "(variable)"
452 This is the default regular-expression search string used by \s-2JOVE\s0 to
453 parse output from
454 .IQ dbx
455 running in a shell process (see the
456 .IQ dbx-mode
457 command). You shouldn't have to change
458 this unless you are using something other than
459 .IQ DBX .
460 .dc "dbx-mode" "Not Bound"
461 This turns on or off the DBX minor mode in the selected
462 buffer. Without a numeric argument, the command toggles the mode;
463 with a zero argument, the mode is turned off; with a non-zero
464 argument, the mode is turned on.
465 This mode only makes sense in a buffer running an interactive shell
466 process. If you are running
467 .IQ dbx
468 in a window and and the buffer is in DBX minor mode, \s-2JOVE\s0 will
469 automatically track the source location in another window.
470 Whenever you type \*Qwhere\*U or while you're stepping through a
471 program, or when you reach a breakpoint, \s-2JOVE\s0 will present the
472 source file in another window and move to the line that is being referenced.
473 See also the variable
474 .IQ dbx-format-string .
475 .dc "define-global-word-abbrev" "Not Bound"
476 This defines a global abbreviation.
477 See the
478 .IQ word-abbrev-mode
479 command.
480 .dc "define-macro" "Not Bound"
481 This provides a different mechanism for defining keyboard macros.
482 Instead of gathering keystrokes and storing them into the
483 \*Qkeyboard-macro\*U (which is how
484 .IQ begin-kbd-macro
485 works),
486 .IQ define-macro
487 prompts for a macro name (terminated with Space, or Newline) and then for
488 the actual macro body. If you wish to specify control characters in the
489 macro, you may simply insert them (using the
490 .IQ quoted-insert
491 command) or by inserting the character '^' followed by the appropriate
492 letter for that character (e.g., ^A would be the two characters '^'
493 followed by 'A'). You may use Back-slash to prevent the '^' from being
494 interpreted as part of a control character when you really wish to insert
495 one (e.g., a macro body \*Q\^\e\^^foo\*U would insert the string \*Q^foo\*U
496 into the buffer, whereas the body \*Q^foo\*U would be the same as typing ^F
497 and then inserting the string \*Qoo\*U). See
498 .IQ write-macros-to-file
499 to see how to save macros.
500 .dc "define-mode-word-abbrev" "Not Bound"
501 This defines a mode-specific abbreviation.
502 See the
503 .IQ word-abbrev-mode
504 command.
505 .dc "delete-blank-lines" "^X\ ^O"
506 This deletes all the blank lines around point. This is useful when you
507 previously opened many lines with the
508 .IQ newline-and-backup
509 command and now wish to delete the unused ones.
510 .dc "delete-buffer" "^X\ K"
511 This deletes a buffer and frees up all the memory associated with it. Be
512 careful(!) - once a buffer has been deleted it is gone forever. \s-2JOVE\s0
513 will ask you to confirm if you try to delete a buffer that needs saving.
514 This command is useful for when \s-2JOVE\s0 runs out of space to store
515 new buffers.
516 See also the
517 .IQ erase-buffer
518 command and the
519 .IQ kill-some-buffers
520 command.
521 .dc "delete-current-window" "^X\ D)"
522 This deletes the active window and moves point into one of the
523 remaining ones. It is an error to try to delete the only remaining
524 window.
525 .dc "delete-next-character" "^D"
526 This deletes the character that's just after point (that is, the
527 character under the cursor). If point is at the end of a line, the
528 line-separator is deleted and the next line is joined with the current
529 one.
530 If an argument is given, that many characters are deleted and placed on the
531 kill ring. If the argument is negative the deletion is forwards.
532 .dc "delete-other-windows" "^X\ 1"
533 This deletes all the other windows except the current one. This can be
534 thought of as going back into One Window mode.
535 .dc "delete-previous-character" "DEL and ^H"
536 This deletes the character that's just before point (that is, the
537 character before the cursor). If point is at the beginning of the
538 line, the line separator is deleted and that line is joined with the
539 previous one.
540 If an argument is given, that many characters are deleted and placed on the
541 kill ring. If the argument is negative the deletion is backwards.
542 .dc "delete-white-space" "ESC\ \e\^"
543 This deletes all the Tabs and Spaces around point.
544 .dc "describe-bindings" "Not Bound"
545 This types out a list containing each bound key and the command that gets
546 invoked every time that key is typed. To make a wall chart of \s-2JOVE\s0
547 commands, set
548 .IQ send-typeout-to-buffer
549 to
550 .IQ on
551 and \s-2JOVE\s0 will
552 store the key bindings in a buffer which you can save to a file and then
553 print.
554 .dc "describe-command" "ESC\ ?"
555 This waits for you to type a command and then prints an explanation of that
556 command, together with its current bindings.
557 .dc "describe-key" "^X\ ?"
558 This waits for you to type a key and then tells the name of the
559 command that gets invoked every time that key is hit. Once you have
560 the name of the command you can use the
561 .IQ describe-command
562 command
563 to find out exactly what it does.
564 .dc "describe-variable" "Not Bound"
565 This prints an explanation of a specified variable.
566 .dc "digit" "ESC\ 0 through ESC\ 9"
567 Starts or continues the entry of a numeric argument with the digit typed.
568 It continues reading digits until you type some other command.
569 Then that command is executed with the numeric argument you specified.
570 .dc "digit-0" "Not Bound"
571 Starts or continues the entry of a numeric argument with the digit 0.
572 It continues reading digits until you type some other command.
573 Then that command is executed with the numeric argument you specified.
574 Sometimes it is handy to bind this to the 0 key on the numeric keypad.
575 .dc "digit-1" "Not Bound"
576 Starts or continues the entry of a numeric argument with the digit 1.
577 It continues reading digits until you type some other command.
578 Then that command is executed with the numeric argument you specified.
579 Sometimes it is handy to bind this to the 1 key on the numeric keypad.
580 .dc "digit-2" "Not Bound"
581 Starts or continues the entry of a numeric argument with the digit 2.
582 It continues reading digits until you type some other command.
583 Then that command is executed with the numeric argument you specified.
584 Sometimes it is handy to bind this to the 2 key on the numeric keypad.
585 .dc "digit-3" "Not Bound"
586 Starts or continues the entry of a numeric argument with the digit 3.
587 It continues reading digits until you type some other command.
588 Then that command is executed with the numeric argument you specified.
589 Sometimes it is handy to bind this to the 3 key on the numeric keypad.
590 .dc "digit-4" "Not Bound"
591 Starts or continues the entry of a numeric argument with the digit 4.
592 It continues reading digits until you type some other command.
593 Then that command is executed with the numeric argument you specified.
594 Sometimes it is handy to bind this to the 4 key on the numeric keypad.
595 .dc "digit-5" "Not Bound"
596 Starts or continues the entry of a numeric argument with the digit 5.
597 It continues reading digits until you type some other command.
598 Then that command is executed with the numeric argument you specified.
599 Sometimes it is handy to bind this to the 5 key on the numeric keypad.
600 .dc "digit-6" "Not Bound"
601 Starts or continues the entry of a numeric argument with the digit 6.
602 It continues reading digits until you type some other command.
603 Then that command is executed with the numeric argument you specified.
604 Sometimes it is handy to bind this to the 6 key on the numeric keypad.
605 .dc "digit-7" "Not Bound"
606 Starts or continues the entry of a numeric argument with the digit 7.
607 It continues reading digits until you type some other command.
608 Then that command is executed with the numeric argument you specified.
609 Sometimes it is handy to bind this to the 7 key on the numeric keypad.
610 .dc "digit-8" "Not Bound"
611 Starts or continues the entry of a numeric argument with the digit 8.
612 It continues reading digits until you type some other command.
613 Then that command is executed with the numeric argument you specified.
614 Sometimes it is handy to bind this to the 8 key on the numeric keypad.
615 .dc "digit-9" "Not Bound"
616 Starts or continues the entry of a numeric argument with the digit 9.
617 It continues reading digits until you type some other command.
618 Then that command is executed with the numeric argument you specified.
619 Sometimes it is handy to bind this to the 9 key on the numeric keypad.
620 .dc "digit-minus" "ESC\ \-"
621 Starts the entry of a numeric argument with a minus sign.
622 It continues reading digits until you type some other command.
623 Then that command is executed with the numeric argument you specified.
624 Sometimes it is handy to bind this to the \- key on a numeric keypad.
625 In the absence of further digits and unless otherwise stated (e.g.
626 .IQ next-page "),"
627 the argument \-1 is assumed.
628 .dc "dirs" "Not Bound"
629 This prints out the directory stack. See the
630 .IQ cd ,
631 .IQ pushd ,
632 .IQ pushlibd
633 and
634 .IQ popd
635 commands for more information.
636 .dc "display-default-filenames" "(variable)"
637 If this is set when \s-2JOVE\s0 asks for a filename, it will display the
638 default (unless that would take too much of the prompt line).
639 .dc "display-filenames-with-bad-extensions" "(variable)"
640 This variable affects only filename completion, in particular, what
641 happens when \*Q?\*U is typed while prompting for a file. When this variable
642 is
643 .IQ on ,
644 any files that end with one of the extensions defined by the
645 variable
646 .IQ bad-filename-extensions
647 will be displayed with an \*Q!\*U in front of their names. When
648 .IQ display-filenames-with-bad-extensions
649 is
650 .IQ off
651 the files will not be displayed at all. The default value
652 is
653 .IQ on .
654 .dc "down-list" "ESC\ ^D"
655 This is the opposite of
656 .IQ backward-up-list .
657 It enters the next list. In other
658 words, it moves forward to whichever of \*Q([{\*U it first encounters.
659 Arguments are accepted, and negative arguments search backwards as in
660 .IQ backward-up-list .
661 .dc "dstop-process" "Proc: ^C\ ^Y"
662 Send the signal SIGTSTP to the interactive process in the selected buffer when
663 next it tries to read input. This is equivalent to sending the \*Qdsusp\*U
664 character (which most people have set to ^Y) to the process.
665 This only works if you are in a buffer bound to an interactive process.
666 .dc "edit-word-abbrevs" "Not Bound"
667 This creates (if necessary) a buffer with a list of each abbreviation and
668 the phrase
669 it expands into, and enters a recursive edit to let you change the
670 abbreviations or add some more. The format of this list is
671 \*Qabbreviation:phrase\*U so if you add some more you should follow that
672 format. It's probably simplest just to copy some already existing
673 abbreviations and edit them. Use the
674 .IQ exit-jove
675 command to exit the recursive edit.
676 .dc "end-kbd-macro" "^X\ )"
677 This stops the definition of the keyboard macro. Because of a bug in
678 \s-2JOVE\s0, this must be bound to \*Q^X\ )\*U, or some key sequence which is
679 one or two characters long. Anything else will not work properly.
680 See
681 .IQ begin-kbd-macro
682 for more details.
683 .dc "end-of-file" "ESC\ >"
684 This moves point forward to the end of the buffer. This sometimes
685 prints the \*Q[Point pushed]\*U message to indicate that
686 \s-2JOVE\s0 has set the mark so you can go back to where you were
687 if you want.
688 See also the variable
689 .IQ mark-threshold .
690 .dc "end-of-line" "^E"
691 This moves point to the end of the current line. If the line is too
692 long to fit on the screen, it will be scrolled horizontally.
693 This is described with the variables
694 .IQ scroll-width
695 and
696 .IQ scroll-all-lines .
697 .dc "end-of-window" "ESC\ ."
698 This moves point to the last character in the active window. If there is a
699 numeric argument, the point moves that many lines above the bottom
700 line. With the default bindings, the sequence \*QESC\ .\*U is the same as
701 \*QESC\ >\*U (\c
702 .IQ end-of-file )
703 but without the shift key on the \*Q>\*U,
704 and can thus easily be remembered.
705 .dc "enhanced-keyboard" "(variable)"
706 (IBM PC version only) This is a boolean variable which can be set to
707 enable the enhanced AT-style keyboard. The enhanced keyboard contains
708 function keys and key combinations that are not supported on the
709 original IBM PCs and XTs. The default value is determined by a bit in
710 the BIOS data area, but this method apparently does not work with a
711 few BIOS implementations. WARNING: setting enhanced-keyboard
712 .IQ on
713 on systems without an enhanced keyboard will lock up your
714 system and require you to reboot.
715 .dc "eof-process" "^C\ ^D"
716 Sends EOF to the current interactive process. This only works on
717 versions of \s-2JOVE\s0 running under versions of
718 .B UNIX
719 with pty's.
720 .dc "erase-buffer" "Not Bound"
721 This erases the contents of the specified buffer. This is like
722 .IQ delete-buffer
723 except it only erases the contents of the buffer, not
724 the buffer itself. If you try to erase a buffer that needs saving you
725 will be asked to confirm it.
726 .dc "error-format-string" "(variable)"
727 This is the error format string that is used by
728 .IQ parse-errors
729 to find the error messages in a buffer. The way it works is by using
730 this string as a \s-2JOVE\s0 regular expression search string, where the
731 \e\^(\^...\^\e) regular expression feature is used to pick out the
732 file name and line number from the line containing an error message. For
733 instance, a typical error message might look like this:
734 .sp 1
735 "file.c", line 540: missing semi-colon
736 .sp 1
737 For strings of this format, an appropriate value for
738 .IQ error-format-string
739 would be something like this:
740 .sp 1
741 ^"\^\e\^([^"]\(**\^\e)", line \e\^([0-9]\(**\^\e):
742 .sp 1
743 What this means is, to find an error message, search for a line beginning
744 with a double-quote. Then it says that all the following characters up
745 to another double-quote should be remembered as one unit, namely the
746 filename that the error is in (that is why the first set of parentheses is
747 surrounding it). Then it says that after the filename there will be the
748 string \*Q, line \*U followed by a line number, which should be remembered as
749 a single unit (which is why the second set of parentheses is around that).
750 The only constraint on the error messages is that the file name and line
751 number appear on the same line. Most compilers seem to do this anyway, so
752 this is not an unreasonable restriction.
753 .sp 1
754 If you do not know how to use regular expressions then this variable will
755 be hard for you to use. Also note that you can look at the default
756 value of this variable by printing it out, but it is a really complicated
757 string because it is trying to accommodate the outputs of more than one
758 compiler.
759 .dc "error-window-size" "(variable)"
760 This is the percentage of the screen to use for the error-window on the
761 screen. When you execute
762 .IQ compile-it
763 or
764 .IQ spell-buffer ,
765 .IQ error-window-size
766 percent of the screen will go to the error window. If the window already
767 exists and is a different size, it is made to be this size. The default
768 value is 20%.
769 .dc "exchange-point-and-mark" "^X\ ^X"
770 This moves point to mark and makes mark the old point. This is for
771 quickly moving from one end of the region to the other.
772 .dc "execute-kbd-macro" "^X\ E"
773 This executes the keyboard macro. If you supply a numeric argument the
774 macro is executed that many times.
775 See the
776 .IQ begin-kbd-macro
777 command for more details.
778 .dc "execute-macro" "Not Bound"
779 This executes a specified macro. If you supply a numeric argument the
780 macro is executed that many times.
781 .dc "execute-named-command" "ESC\ X"
782 This is the way to execute a command that isn't bound to any key. When you
783 are prompted with \*Q:\ \*U you can type the name of the command. You don't
784 have to type the entire name. After typing a few characters, Tab will fill
785 in as many more as it can (as will Space, but that will also obey the
786 command if it is now unambiguous). If you are not sure of the name of the
787 command, type \*Q?\*U and \s-2JOVE\s0 will print a list of all the commands
788 that you could possibly match given what you've already typed. Once the
789 command is unambiguous, typing Return will cause it to be obeyed.
790
791 If you don't have any idea what the command's name
792 is but you know it has something to do with windows (for example), you
793 can do \*QESC\ X apropos window\*U and \s-2JOVE\s0 will print a list of all
794 the commands that are related to windows. If you find yourself
795 constantly executing the same commands this way you probably want to bind
796 them to keys so that you can execute them more quickly. See the
797 .IQ bind-to-key
798 command.
799 .dc "exit-jove" "^X\ ^C"
800 This exits \s-2JOVE\s0. If any buffers need saving \s-2JOVE\s0 will print
801 a warning message and ask for confirmation. If you leave without saving your
802 buffers all your work will be lost. If you made a mistake and really
803 do want to exit then you can.
804 If there are any interactive processes running, \s-2JOVE\s0 will also ask
805 whether they should be terminated.
806
807 If you are in a recursive editing level
808 .IQ exit-jove
809 will return you from that. The selected buffer will be set back to
810 the buffer that was current when the recursive edit was entered.
811 Normally, point will be returned to its position at the time of
812 entry, but if the
813 .IQ exit-jove
814 command is given a numeric argument,
815 point is left at its most recent position within that buffer.
816 .dc "expand-environment-variables" "(variable)"
817 When this variable is
818 .IQ on
819 \s-2JOVE\s0 will try to expand any strings of the form
820 \*Q$var\*U into the value of the environment variable \*Qvar\*U when asking for
821 a filename. For example, if you type
822 .BQ $HOME/.joverc ,
823 \*Q$HOME\*U will be
824 replaced with your home directory. The default value is
825 .IQ on .
826 .dc "file-creation-mode" "(variable)"
827 This variable has an octal value. It contains the mode (see
828 .IQ chmod (1))
829 with which files should be created. This mode gets
830 modified by your current umask setting (see
831 .IQ umask (1)).
832 The default value is usually
833 0666 or 0644.
834 .dc "files-should-end-with-newline" "(variable)"
835 This variable indicates that all files should always have a newline
836 at the end. This is often necessary for line printers and the like.
837 When set, if \s-2JOVE\s0 is writing a file whose last character is not a
838 newline, it will add one automatically.
839 The default value is
840 .IQ on .
841 .dc "fill-comment" "Not Bound"
842 This command fills in your C comments to make them pretty and readable.
843 This filling is done according the variable
844 .IQ comment-format .
845 .DS
846 /\(**
847 \(** the default format makes comments like this.
848 \(**/
849 .DE
850 This can be changed by changing the
851 .IQ comment-format
852 variable. Other languages
853 may be supported by changing the format variable appropriately. The
854 formatter looks backwards from point for an open comment symbol. If
855 found, all indentation is done relative to the position of the first character
856 of the open symbol. If there is a matching close symbol, the entire
857 comment is formatted. If not, the region between the open symbol and point
858 is reformatted. The original text is saved in the kill ring; a
859 .IQ yank-pop
860 command will undo the formatting.
861 .dc "fill-paragraph" "ESC\ J"
862 This rearranges words between lines so that all the lines in the current
863 paragraph extend as close to the right margin as possible, ensuring that
864 none of the lines will be greater than the right margin. The default value
865 for
866 .IQ right-margin
867 is 78, but can be changed with the
868 .IQ set
869 and
870 .IQ right-margin-here
871 commands.
872
873 The rearrangement may cause an end of line to be replaced by whitespace.
874 Normally, this whitespace is a single space character.
875 If the variable
876 .IQ space-sentence-2
877 is
878 .IQ on ,
879 and the end of the line was apparently the end of a sentence
880 or the line ended with a colon, two spaces will be used.
881 However, a sentence or colon followed by a single space already within
882 a line will not be altered.
883
884 \s-2JOVE\s0 has a complicated algorithm
885 for determining the beginning and end of the paragraph. In the normal case
886 \s-2JOVE\s0 will give all the lines the same indent as they currently have,
887 but if you wish to force a new indent you can supply a numeric argument to
888 .IQ fill-paragraph
889 and \s-2JOVE\s0 will indent each line to the column
890 specified by the
891 .IQ left-margin
892 variable. See also the
893 .IQ left-margin
894 variable and
895 .IQ left-margin-here
896 command.
897
898 Filling a paragraph can do something that you didn't intend. For that
899 reason the original text is saved on the kill ring and can be yanked
900 back. Deleting the rubble is up to you.
901 .dc "fill-region" "Not Bound"
902 This is like
903 .IQ fill-paragraph ,
904 except it operates on a region instead of
905 just a paragraph.
906 .dc "filter-region" "Not Bound"
907 This sends the text in the region to a
908 .B UNIX
909 command, and replaces the
910 region with the output from that command. For example, if you are
911 lazy and don't like to take the time to write properly indented C
912 code, you can put the region around your C file and
913 .IQ filter-region
914 it through
915 .IQ cb ,
916 the
917 .B UNIX
918 C beautifier. If you have a file that contains
919 a bunch of lines that need to be sorted you can do that from inside
920 \s-2JOVE\s0 too, by filtering the region through the
921 .B UNIX
922 .IQ sort
923 command.
924 Before output from the command replaces the region \s-2JOVE\s0 stores the old
925 text in the kill ring. If you are unhappy with the results a
926 .IQ yank-pop
927 command will get back the old text.
928 .dc "find-file" "^X\ ^F"
929 This reads a specified file into its own buffer and then selects that buffer.
930 If you've already read this file into a buffer, that buffer is simply
931 selected. If the file doesn't yet exist, \s-2JOVE\s0 will
932 print \*Q(New file)\*U so that you know.
933 If possible, the buffer is named after the filename (ignoring any directory
934 part).
935 .dc "find-tag" "^X\ T"
936 This finds the file that contains the specified tag. \s-2JOVE\s0 looks up
937 tags by default in the
938 .BQ tags
939 file in the current directory, as created
940 by the
941 .B UNIX
942 command
943 .IQ ctags(1) .
944 You can change
945 the default tag name by setting the
946 .IQ tag-file
947 variable to another
948 name. If you specify a numeric argument to this command, you will be
949 prompted for a tag file. This is a good way to specify another tag file
950 without changing the default.
951 .dc "find-tag-at-point" "Not Bound"
952 This finds the file that contains the tag that point is currently in.
953 See
954 .IQ find-tag .
955 .dc "first-non-blank" "ESC\ M"
956 This moves point (backwards or forwards) to the indent of the current line.
957 .dc "forward-character" "^F"
958 This moves point forward over a single character or line-separator.
959 Thus if point is at the end of
960 the line it moves to the beginning of the next one.
961 .dc "forward-list" "ESC\ ^N"
962 This moves point forward over a list, which is any text between properly
963 matching (\^...\^), [\^...\^] or {\^...\^}.
964 It first searches forward for a \*Q(\*U and then moves to the matching \*Q)\*U.
965 This is useful when you are trying to find unmatched parentheses in a program.
966 Arguments are accepted, and negative arguments search backwards.
967 See also
968 .IQ forward-s-expression .
969 .dc "forward-paragraph" "ESC\ ]"
970 This moves point forward to the end of the current or next paragraph.
971 Paragraphs are bounded by lines that match
972 .IQ paragraph-delimiter-pattern
973 (by default, those that are empty or look like troff or TeX commands).
974 A change in indentation may also signal a break
975 between paragraphs, except that \s-2JOVE\s0 allows the first line of a
976 paragraph to be indented differently from the other lines.
977 Arguments are accepted, and negative arguments search backwards.
978 .dc "forward-s-expression" "ESC\ ^F"
979 This moves point forward over an s-expression, that is over a Lisp atom or
980 a C identifier (depending on the major mode) ignoring punctuation and
981 whitespace; or, if the nearest succeeding significant character is one of
982 \*Q([{\*U, over a list as in
983 .IQ forward-list .
984 Arguments are accepted, and negative arguments search backwards.
985 .dc "forward-sentence" "ESC\ E"
986 This moves point forward to the end of the current or next sentence.
987 \s-2JOVE\s0 considers the end of a sentence to be the
988 characters \*Q.\*U, \*Q!\*U or
989 \*Q?\*U, followed possibly by \*Q'\*U, \*Q''\*U, or \*Q"\*U, followed by a
990 Return or whitespace.
991 Arguments are accepted, and negative arguments search backwards.
992 .dc "forward-word" "ESC\ F"
993 This moves point forward to the end of the current or next word.
994 .dc "fundamental-mode" "Not Bound"
995 This sets the major mode to Fundamental.
996 Fundamental mode is the mode of the Minibuf, and hence of anything typed in
997 the message line.
998 .dc "gather-numeric-argument" "^U"
999 This command is one of two ways to specify a numeric argument to a
1000 command. Typing this command once means, Do the next
1001 command 4 times. Typing it twice will do the next command 16 times, and
1002 so on. If at any point you type a number, then that number will be used
1003 instead of 4. For instance, ^U 3 5 means do the next command 35 times
1004 (assuming
1005 .IQ gather-numeric-argument
1006 is bound to ^U).
1007 .dc "goto-line" "ESC\ G"
1008 If a positive numeric argument is supplied, point moves to the
1009 beginning of that line. If the argument is negative, it indicates
1010 how many lines from the end of the buffer to move point to. If no
1011 argument is supplied one is prompted for.
1012 .dc "goto-window-with-buffer" "Not Bound"
1013 This command prompts for a buffer name and then selects that buffer. If
1014 the buffer is currently being displayed in one of the windows, that
1015 window is selected instead.
1016 .dc "grind-s-expr" "Not Bound"
1017 When point is positioned on a \*Q(\*U, this re-indents that LISP expression.
1018 .dc "grow-window" "^X\ ^\^"
1019 This makes the active window one line bigger. This only works when
1020 there is more than one window and provided there is room to change the
1021 size.
1022 See also
1023 .IQ shrink-window .
1024 .dc "handle-tab" "Tab"
1025 This handles indenting to the \*Qright\*U place in C and Lisp mode, and
1026 just inserts itself in Text mode.
1027 .dc "highlight-attribute" "(variable)"
1028 (IBM PC version only) This specifies how the attribute (color) of a
1029 character is to be changed when it is highlighted. Highlighting is indicated
1030 by exclusive oring this value with the normal attribute for the character.
1031 The default is 16.
1032 .dc "highlight-mark" "(variable)"
1033 When this is on, jove will highlight the mark if currently
1034 visible. The mark is highlighted with an underscore.
1035 .dc "i-search-forward" "Not Bound"
1036 Incremental search. Like search-forward except that instead of prompting
1037 for a string and searching for that string all at once, it accepts the string
1038 one character at a time. After each character you type as part of the search
1039 string, it searches for the entire string so far. When you like what it
1040 found, type Return to finish the search. You can take back a
1041 character with DEL and the search will back up to the position before
1042 that character was typed. ^G aborts the search.
1043 .dc "i-search-reverse" "Not Bound"
1044 Incremental search. Like search-reverse except that instead of prompting
1045 for a string and searching for that string all at once, it accepts the string
1046 one character at a time. After each character you type as part of the search
1047 string, it searches for the entire string so far. When you like what it
1048 found, type Return to finish the search. You can take back a
1049 character with DEL and the search will back up to the position before
1050 that character was typed. ^G aborts the search.
1051 .dc "i-shell-command" "Not Bound"
1052 This is like
1053 .IQ shell-command
1054 except that it launches an interactive process and so lets you continue with
1055 your editing while the command is running. This is really useful for long
1056 running commands with sporadic output.
1057 See also the variable
1058 .IQ wrap-process-lines .
1059 .dc "insert-file" "^X\ ^I"
1060 This inserts a specified file into the selected buffer at point. Point
1061 is positioned at the beginning of the inserted file.
1062 .dc "interrupt-character" "(variable)"
1063 This specifies what character should be used as the operating
1064 system's tty driver interrupt character. When this character is
1065 typed, the tty driver generates SIGINT signal. This will
1066 interrupt a non-interactive process. If no such process is
1067 running, \s-2JOVE'S\s0 will offer you the option of continuing, or
1068 crashing \s-2JOVE'S\s0 (trying to save your work). This is a crude and
1069 desperate way to stop \s-2JOVE'S\s0. Unfortunately there is no way to
1070 turn off the interrupt character. The default is ^]. See also
1071 .IQ abort-char .
1072 .dc "insert-variable" "Not Bound"
1073 This inserts the value of the specified variable
1074 at the current point in the current buffer.
1075 .dc "interrupt-process" "Proc: ^C\ ^C"
1076 This sends the signal SIGINT to the interactive process
1077 in the selected buffer. This only works if you are inside a buffer
1078 bound to an interactive process.
1079 .dc "iproc-env-export" "Not Bound"
1080 This takes an argument of the form VARNAME=VALUE and replaces or
1081 sets VARNAME to that VALUE in the list of environment variables that
1082 are passed to interactive shell commands i.e.
1083 .IQ shell
1084 and
1085 .IQ i-shell-command .
1086 .dc "iproc-env-show" "Not Bound"
1087 This shows (as temporary screen output or in a buffer, depending on the
1088 variable
1089 .IQ send-typeout-to-buffer )
1090 the environment that will be exported to interactive processes.
1091 .dc "iproc-env-unset" "Not Bound"
1092 This takes an argument that is the name of an environment variable and
1093 removes it from the list of environment variables that will be passed
1094 to interactive processes.
1095 .dc "jove-compiled-with" "(variable)"
1096 This is a special, read-only variable, containing the compiler, flags and
1097 options used to build Jove (on Unix-style machines)
1098 .dc "jove-features" "(variable)"
1099 This is a special, read-only variable, set with a colon-delimited list of
1100 all the optional capabilities compiled into \s-2JOVE\s0. The value will
1101 be something like
1102 .br
1103 .IQ :unix:abbr:bak:cmtfmt:fcomp:iproc:pty:lisp:proc:spell:rec:job:idchar:hl:tcap:ctype:
1104 .br
1105 .IQ unix
1106 specifies a variety of traditional UNIX/POSIX capabilities (case-sensitive
1107 filenames, a Unix-style filesystem), as opposed to
1108 .br
1109 .IQ msdos
1110 or
1111 .IQ win32
1112 which have case-insensitive filesystems, for example. The platform
1113 .IQ ibmpcdos
1114 indicates specialization for the IBM-PC platform, which in reality, is
1115 the only MS-DOS form remaining in existence (other non-IBM-PC platforms,
1116 like Heath/Zenith, DEC Rainbow, etc probably do not exist anymore,
1117 as is probably the case for the pre-OSX classic
1118 .IQ mac
1119 platform). Other tokens are
1120 .br
1121 .IQ abbr
1122 (abbrev-mode exists),
1123 .br
1124 .IQ bak
1125 (backup-files can be created),
1126 .br
1127 .IQ cmtfmt
1128 (format C comments),
1129 .br
1130 .IQ fcomp
1131 (filename completion),
1132 .br
1133 .IQ iproc
1134 (interactive shell processes),
1135 .br
1136 .IQ pipe
1137 (indicating that
1138 .IQ iproc
1139 is implemented using pipes and the
1140 .IQ portsrv
1141 helper program ), or
1142 .br
1143 .IQ pty
1144 (indicating that
1145 .IQ iproc
1146 is implemented using pseudo-terminals, available on any modern
1147 post-4.2BSD platform),
1148 .br
1149 .IQ lisp
1150 (lisp mode is available),
1151 .br
1152 .IQ proc
1153 (the ability to run non-interactive subshell processes with output
1154 to buffers, or switch entirely from \s-2JOVE\s0 to a child shell
1155 via
1156 .IQ push-shell
1157 and then return to \s-2JOVE\s0 when that child shell exits),
1158 .br
1159 .IQ spell
1160 (the ability to run a spell checker on the contents of a buffer,
1161 parse and modify the checker output and then step through
1162 any misspelled words in the original buffer with ^X^N and ^X^P)
1163 .br
1164 .IQ rec
1165 (periodically generate a recovery file so that one can restore unsaved changes
1166 from \s-2JOVE\s0 editors after a machine or program crash)
1167 .br
1168 .IQ job
1169 (BSD job control is supported, so one can suspend \s-2JOVE\s0
1170 with the pause-jove command and return to the shell that \s-2JOVE\s0
1171 was started from, and later resume \s-2JOVE\s0 using a
1172 shell command like
1173 .IQ fg ),
1174 .br
1175 .IQ jsmall
1176 (\s-2JOVE\s0 was built with smaller limits on the number of
1177 lines it can support, probably only 32000)
1178 .br
1179 .IQ idchar
1180 (\s-2JOVE\s0 will attempt to optimize screen display
1181 using insert/delete character modes and terminal control sequences),
1182 .IQ hl
1183 (enable highlight-mark capabiltiy to display a small underscore for the
1184 position of the mark,
1185 and enable the scroll-bar capability in the buffer mode line),
1186 .br
1187 .IQ jtc
1188 (uses builtin ANSI/VT1xx/XTERM driver rather than
1189 .IQ termcap/terminfo/curses ),
1190 .br
1191 .IQ tcap
1192 (termcap database code is enabled)
1193 .br
1194 .IQ tinfo
1195 (uses SystemV-style terminfo rather than BSD-style termcap calls),
1196 .br
1197 .IQ ctype
1198 (uses the system ctype character classification rather than \s-2JOVE\s0 builtin
1199 capability)
1200 .br
1201 .IQ iso88591
1202 (uses builtin \s-2JOVE\s0 tables for ISO-8859-1 character classification
1203 rather than the system ctype capability).
1204 .dc "jove-linked-with" "(variable)"
1205 This is a special, read-only variable, containing the linker, flags and
1206 libraries used to build Jove (on Unix-style machines)
1207 .dc "kill-next-word" "ESC\ D"
1208 This kills the text from point to the end of the current or next word.
1209 .IQ
1210 The killed text is sent to the kill ring.
1211 .dc "kill-previous-word" "ESC\ DEL"
1212 This kills the text from point to the beginning of the current or
1213 previous word.
1214 The killed text is sent to the kill ring.
1215 .dc "kill-process" "Not Bound"
1216 This command prompts for a buffer name or buffer number (just as
1217 .IQ select-buffer
1218 does) and then sends the process in that buffer the
1219 signal SIGKILL.
1220 .dc "kill-region" "^W"
1221 This deletes the text in the region and saves it on the kill ring.
1222 Commands that delete text but save it on the kill ring all have the
1223 word \*Qkill\*U in their names. Use the
1224 .IQ yank
1225 command to get back the most recent
1226 kill.
1227 .dc "kill-s-expression" "ESC\ ^K"
1228 This kills the text from point to the end of the current or next
1229 s-expression.
1230 The killed text is sent to the kill ring.
1231 .dc "kill-some-buffers" "Not Bound"
1232 This goes through all the existing buffers and asks whether or not to delete
1233 each one. If you decide to delete a buffer, and it turns out that the buffer
1234 is modified, \s-2JOVE\s0 will offer to save it first. This is useful for
1235 when \s-2JOVE\s0 runs out of memory to store lines (this only happens on
1236 PDP-11's) and you have lots of buffers that you are no longer using.
1237 See also the
1238 .IQ delete-buffer
1239 command.
1240 .dc "kill-to-beginning-of-sentence" "^X\ DEL"
1241 This kills from point to the beginning of the current or previous
1242 sentence. If a
1243 negative numeric argument is supplied it kills from point to the
1244 end of the current or next sentence.
1245 The killed text is sent to the kill ring.
1246 .dc "kill-to-end-of-line" "^K"
1247 This kills from point to the end of the current line. When point is
1248 at the end of the line (discounting any white space) the line-separator
1249 is also deleted and the next line
1250 is joined with current one. If a numeric argument is supplied that
1251 many lines are killed; if the argument is negative that many lines
1252 before point are killed; if the argument is zero the text from point
1253 to the beginning of the line is killed.
1254 The killed text is sent to the kill ring.
1255 .dc "kill-to-end-of-sentence" "ESC\ K"
1256 This kills from point to the end of the current or next sentence. If a
1257 negative numeric argument is supplied it kills from point to the
1258 beginning of the current or previous sentence.
1259 The killed text is sent to the kill ring.
1260 .dc "lc-ctype" "(variable)"
1261 This string variable determines how non-ASCII characters are displayed, and
1262 which characters are to be considered as upper-case, lower-case, printable,
1263 etc. The default is the implementation-defined native environment; under
1264 POSIX, it is determined by whichever of the environment variables
1265 LC_ALL, LC_CTYPE or LANG is first found to be set, and is otherwise "C".
1266 Some useful values of
1267 .IQ lc-ctype
1268 might be:
1269 .DS
1270 .ta \w'"iso_8859_111" 'u
1271 "" Default: the native environment.
1272 "C" Strict ASCII. All other characters greater than \e\^177
1273 rendered in octal.
1274 "iso_8859_1" Latin-1 alphabet.
1275 .DE
1276 .dc "left-margin" "(variable)"
1277 This is how far lines should be indented when Auto Indent mode is on,
1278 or when the
1279 .IQ newline-and-indent
1280 command is run (usually by typing
1281 Linefeed). It is also used by
1282 .IQ fill-paragraph
1283 and Auto Fill mode.
1284 If the value is zero (the default) then the left margin is determined
1285 from the surrounding lines.
1286 .dc "left-margin-here" "Not Bound"
1287 This sets the
1288 .IQ left-margin
1289 variable to the current position of
1290 point. This is an easy way to say, \*QMake the left margin begin here,\*U
1291 without having to count the number of spaces over it actually is.
1292 .dc "lib-dir-pathname" "(variable)"
1293 This tells JOVE where to find the machine-dependent helper
1294 programs: the
1295 .IQ recover
1296 program, run when
1297 .IQ "jove -r"
1298 is run after a crash to try to recover unsaved files,
1299 and on some older machines without pseudo-terminal support, the
1300 .IQ portsrv
1301 program, which handles multiplexed communication with the
1302 keyboard and interactive shells (if JOVE is compiled with SUBSHELL
1303 and PIPEPROCS configured)
1304 .dc "lisp-mode" "Not Bound"
1305 This turns on the Lisp major mode. In Lisp mode, the characters Tab
1306 and \*Q)\*U are treated specially, similar to the way they are treated in C
1307 mode. Also, Auto Indent mode is affected, and handled specially.
1308 See also the
1309 .IQ c-mode
1310 command.
1311 .dc "list-buffers" "^X\ ^B"
1312 This types out a list containing various information about each buffer.
1313 The list looks like this:
1314 .DS
1315 .ta \w'NO111'u +\w'Lines1'u +\w'Scratch111'u +\w'\(**1'u +\w'commands.doc111'u
1316 \ (\(** means the buffer needs saving)
1317 \ NO Lines Type Name File
1318 \ -- ----- ---- ---- ----
1319 \ 1 1 File Main [No file]
1320 \ 2 1 Scratch \(** Minibuf [No file]
1321 \ 3 519 File \(** commands.doc commands.doc
1322 .DE
1323 The first column lists the buffer's number. When \s-2JOVE\s0 prompts for a
1324 buffer name you can either type in the full name, or you can simply
1325 type the buffer's number. The second column is the number of lines in
1326 the buffer. The third says what type of buffer. There are four
1327 types: File, Scratch, Process and I-Process. \*QFile\*U is simply a
1328 buffer that holds a file; \*QScratch\*U is for buffers that \s-2JOVE\s0 uses
1329 internally; \*QProcess\*U is one that holds the output from a
1330 .B UNIX
1331 command; \*QI-Process\*U is one that has an interactive process attached to
1332 it. The next column contains the name of the buffer. And the last
1333 column is the name of the file that's attached to the buffer. In this
1334 case, both Minibuf and commands.doc have been changed but not yet
1335 saved. In fact Minibuf won't be saved since it's a Scratch buffer.
1336 .dc "list-processes" "Not Bound"
1337 This makes a list somewhat like \*Qlist-buffers\*U does, except its
1338 list consists of the current interactive processes. The list
1339 looks like this:
1340 .DS
1341 .ta \w'shell-111111111111'u +\w'Running1111111111'u +\w'1851211111'u
1342 \ Buffer Status Pid Command
1343 \ ------ ------ --- -------
1344 \ \(**shell\(** Running 18415 shell
1345 \ fgrep Done 18512 fgrep -n Buffer \(**.c
1346 .DE
1347 The first column has the name of the buffer to which the process is
1348 attached. The second has the status of the process; if a process has
1349 exited normally the status is \*QDone\*U as in fgrep; if the process
1350 exited with an error the status is \*QExit N\*U where N is the value of
1351 the exit code; if the process was killed by some signal the status is
1352 the name of the signal that was used; otherwise the process is
1353 running. The last column is the name of the command that is being run.
1354 .dc "local-bind-keymap-to-key" "Not Bound"
1355 This is like
1356 .IQ local-bind-to-key
1357 except that you use it to attach a key sequence to a named keymap.
1358 The only reasonable use is to bind some extra key to
1359 .IQ ESC-map
1360 for keyboards that make typing ESC painful.
1361 .dc "local-bind-macro-to-key" "Not Bound"
1362 This is like
1363 .IQ local-bind-to-key
1364 except you use it to attach a key sequence to a named macro.
1365 .dc "local-bind-to-key" "Not Bound"
1366 This is like
1367 .IQ bind-to-key ,
1368 except that the binding is only enabled when the selected buffer is
1369 the buffer that was current when the command was executed. In other
1370 words, the binding only applies to the selected buffer.
1371 .dc "macify" "(variable)"
1372 (Mac version only)
1373 When this variable is on, \s-2JOVE\s0 will use the standard Macintosh
1374 file-selector dialog in place of the traditional \s-2JOVE\s0 Minibuffer.
1375 .dc "mail-check-frequency" "(variable)"
1376 This is how often (in seconds) \s-2JOVE\s0 should check your mailbox for
1377 incoming mail. If you set this to zero \s-2JOVE\s0 won't check for new
1378 mail. See also the
1379 .IQ mode-line
1380 and
1381 .IQ mailbox
1382 variables.
1383 The default is 60.
1384 .dc "mailbox" "(variable)"
1385 Set this to the full pathname of your mailbox. \s-2JOVE\s0 will look here to
1386 decide whether or not you have any unread mail. This defaults to
1387 .BQ /usr/spool/mail/$USER ,
1388 where \*Q$USER\*U is set to your login name.
1389 .dc "make-backup-files" "(variable)"
1390 If this variable is set, then whenever \s-2JOVE\s0 writes out a file, it will
1391 move the previous version of the file (if there was one) to \*Q#filename~\*U.
1392 This is often convenient if you save a file by accident. The default
1393 value of this variable is
1394 .IQ off .
1395 .dc "make-buffer-unmodified" "ESC\ ~\^"
1396 This makes \s-2JOVE\s0 think the selected buffer hasn't been changed even if
1397 it has. Use this when you accidentally change the buffer but don't
1398 want it considered changed. Watch the mode line to see the \(** disappear
1399 when you use this command.
1400 .dc "make-macro-interactive" "ESC\ I"
1401 This command is meaningful only while you are defining a keyboard macro,
1402 and when you are expecting input in the message line.
1403 Ordinarily, when a command in a macro
1404 definition requires a trailing text argument (file name, search string,
1405 etc.), the argument you supply becomes part of the macro definition. If
1406 you want to be able to supply a different argument each time the macro is
1407 used, then while you are defining it, you should give the
1408 .IQ make-macro-interactive
1409 command just before typing the argument which will
1410 be used during the definition process. Note: you must bind this command
1411 to a key in order to use it; you can't say \*QESC\ X make-macro-interactive\*U.
1412 .dc "mark-threshold" "(variable)"
1413 This variable contains the number of lines point may move by before
1414 the mark is set. If, in a search or some other command that may move point,
1415 point moves by more
1416 than this many lines, the mark is set so that you may return easily.
1417 The default value of this variable is 22 (one screenful, on most
1418 terminals).
1419 See also the commands
1420 .IQ search-forward ,
1421 .IQ search-reverse ,
1422 .IQ beginning-of-file
1423 and
1424 .IQ end-of-file .
1425 .dc "match-regular-expressions" "(variable)"
1426 When set, \s-2JOVE\s0 will match regular expressions in search patterns.
1427 This makes special the characters ., \(**, [ and ].
1428 See the \s-2JOVE\s0 Manual for a full discussion of regular-expressions.
1429 .dc "meta-key" "(variable)"
1430 You should set this variable to
1431 .IQ on
1432 if your terminal has a real Meta key
1433 which forces the 8th bit of each character.
1434 If your terminal has such a key, then a key sequence like ESC\ Y can be
1435 entered by holding down Meta and typing Y.
1436 On the IBM PC, this variable affects how ALT is interpreted.
1437 On the Macintosh, it affects how Option is interpreted.
1438 NOTE: In some older
1439 .B UNIX
1440 systems, \s-2JOVE\s0 must switch the tty to
1441 raw mode to accept the 8-bit characters generated by a meta key.
1442 Unfortunately, the
1443 .IQ interrupt-character
1444 does not generate an interrupt in raw mode.
1445 .dc "mode-line" "(variable)"
1446 The format of the mode line can be determined by setting this variable.
1447 The items in the line are specified using a format similar to that used by
1448 .IQ printf(3) ,
1449 with the special things being marked as \*Q%x\*U. Digits may be used
1450 between the '%' and the 'x' to mean repeat that many times.
1451 \&'x' may be:
1452 .DS I
1453 .ta .5i 1i 1.5i
1454 C checks for new mail, and displays \*Q[New mail]\*U if there
1455 is any (see also the \c
1456 .IQ mail-check-frequency " \c"
1457 and \c
1458 .IQ mailbox " \c"
1459 variables)
1460 F the current file name, with leading path stripped
1461 M the current list of major and minor modes
1462 b the selected buffer name
1463 c the fill character (-)
1464 d the current directory
1465 e extra space in mode line is distributed evenly
1466 among the places %e is used (used for justifying,
1467 separating, or centering parts of the mode line)
1468 f the current file name
1469 ixy x, when the buffer's file has been changed behind JOVE's back,
1470 y, when not
1471 mxy x, when the buffer is modified or y, when not
1472 n the selected buffer number
1473 p interactive process status for process windows
1474 s space, but only if previous character is not a space
1475 t the current time (updated automatically)
1476 w a '>' for windows which are scrolled left
1477 [ ] the square brackets printed when in a recursive edit
1478 ( ) items enclosed in %( ... %) will only be printed on
1479 the bottom mode line, rather than copied when the
1480 window is split
1481 .DE
1482 In addition, any other character is simply copied into the mode line.
1483 Characters may be escaped with a backslash. To get a feel for all
1484 this, try typing \*QESC\ X print mode-line\*U and compare the result with
1485 your current mode line.
1486 .dc "mode-line-attribute" "(variable)"
1487 (IBM PC version only) This specifies the screen attribute (color) for
1488 characters in the mode line. The default is 112 (black on white).
1489 .dc "mode-line-should-standout" "(variable)"
1490 If set, the mode line will be printed in reverse video, if your
1491 terminal supports it. The default for this variable is
1492 .IQ on .
1493 .dc "name-kbd-macro" "Not Bound"
1494 This copies the keyboard macro and gives it a name freeing up the
1495 keyboard macro so you can define some more. Keyboard macros with
1496 their own names can be bound to keys just like built in commands
1497 can. See the
1498 .IQ define-macro ,
1499 .IQ source
1500 and
1501 .IQ write-macros-to-file
1502 commands.
1503 .dc "newline" "Return"
1504 This divides the current line at point moving all the text to the
1505 right of point down onto the newly created line. Point moves down to
1506 the beginning of the new line. In Auto Indent mode, the new line will
1507 be indented to match the old line.
1508 .dc "newline-and-backup" "^O"
1509 This divides the current line at point moving all the text to the
1510 right of point down onto the newly created line. The difference
1511 between this and
1512 .IQ newline
1513 is that point does not move down to the beginning of the new line.
1514 .dc "newline-and-indent" "Linefeed"
1515 This behaves in any mode the same way as
1516 .IQ newline
1517 does in Auto Indent mode.
1518 .dc "next-error" "^X\ ^N"
1519 This moves to the next error in the list of errors that were parsed
1520 with
1521 .IQ parse-errors .
1522 In one window the list of errors is shown with the current one always at
1523 the top. If the file that contains the error is not already in a buffer, it
1524 is read in. Its buffer is displayed in another window and point
1525 is positioned in this window on the line where the error occurred.
1526 .dc "next-line" "^N"
1527 This moves point down to the corresponding position on the next line (or the
1528 end of that line if it does not extend so far).
1529 .dc "next-page" "^V"
1530 This displays the next page of the selected buffer by taking the bottom line
1531 of the window and redrawing the window with it at the top. If there isn't
1532 another page in the buffer \s-2JOVE\s0 rings the bell. If a numeric argument
1533 of only \- (with no digits) is supplied, the previous page
1534 is displayed. Otherwise, if a numeric argument
1535 is supplied the screen is scrolled up that many lines, exactly as in the
1536 .IQ scroll-up
1537 command; if the argument
1538 is negative the screen is scrolled down.
1539 .dc "next-window" "^X\ N"
1540 This moves into the next window. Windows live in a circular list so
1541 when you're in the bottom window and you try to move to the next one
1542 you are moved to the top window. It is an error to use this command
1543 with only one window.
1544 .dc "number-lines-in-window" "Not Bound"
1545 This displays the line numbers for each line in the buffer being
1546 displayed. The number isn't actually part of the text; it's just
1547 printed before the actual buffer line is. To turn this off you run
1548 the command again; it toggles.
1549 .dc "one-key-confirmation" "(variable)"
1550 If this variable is set, a single keystroke of y or n is expected
1551 in answer to yes/no questions.
1552 Normally, a yes/no question must be answered with any non-empty
1553 prefix of yes or no, followed by a Return
1554 .dc "over-write-mode" "Not Bound"
1555 This turns Over Write minor mode on in the selected buffer. Without
1556 a numeric argument, the command toggles the mode; with a zero
1557 argument, the mode is turned off; with a non-zero argument, the
1558 mode is turned on. When on, this mode changes the way the
1559 self-inserting characters work. Instead of inserting themselves and
1560 pushing the rest of the line over to the right, they replace or
1561 over-write the existing character. Also, DEL replaces the character
1562 before point with a space instead of deleting it. When Over Write
1563 mode is on \*QOvWrt\*U is displayed in the mode line.
1564 .dc "page-next-window" "ESC\ ^V"
1565 This displays the next page in the next window.
1566 It switches to the next window, performs a
1567 .IQ next-page
1568 command (with any numeric argument), and switches back to the original window.
1569 Note that an argument of just \*Q\-\*U will thus display the previous page.
1570 .dc "paren-flash" "\^) } ]\^"
1571 This command causes the characters bound to it to be inserted, and then to
1572 partake in C mode curly brace indentation, Lisp mode parenthesis
1573 indentation, and the Show Match mode paren/curly-brace/square-bracket
1574 flashing.
1575 .dc "paragraph-delimiter-pattern" "(variable)"
1576 When \s-2JOVE\s0 is searching for a paragraph boundary, if this
1577 pattern (a regular expression) matches the start of a line, that
1578 line is treated as a paragraph delimiter. The default pattern
1579 recognizes blank lines, troff control lines, and lines starting with
1580 a TeX control sequence.
1581
1582 There is a special provision for TeX: if a line is matched by the
1583 pattern, and the match is of exactly an initial \e, that line is
1584 only treated as a delimiter if the next line also starts with \e.
1585 .dc "paren-flash-delay" "(variable)"
1586 How long, in tenths of a second, \s-2JOVE\s0 should pause on a matching
1587 parenthesis in Show Match mode. The default is 5.
1588 .dc "parse-errors" "Not Bound"
1589 This takes the list of C compilation errors (or the output from another
1590 program in an acceptable format) in the selected buffer and parses them for
1591 use with the
1592 .IQ next-error ,
1593 .IQ previous-error
1594 and
1595 .IQ current-error
1596 commands.
1597 This is a very useful tool and helps with compiling C programs or, when used
1598 in conjunction with the
1599 .B UNIX
1600 .IQ grep
1601 command, with making changes to a bunch of files.
1602 \s-2JOVE\s0 finds each file that has an error and remembers each line that
1603 contains an error. It doesn't matter if later you insert or delete
1604 some lines in the buffers containing errors; \s-2JOVE\s0 remembers where
1605 they are regardless.
1606 .IQ current-error
1607 is automatically executed after one of the parse commands, so you end up
1608 at the first error. The variable
1609 .IQ error-format-string
1610 specifies, by means of regular-expressions, the format of errors to be
1611 recognized. Its default value can handle messages from
1612 .IQ cc ,
1613 .IQ cpp ,
1614 .IQ lint
1615 and
1616 .IQ "grep\ \-n" .
1617 .dc "parse-spelling-errors-in-buffer" "Not Bound"
1618 This parses a list of words in the selected buffer and looks them up in
1619 another buffer that you specify.
1620 It is invoked automatically by the
1621 .IQ spell-buffer
1622 command.
1623 .dc "pause-jove" "ESC\ S"
1624 This stops \s-2JOVE\s0 and returns control to the parent shell. This
1625 only works on systems that have the
1626 job control facility. To return to \s-2JOVE\s0 you type \*Qfg\*U to the shell.
1627 .dc "pop-mark" "Not Bound"
1628 \s-2JOVE\s0 remembers the last eight marks and you use
1629 .IQ pop-mark
1630 to go
1631 backward through the ring of marks. If you execute
1632 .IQ pop-mark
1633 enough
1634 times you will eventually get back to where you started.
1635 This command is also executed when you run
1636 .IQ set-mark
1637 with a numeric argument.
1638 .dc "popd" "Not Bound"
1639 This pops one entry off the directory stack. Entries are pushed with
1640 the
1641 .IQ pushd
1642 or
1643 .IQ pushlibd
1644 commands. The names were stolen from the C-shell and the
1645 behavior is the same.
1646 .dc "previous-error" "^X\ ^P"
1647 This is the same as
1648 .IQ next-error
1649 except it goes to the previous error.
1650 See
1651 .IQ next-error
1652 for documentation.
1653 .dc "previous-line" "^P"
1654 This moves point up to the corresponding position on the previous line (or the
1655 end of that line if it does not extend so far).
1656 .dc "previous-page" "ESC\ V"
1657 This displays the previous page of the selected buffer by taking the top
1658 line and redrawing the window with it at the bottom. If a numeric
1659 argument of only \- (with no digits) is supplied, the next page
1660 is displayed. Otherwise, if a numeric
1661 argument is supplied the screen is scrolled down that many lines, exactly as
1662 in the
1663 .IQ scroll-down
1664 command; if
1665 the argument is negative the screen is scrolled up.
1666 .dc "previous-window" "^X\ P or ^X\ O"
1667 This moves into the previous window. Windows live in a circular list so
1668 when you're in the top window and you try to move to the previous one
1669 you are moved to the bottom window. It is an error to use this command
1670 with only one window.
1671 .dc "print" "Not Bound"
1672 This displays the value of a \s-2JOVE\s0 variable in the message line.
1673 .dc "proc-env-export" "Not Bound"
1674 This takes an argument of the form VARNAME=VALUE and replaces or
1675 sets VARNAME to that VALUE in the list of environment variables that
1676 are passed to subshell commands i.e.
1677 .IQ shell-command ,
1678 .IQ compile-it ,
1679 .IQ spell-buffer ,
1680 etc.
1681 .dc "proc-env-show" "Not Bound"
1682 This shows (as temporary screen output or in a buffer, depending on the
1683 variable
1684 .IQ send-typeout-to-buffer )
1685 the environment that will be exported to subshell commands.
1686 .dc "proc-env-unset" "Not Bound"
1687 This takes an argument that is the name of an environment variable and
1688 removes it from the list of environment variables that will be passed
1689 to subshell commands.
1690 .dc "process-bind-keymap-to-key" "Not Bound"
1691 This is like
1692 .IQ process-bind-to-key
1693 except that you use it to attach a key sequence to named keymap.
1694 The only reasonable use is to bind some extra key to
1695 .IQ ESC-map
1696 for keyboards that make typing ESC\ painful.
1697 .dc "process-bind-macro-to-key" "Not Bound"
1698 This is like
1699 .IQ process-bind-to-key
1700 except you use it to attach a key sequence to a named macro.
1701 .dc "process-bind-to-key" "Not Bound"
1702 This command is identical to
1703 .IQ bind-to-key ,
1704 except that it only affects
1705 your bindings when you are in a buffer attached to an interactive process.
1706 When you enter the process buffer, any keys bound with this command will
1707 automatically take their new values. When you switch to a non-process
1708 buffer, the old bindings for those keys will be restored. For example,
1709 you might want to execute
1710 .DS I
1711 process-bind-to-key stop-process ^C\ ^Z
1712 process-bind-to-key interrupt-process ^C\ ^C
1713 .DE
1714 Then, when you start up an interactive process and switch into that
1715 buffer, ^C\ ^Z will execute
1716 .IQ stop-process
1717 and ^C\ ^C will execute
1718 .IQ interrupt-process .
1719 Bindings effective only in process windows are shown with a \*QProc:\*U
1720 prefix in this manual and by the
1721 .IQ apropos
1722 and
1723 .IQ describe-bindings
1724 commands.
1725 .dc "process-newline" "Proc: Return"
1726 This command is normally bound to Return as if by a
1727 .IQ process-bind-to-key
1728 so that it will only be bound in a process window.
1729 \s-2JOVE\s0 does two different things depending on where you are when you
1730 hit Return. When you're in the last line of the interactive process buffer,
1731 point moves to the end of the line, the line is terminated, and the line is
1732 made available as input to the process. When point is positioned in some
1733 other line, that line is copied to the end of the buffer (with the prompt
1734 stripped) and point is moved there with it, so you can then edit that line
1735 before sending it to the process. This command must be bound to the key you
1736 usually use to enter shell commands (Return), or else you won't be able to
1737 enter any. See the variable
1738 .IQ process-prompt .
1739 .dc "process-prompt" (variable)
1740 What a prompt looks like from the
1741 .IQ shell
1742 and
1743 .IQ i-shell-command
1744 processes. The default is \*Q% \*U, the default C-shell prompt. This is
1745 actually a regular expression search string. So you can set it to be
1746 more than one thing at once using the \e| operator. For instance, for
1747 LISP hackers, the prompt can be
1748 .DS
1749 "% \e|-> \e|<[0-9]>: ".
1750 .DE
1751 .dc "process-send-data-no-return" "Not Bound"
1752 This is like
1753 .IQ process-newline
1754 except it sends everything to the process without the newline. Normally,
1755 when you type return in a process buffer it sends everything you typed
1756 including the Return. This command just provides a way to send data to
1757 the process without having to send a newline as well.
1758 .dc "push-shell" "Not Bound"
1759 This spawns a child shell and relinquishes control to it.
1760 Within this shell, $1 can be used to refer to the filename (if any)
1761 of the selected buffer.
1762 This works on any version of
1763 .B UNIX ,
1764 but this isn't as good as
1765 .IQ pause-jove
1766 because
1767 it takes time to start up the new shell and you get a brand new
1768 environment every time. To return to \s-2JOVE\s0, simply exit the shell.
1769 .dc "pushd" "Not Bound"
1770 This pushes a directory onto the directory stack and cd's into it. It
1771 asks for the directory name but if you don't specify one it switches
1772 the top two entries on the stack. It purposely behaves the same as
1773 C-shell's
1774 .IQ pushd .
1775 .dc "pushlibd" "Not Bound"
1776 Performs same function as
1777 .IQ pushd
1778 except that it pushes the Jove
1779 sharable library directory. This directory holds the system-wide
1780 .BQ jove.rc
1781 and the text used by the
1782 .IQ describe-command
1783 and
1784 .IQ describe-variable
1785 commands. It is mainly intended for use with the
1786 .BQ jove.rc
1787 file.
1788 .dc "pwd" "Not Bound"
1789 This prints the pathname of the working directory, as in the
1790 .B UNIX
1791 .IQ pwd
1792 command.
1793 .dc "query-replace-string" "ESC\ Q"
1794 This replaces strings matching a specified regular-expression
1795 with a specified replacement string.
1796 When a match is found, point is moved to it
1797 and then \s-2JOVE\s0 asks what to do. The options are:
1798 .DS I
1799 .ta \w'DEL, BS, or N or n11'u
1800 Space or Y or y to replace this match and go on to the next one.
1801 Period to replace this match and then stop.
1802 DEL, BS, or N or n to skip this match and go on to the next one.
1803 ^R or R or r to enter a recursive edit. This lets you temporarily
1804 suspend the replace, do some editing, and then return
1805 to continue where you left off. To continue with the
1806 \c
1807 .IQ query-replace-string ,\c
1808 use the \c
1809 .IQ exit-jove " command."
1810 ^W to delete the match and then enter a recursive edit.
1811 ^U or U or u to undo all changes to the last modified line and
1812 continue the search from the start of that line.
1813 ! or P or p to go ahead and replace the remaining matches without
1814 asking, as in \c
1815 .IQ replace-string .
1816 Return or Q or q to stop the \c
1817 .IQ query-replace-string .
1818 ^L to redraw the screen
1819 .DE
1820 It is often useful to include a piece of the matched string in the
1821 replacement, especially if the piece was not matched by literal text.
1822 To select which part of the matched string is to be used, the
1823 corresponding part of the pattern is bracketed with \e\^( and \e).
1824 More than one set of brackets may be used, as long as they are
1825 properly nested. The matching substring is selected in the
1826 replacement string using \e followed by a digit: \e1 for the first,
1827 \e\^2 for the second, and so on. Conveniently, \e\^0 always stands for
1828 the complete matched string, as if the whole regular expression were
1829 bracketed. For example, the following command will reverse pairs of
1830 comma-separated numbers:
1831 .ID
1832 : query-replace-string \e\^([0-9]\(**\^\e),\e\^([0-9]\(**\^\e) with \e\^2,\e1
1833 .DE
1834 The search for a match starts at point and goes to the end of the
1835 buffer, so to replace in the entire buffer you must first go to the
1836 beginning. Each subsequent search starts at the position after the
1837 previous match; if the previous match was an empty string, the search
1838 is first advanced one character to prevent unbounded repetition.
1839 .dc "quit-process" "Proc: ^C\ ^\^\e\^"
1840 Send the signal SIGQUIT to the interactive process in the selected buffer.
1841 This is equivalent to sending the \*Qquit\*U character (which most people
1842 have bound to ^\^\e) to the process. This only works if you are in a buffer
1843 bound to an interactive process.
1844 .dc "quoted-insert" "^Q or ^^\^"
1845 This lets you insert characters that normally would be executed as
1846 other \s-2JOVE\s0 commands. For example,
1847 to insert \*Q^F\*U you type \*Q^Q ^F\*U
1848 (assuming
1849 .IQ quoted-insert
1850 is bound to ^Q).
1851 NUL cannot be represented in the buffer, so
1852 .IQ quoted-insert
1853 will insert \*Q^@\*U in its stead.
1854 On the IBM PC under DOS, non-ASCII keystrokes are seen by \s-2JOVE\s0
1855 as a hex FF character followed by another character;
1856 .IQ quoted-insert
1857 will quote both characters.
1858 .dc "read-only-mode" "Not Bound"
1859 This turns on or off the Read-only minor mode. Without a numeric
1860 argument, the command toggles the mode; with a zero argument, the
1861 mode is turned off; with a non-zero argument, the mode is turned
1862 on. When a buffer is in Read-only mode, any attempt to modify the
1863 buffer will fail. When a file is found, and it's not got write
1864 permission, \s-2JOVE\s0 automatically puts the buffer in read-only mode.
1865 This is very helpful when you are in environments which use source
1866 control programs like RCS and SCCS. It prevents accidents like
1867 making a bunch of changes and only THEN discovering that you haven't
1868 checked the file out for making changes.
1869 .dc "read-word-abbrev-file" "Not Bound"
1870 This reads a specified file that contains a bunch of abbreviation
1871 definitions, and makes those abbreviations available.
1872 See the
1873 .IQ word-abbrev-mode
1874 command.
1875 .dc "recursive-edit" "Not Bound"
1876 This enters a recursive editing level. This isn't really very
1877 useful. I don't know why it's available for public use. I think I'll
1878 delete it some day.
1879 .dc "redraw-display" "^L"
1880 This vertically centers the line containing point within the window. If that
1881 line is already in place, the screen is first cleared and then redrawn.
1882 If a numeric argument is supplied, the line is positioned at that
1883 offset from the top of the window. For example, \*QESC\ 0 ^L\*U positions
1884 the line containing point at the top of the window
1885 (assuming
1886 .IQ redraw-display
1887 is bound to ^L).
1888 .dc "rename-buffer" "Not Bound"
1889 This lets you rename the selected buffer.
1890 .dc "replace-in-region" "Not Bound"
1891 This is the same as
1892 .IQ replace-string
1893 except that it is restricted
1894 to occurrences between point and the mark.
1895 .dc "replace-string" "ESC\ R"
1896 This replaces all occurrences of a specified string with a specified
1897 replacement string. This is just like
1898 .IQ query-replace-string
1899 except that
1900 it replaces without asking.
1901 .dc "right-margin" "(variable)"
1902 Where the right margin is for Auto Fill mode and the
1903 .IQ fill-paragraph
1904 and
1905 .IQ fill-region
1906 commands. The default is 78.
1907 .dc "right-margin-here" "Not Bound"
1908 This sets the
1909 .IQ right-margin
1910 variable to the current position of
1911 point. This is an easy way to say, \*QMake the right margin begin here,\*U
1912 without having to count the number of spaces over it actually is.
1913 .dc "save-file" "^X\ ^S or ^X\ S or ^X\ \e\^"
1914 This saves the selected buffer to the associated file. This makes your
1915 changes permanent so you should be sure you really want to do it. If the
1916 buffer has not been modified
1917 .IQ save-file
1918 refuses to do the save. If
1919 you really do want to write the file you must use
1920 .IQ write-file .
1921 .dc "save-on-exit" "(variable)"
1922 If this is
1923 .IQ on
1924 when \s-2JOVE\s0 is about to exit, it will ask, for each modified buffer,
1925 whether you wish it to be saved.
1926 See
1927 .IQ write-modified-files .
1928 .dc "scroll-all-lines" "(variable)"
1929 When this is
1930 .IQ off ,
1931 (the default) horizontal scrolling will only affect the line
1932 containing point.
1933 When it is
1934 .IQ on ,
1935 horizontal scrolling will affect the whole window. See also the
1936 .IQ scroll-width
1937 variable.
1938 .dc "scroll-bar" "(variable)"
1939 When this is turned
1940 .IQ on ,
1941 a section of the mode line at the foot of each window is
1942 left in not-reverse-video, to show the position of the window relative to
1943 the whole of the file represented by that buffer (however, if the whole of
1944 the buffer is within the window, the whole mode line remains inverted).
1945 .dc "scroll-down" "ESC\ Z"
1946 This scrolls the screen one line down. If the line containing point
1947 moves past the bottom of the window, point is moved up to the top of
1948 the window. If a numeric argument is supplied that many lines are
1949 scrolled; if the argument is negative the screen is scrolled up
1950 instead.
1951 See the
1952 .IQ previous-page
1953 command.
1954 .dc "scroll-left" "Not Bound"
1955 This scrolls the text in the active window to the
1956 left. If a numeric argument is specified then the text is scrolled that
1957 number of columns. Otherwise, the text is scrolled by
1958 the number of columns specified by the variable
1959 .IQ scroll-width .
1960 If the variable
1961 .IQ scroll-all-lines
1962 is ON then
1963 .IQ scroll-left
1964 may actually do nothing if the scrolling would cause point not to be
1965 visible. A negative argument scrolls right. If the
1966 .IQ mode-line
1967 variable
1968 is suitably set, an indication that the text is scrolled will be given in
1969 the mode line.
1970 .dc "scroll-right" "Not Bound"
1971 This scrolls the text in the active window to the
1972 right. If a numeric argument is specified then the text is scrolled that
1973 number of columns. Otherwise, the text is scrolled by
1974 the number of columns specified by the variable
1975 .IQ scroll-width .
1976 If the variable
1977 .IQ scroll-all-lines
1978 is ON then
1979 .IQ scroll-right
1980 may actually do nothing if the scrolling would cause point not to be
1981 visible. A negative argument scrolls left.
1982 .dc "scroll-step" "(variable)"
1983 How many lines should be scrolled if the
1984 .IQ previous-line
1985 or
1986 .IQ next-line
1987 commands move you off the top or bottom of the screen. You may wish to
1988 decrease this variable if you are on a slow terminal. The default value
1989 is 0, which means to center the current line in the window. If the value
1990 is negative, the behavior is slightly different. If you move off the top
1991 of the window, and
1992 .IQ scroll-step
1993 is, say, \-5 then the new line will be displayed 5 lines from the bottom
1994 of the window. If you move off the bottom of the window, the new line
1995 will be positioned 5 lines from the top of the window.
1996 .dc "scroll-up" "^Z"
1997 This scrolls the screen one line up. If the line containing point
1998 moves past the top of the window, point is moved down to the top of
1999 the window. If a numeric argument is supplied that many lines are
2000 scrolled; if the argument is negative the screen is scrolled down
2001 instead.
2002 See also the
2003 .IQ next-page
2004 command.
2005 .dc "scroll-width" "(variable)"
2006 Just as a buffer may be too long to be completely displayed in a
2007 window, a line may be too wide. \s-2JOVE\s0 handles wide lines
2008 through horizontal scrolling, displaying only a portion of the
2009 line. This variable affects horizontal scrolling. If point is
2010 outside the displayed portion of its line, but is within the
2011 specified number of columns beyond either side, the line is scrolled
2012 that much. Otherwise, the line will be scrolled to center point.
2013 The default value is 10. If the variable is 0, centering will
2014 always be used. See also the
2015 .IQ scroll-all-lines
2016 variable.
2017 .dc "search-exit-char" "(variable)"
2018 Set this to the character you want to use to exit incremental search. The
2019 default is Newline, which makes
2020 .IQ i-search
2021 commands compatible with
2022 normal string search.
2023 .dc "search-forward" "^S or ^\^\e\^"
2024 This searches forward for a specified search string and positions
2025 point at the end of the string if it's found. If the string is not
2026 found point remains unchanged. This searches from point to the end of
2027 the buffer, so any matches before point will be missed.
2028 If point is moved by more than the variable
2029 .IQ mark-threshold ,
2030 the old
2031 point will be pushed.
2032 .dc "search-forward-nd" "Not Bound"
2033 This is just like
2034 .IQ search-forward
2035 except that it doesn't assume a default search string, and it doesn't set
2036 the default search string. This is useful for defining macros, when you
2037 want to search for something, but you don't want it to affect the current
2038 default search string.
2039 .dc "search-reverse" "^R"
2040 This searches backward for a specified search string and positions
2041 point at the beginning if the string if it's found. If the string is
2042 not found point remains unchanged. This searches from point to the
2043 beginning of the buffer, so any matches after point will be missed.
2044 If point is moved by more than the variable
2045 .IQ mark-threshold ,
2046 the old
2047 point will be pushed.
2048 .dc "search-reverse-nd" "Not Bound"
2049 This is just like
2050 .IQ search-reverse
2051 except that it doesn't assume a default search string, and it doesn't set
2052 the default search string. This is useful for defining macros, when you
2053 want to search for something, but you don't want it to affect the current
2054 default search string.
2055 .dc "select-buffer" "^X\ B"
2056 This selects a new or already existing buffer making it the current
2057 one. You can type either the buffer name or number. If you type in
2058 the name you need only type the name until it is unambiguous, at which
2059 point typing Tab or Space will complete it for you. If you want to
2060 create a new buffer you can type Return instead of Space, and a new
2061 empty buffer will be created.
2062 .dc "select-buffer-1" "Not Bound"
2063 This selects buffer number 1, if it exists.
2064 .dc "select-buffer-10" "Not Bound"
2065 This selects buffer number 10, if it exists.
2066 .dc "select-buffer-2" "Not Bound"
2067 This selects buffer number 2, if it exists.
2068 .dc "select-buffer-3" "Not Bound"
2069 This selects buffer number 3, if it exists.
2070 .dc "select-buffer-4" "Not Bound"
2071 This selects buffer number 4, if it exists.
2072 .dc "select-buffer-5" "Not Bound"
2073 This selects buffer number 5, if it exists.
2074 .dc "select-buffer-6" "Not Bound"
2075 This selects buffer number 6, if it exists.
2076 .dc "select-buffer-7" "Not Bound"
2077 This selects buffer number 7, if it exists.
2078 .dc "select-buffer-8" "Not Bound"
2079 This selects buffer number 8, if it exists.
2080 .dc "select-buffer-9" "Not Bound"
2081 This selects buffer number 9, if it exists.
2082 .dc "self-insert" "Most Printing Characters"
2083 This inserts the character that invoked it into the buffer at point.
2084 Initially all but a few of the printing characters are bound to
2085 .IQ self-insert .
2086 See also
2087 .IQ paren-flash .
2088 .dc "send-typeout-to-buffer" "(variable)"
2089 When this is
2090 .IQ on
2091 \s-2JOVE\s0 will send output that normally overwrites the
2092 screen (temporarily) to a buffer instead. This affects commands like
2093 .IQ list-buffers ,
2094 .IQ list-processes ,
2095 .IQ shell-command-with-typeout ,
2096 and commands that use completion. The default value is
2097 .IQ off .
2098 .dc "set" "Not Bound"
2099 This sets a specified variable to a new value.
2100 .dc "set-mark" "^@"
2101 This sets the mark at the current position in the buffer. It prints
2102 the message \*Q[Point pushed]\*U on the message line. It says that instead
2103 of \*Q[Mark set]\*U because when you set the mark the previous mark is still
2104 remembered on a ring of eight marks. So \*Q[Point pushed]\*U means point is
2105 pushed onto the ring of marks and becomes the value of \*Qthe mark\*U.
2106 To go through the ring of marks, use the
2107 .IQ pop-mark
2108 command. If you type this enough times you will get back
2109 to where you started.
2110 If a
2111 .IQ set-mark
2112 command is given a numeric argument, it acts like a
2113 .IQ pop-mark
2114 command.
2115 .dc "share-dir-pathname" "(variable)"
2116 This tells JOVE where to find the machine-independent configuration
2117 files that it uses, typically some system-wide
2118 .IQ jove.rc
2119 configuration files read on startup,
2120 the formatted help information for the
2121 .IQ describe-*
2122 commands and the tutorial. There is usually a compiled-in path that
2123 should be correct if Jove was properly installed. This path
2124 can also be overridden with the
2125 .IQ -s
2126 command-line option.
2127 .dc "shell" "(variable)"
2128 The shell to be used with all the shell-\(** commands command. If your SHELL
2129 environment variable is set, it is used as the default value of
2130 .IQ shell ;
2131 otherwise \*Q/bin/csh\*U is the default.
2132 See also the description of the
2133 .IQ shell-flags
2134 variable to see how to change the flags passed to this shell.
2135 .dc "shell" "Not Bound"
2136 This starts up an interactive shell in a window; if there is already
2137 an interactive shell, it just selects that buffer.
2138 \s-2JOVE\s0 uses \*Q\(**shell-n\(**\*U (where
2139 .BQ n
2140 is the argument of the command)
2141 as the name of the buffer in which the interacting takes place.
2142 Thus different argument values refer to different interactive shells.
2143 See the \s-2JOVE\s0 manual for information on how to use interactive processes.
2144 See also the variable
2145 .IQ wrap-process-lines .
2146 .dc "shell-command" "^X\ !"
2147 This runs a
2148 .B UNIX
2149 command and places the output from that command in a
2150 buffer.
2151 Within the command, $1 can be used to refer the the filename (if any)
2152 of the selected buffer.
2153 \s-2JOVE\s0 creates a buffer that matches the name of the command
2154 you specify and then attaches that buffer to a window. So, when you
2155 have only one window running, this command will cause \s-2JOVE\s0 to split the
2156 window and attach the new buffer to that window. Otherwise, \s-2JOVE\s0
2157 finds the most convenient of the available windows and uses that one
2158 instead. If the buffer already exists it is first emptied (unless a
2159 numeric argument is specified). If it's already holding a file, not
2160 some output from a previous command, \s-2JOVE\s0 asks permission before
2161 emptying the buffer. Beware that if you go ahead, not only do you
2162 lose any unsaved changes that you made to the buffer, but the buffer's file
2163 name remains set, making it easy to later accidentally overwrite the
2164 original file.
2165 See also the variable
2166 .IQ wrap-process-lines .
2167 .dc "shell-command-no-buffer" "Not Bound"
2168 This is just like
2169 .IQ shell-command
2170 except it just runs the command without saving the output to any buffer.
2171 It will report the success of the command in the usual way.
2172 .dc "shell-command-to-buffer" "Not Bound"
2173 This is just like
2174 .IQ shell-command
2175 except it lets you specify the
2176 buffer to use.
2177 .dc "shell-command-with-typeout" "Not Bound"
2178 This is just like
2179 .IQ shell-command
2180 except that instead of saving the output to a buffer, and displaying
2181 it in a window, this just types out the output in the same way that
2182 .IQ list-buffers
2183 does. Actually, how this behaves depends on the value of the variable
2184 .IQ send-typeout-to-buffer .
2185 If it is
2186 .IQ on
2187 then
2188 .IQ shell-command-with-typeout
2189 will behave just like
2190 .IQ shell-command .
2191 If a numeric argument is given, the \*Qcompleted successfully\*U
2192 message at the end is suppressed.
2193 .dc "shell-flags" "(variable)"
2194 This specifies a flag argument that directs the shell to
2195 take the next argument as a command to be executed.
2196 The default is \*Q\-c\*U (suitable for all known
2197 .B UNIX
2198 shells).
2199 Under MSDOS, the default is \*Q/c\*U (suitable for command.com and
2200 similar MSDOS shells).
2201 Other MSDOS shells, such as MKS KSH require that this be changed to \*Q\-c\*U.
2202 Under MSDOS, \s-2JOVE\s0 puts quotes around the command argument if
2203 .IQ shell-flags
2204 starts with \*Q\-\*U.
2205 See the
2206 .IQ shell
2207 variable to change the default shell.
2208 .dc "shift-region-left" "Not Bound"
2209 This shifts the region left by
2210 .IQ c-indentation-increment
2211 OR by the numeric
2212 argument, if one is supplied. If a negative argument is supplied the
2213 region is shifted the other way.
2214 .dc "shift-region-right" "Not Bound"
2215 This shifts the region right by
2216 .IQ c-indentation-increment
2217 OR by the numeric
2218 argument, if one is supplied. If a negative argument is supplied the
2219 region is shifted the other way.
2220 .dc "show-match-mode" "Not Bound"
2221 This turns on or off the Show Match minor mode in the selected
2222 buffer. Without a numeric argument, the command toggles the mode;
2223 with a zero argument, the mode is turned off; with a non-zero
2224 argument, the mode is turned on. This mode changes \*Q}\*U, \*Q)\*U and
2225 \*Q]\*U so that when they are typed they are inserted as usual, and then the
2226 cursor flashes back to the matching \*Q{\*U, \*Q(\*U or \*Q[\*U (depending on
2227 what was typed) for about half a second, and then goes back to just
2228 after the \*Q}\*U, \*Q)\*U or \*Q]\*U that invoked the command. This is useful
2229 for typing in complicated expressions in a program. You can change
2230 how long the cursor sits on the matching parenthesis by setting the
2231 .IQ paren-flash-delay
2232 variable in tenths of a second. If the matching
2233 \*Q{\*U, \*Q(\*U or \*Q[\*U isn't visible, the line containing the match is
2234 displayed on the message line.
2235 .dc "shrink-window" "Not Bound"
2236 This makes the active window one line shorter, if possible. Windows
2237 must be at least 2 lines high, one for the text and the other for the
2238 mode line.
2239 See also
2240 .IQ grow-window .
2241 .dc "source" "Not Bound"
2242 This reads a bunch of \s-2JOVE\s0 commands from a file.
2243 If a numeric argument is supplied to the
2244 .IQ source
2245 command, it will quietly do nothing if it cannot read the file.
2246
2247 The format of the file is the same as that in the
2248 .BQ jove.rc
2249 file, or
2250 your private
2251 .BQ \&.joverc
2252 in your home directory. There should be one
2253 command per line and it should be as though you were responding to an
2254 .IQ execute-named-command
2255 command while in \s-2JOVE\s0.
2256 A command can be optionally preceded by a numeric argument.
2257 Lines commencing with a # are treated as comments. Control characters such
2258 as ^R may be represented as themselves, or as \*Q^\*U followed by \*QR\*U.
2259 ESC should be represented by ^[.
2260
2261 Sometimes it is useful to do different things in
2262 different circumstances.
2263 To make this possible, there are three conditional commands:
2264 .IQ if ,
2265 .IQ ifenv ,
2266 and
2267 .IQ ifvar .
2268 The
2269 .IQ if
2270 command takes as an operand a shell command, which it runs.
2271 If the command succeeds, the commands after the
2272 .IQ if ,
2273 until a line
2274 containing
2275 .IQ else
2276 or
2277 .IQ endif ,
2278 are performed.
2279 Otherwise, these commands are suppressed and
2280 the commands after any
2281 .IQ else ,
2282 up until an
2283 .IQ endif ,
2284 are executed.
2285 Conditionals nest in the normal way.
2286 The
2287 .IQ ifenv
2288 command takes as operands the name of an environment variable
2289 and a pattern.
2290 If the environment variable is defined and its value matches the pattern,
2291 the
2292 .IQ ifenv
2293 succeeds. Note that patterns are anchored matches from the left.
2294 The
2295 .IQ ifvar
2296 command takes as operands the name of a \s-2JOVE\s0 variable
2297 and a pattern.
2298 If the \s-2JOVE\s0 variable is defined and its value matches the pattern,
2299 the
2300 .IQ ifvar
2301 succeeds.
2302
2303 For example, here are some lines from the file
2304 .BQ jove.rc .
2305 .DS I
2306 bind-to-key pause-jove ^[S
2307 bind-to-key pause-jove ^[s
2308 set process-prompt ^[^%$#]*[%$#]
2309 # source any TERMinal-specific rc file
2310 1 source jove.rc.$TERM
2311 ifvar jove-features .*:iproc:
2312 process-bind-to-key interrupt-process ^C^C
2313 endif
2314 .DE
2315 What they do is to provide two alternative key bindings for
2316 .IQ pause-jove ,
2317 set the variable
2318 .IQ process-prompt ,
2319 and attempt to call
2320 the
2321 .IQ source
2322 command on the file
2323 .BQ jove.rc.$TERM .
2324 Because of the
2325 numeric argument 1, there will be no complaint if this file cannot be found.
2326 If \s-2JOVE\s0 was compiled with interactive-processes enabled (in which
2327 case the string
2328 .IQ :iproc:
2329 will be part of the read-only \s-2JOVE\s0 variable
2330 .IQ jove-features ),
2331 the
2332 .iQ process-bind-to-key
2333 command binds the key sequence Control-C Control-C to the
2334 .IQ interrupt-process
2335 command, which sends the SIGINT signal to interactive shell.
2336 .dc "space-sentence-2" (variable)
2337 If set
2338 .IQ on ,
2339 two spaces are left after each sentence by commands such as
2340 .IQ fill-paragraph ;
2341 otherwise, one space is left. The default is
2342 .IQ on .
2343 .dc "spell-command-format" "(variable)"
2344 This is the format specification string for a command which will run
2345 a spell checker on a specified file and produce
2346 a list of misspelled words on the output. This variable (and related
2347 .IQ spell-buffer
2348 capability) is only available
2349 if Jove is built with support for subshells. The string must contain one
2350 instance of the specifier %s which will be replaced with
2351 the pathname of the file to be checked.
2352 .dc "spell-buffer" "Not Bound"
2353 This saves the current buffer and runs it through the
2354 .B UNIX
2355 .IQ spell
2356 command (specified by the variable
2357 .IQ spell-command-format
2358 ) and places
2359 the output in buffer \*QSpell\*U. Then \s-2JOVE\s0 lets you edit the list of
2360 words, expecting you to delete the ones that you don't care about, i.e., the
2361 ones you know are spelled correctly. Then the
2362 .IQ parse-spelling-errors-in-buffer
2363 command comes along and finds all the
2364 misspelled words and sets things up so the error commands
2365 .IQ next-error ,
2366 .IQ previous-error
2367 and
2368 .IQ current-error
2369 work. See also the variable
2370 .IQ error-window-size .
2371 .dc "split-current-window" "^X\ 2"
2372 This splits the active window into two equal parts (providing the
2373 resulting windows would be big enough) and displays the selected buffer
2374 in both windows. Use
2375 .IQ delete-other-windows
2376 to go back to 1 window mode. If a numeric
2377 argument is supplied, the window is split \*Qevenly\*U that many times (when
2378 possible).
2379 .dc "start-remembering" "Not Bound"
2380 This is just another name for the
2381 .IQ begin-kbd-macro
2382 command. It is included for backward compatibility.
2383 .dc "stop-process" "Not Bound"
2384 Send the signal SIGTSTP to the interactive process in the selected buffer.
2385 This is equivalent to sending the \*Qstop\*U character (which most people
2386 have bound to ^Z) to the process. This only works if you are in a buffer
2387 bound to an interactive process.
2388 .dc "stop-remembering" "Not Bound"
2389 This is just another name for the
2390 .IQ end-kbd-macro
2391 command. It is included for backward compatibility.
2392 .dc "string-length" "Not Bound"
2393 This prints the number of characters in the string that point sits in.
2394 Strings are surrounded by double quotes. \s-2JOVE\s0 knows that
2395 \*Q\^\e\^007\*U is considered a single character, namely \*Q^G\*U, and also
2396 knows about other common ones, like \*Q\^\e\^r\*U (Return) and \*Q\^\e\^n\*U
2397 (Linefeed). This is mostly useful only for C programmers.
2398 .dc "suspend-jove" "Not Bound"
2399 This is a synonym for
2400 .IQ pause-jove .
2401 .dc "sync-frequency" "(variable)"
2402 The temporary files used by \s-2JOVE\s0 are forced out to disk every
2403 .IQ sync-frequency
2404 modifications. The default is 50, which really makes
2405 good sense. Unless your system is very unstable, you probably
2406 shouldn't fool with this.
2407 .dc "tab-width" "(variable)"
2408 When \s-2JOVE\s0 displays a Tab character, it moves point forward to the
2409 next multiple of this variable. If the value is 0, tab is displayed as ^I,
2410 not whitespace.
2411 The default value is 8.
2412 .dc "tag-file" "(variable)"
2413 This is the name of the file in which \s-2JOVE\s0 should look up tag
2414 definitions. The default value is \*Q.\^/tags\*U.
2415 .dc "text-attribute" "(variable)"
2416 (IBM PC version only) This specifies the screen attribute (color) for
2417 normal text characters. The default is 7 (white on black).
2418 .dc "teach-jove" "Not Bound"
2419 This loads the Jove tutorial from from
2420 the
2421 .BQ ~/teach-jove
2422 file if it was already saved there, else it loads the reference copy
2423 from
2424 .BQ SHAREDIR/teach-jove
2425 into a buffer that will save to
2426 .BQ ~/teach-jove,
2427 replacing the old standalone
2428 .I teachjove
2429 command. The
2430 .IQ -T
2431 option, if given to JOVE on the command line, will start JOVE up with
2432 the tutorial loaded.
2433 .dc "text-mode" "Not Bound"
2434 This sets the major mode to Text. This affects what \s-2JOVE\s0 considers
2435 as characters that make up words. For instance, Single-quote is not part of
2436 a word in Fundamental mode, but is in Text mode.
2437 .dc "tmp-file-pathname" "(variable)"
2438 This tells \s-2JOVE\s0 where to put the tmp files, which is
2439 where \s-2JOVE\s0 stores buffers internally. The default is in
2440 .BQ /tmp ,
2441 or as set up when your system
2442 was compiled, but if you want to
2443 store them somewhere else, you can set this variable. If your system
2444 crashes a lot it might be a good idea to set this variable to somewhere
2445 other than
2446 .BQ /tmp
2447 because the system removes all the files in
2448 .BQ /tmp
2449 upon
2450 reboot, and so you would not be able to recover editor buffers using the
2451 .IQ "jove -r"
2452 command.
2453
2454 NOTE: In order for this to work correctly you must set this variable
2455 BEFORE \s-2JOVE\s0 creates the tmp file. You can set this in your
2456 .BQ \&.joverc
2457 (the closer to the beginning the better), or as soon as you
2458 start up \s-2JOVE\s0 before you read any files.
2459 .dc "transpose-characters" "^T"
2460 This switches the character before point with the one after point, and
2461 then moves forward one. This doesn't work at the beginning of the
2462 line, and at the end of the line it switches the two characters before
2463 point. Since point is moved forward, so that the character that was
2464 before point is still before point, you can use
2465 .IQ transpose-characters
2466 to drag a character down the length of a line.
2467 .dc "transpose-lines" "^X\ ^T"
2468 This switches the current line with the one above it, and then moves
2469 down one so that the line that was above point is still above point.
2470 This, like
2471 .IQ transpose-characters ,
2472 can be used to drag a line down a page.
2473 .dc "unbound" "Not Bound"
2474 This command acts as if an unbound key sequence were typed.
2475 In fact, that is its use: if you wish to unbind a key sequence,
2476 simply bind it to this command.
2477 .dc "update-time-frequency" "(variable)"
2478 How often the mode line is updated (and thus the time). The
2479 default is 30 seconds.
2480 .dc "use-i/d-char" "(variable)"
2481 If your terminal has insert/delete character capability you can tell
2482 \s-2JOVE\s0 not to use it by setting this to
2483 .IQ off .
2484 In my opinion it is only worth using
2485 insert/delete character at low baud rates. WARNING: if you set this to
2486 .IQ on
2487 when your terminal doesn't have insert/delete character capability,
2488 you will get weird (perhaps fatal) results.
2489 .dc "version" "Not Bound"
2490 Displays the version number of this \s-2JOVE\s0.
2491 .dc "visible-bell" "(variable)"
2492 If the terminal has a visible bell, use it instead of beeping.
2493 .dc "visible-spaces-in-window" "Not Bound"
2494 This displays an underscore character instead of each Space in the
2495 window and displays a greater-than followed by spaces for each Tab
2496 in the window. The actual text in the buffer is not changed; only
2497 the screen display is affected. To turn this off you run the command
2498 again; it toggles.
2499 .dc "visit-file" "^X\ ^V or ^X\ ^R"
2500 This reads a specified file into the selected buffer replacing the old
2501 text. If the buffer needs saving \s-2JOVE\s0 will offer to save it for you.
2502 Sometimes you use this to start over, say if you make lots of changes
2503 and then change your mind. If that's the case you don't want \s-2JOVE\s0 to
2504 save your buffer and you answer \*QNO\*U to the question.
2505 .dc "window-find" "^X\ 4"
2506 This lets you select another buffer in another window three
2507 different ways. This waits for another character which can be one of
2508 the following:
2509 .DS I
2510 .ta .5i 1i 1.5i
2511 T Finds a tag in the other window.
2512 ^T Finds the tag at point in the other window
2513 F Finds a file in the other window.
2514 B Selects a buffer in the other window.
2515 .DE
2516 This is just a convenient short hand for
2517 .IQ split-current-window
2518 (or
2519 .IQ previous-window
2520 if there are
2521 already two windows) followed by the appropriate sequence for invoking each
2522 command. With this, though, there isn't the extra overhead of having to
2523 redisplay. In addition, you don't have to decide whether to use
2524 .IQ split-current-window
2525 or
2526 .IQ previous-window
2527 since
2528 .IQ window-find
2529 does the right thing.
2530 .dc "word-abbrev-mode" "Not Bound"
2531 This turns on or off Word Abbrev minor mode in the selected buffer.
2532 Without a numeric argument, the command toggles the mode; with a
2533 zero argument, the mode is turned off; with a non-zero argument,
2534 the mode is turned on. Word Abbrev mode lets you specify a word (an
2535 abbreviation) and a phrase with which \s-2JOVE\s0 should substitute
2536 the abbreviation. You can use this to define words to expand into
2537 long phrases, e.g., \*Qjove\*U can expand into
2538 \*QJonathan's Own Version of Emacs\*U;
2539 another common use is defining words that you often misspell
2540 in the same way, e.g., \*Qthier\*U => \*Qtheir\*U or \*Qteh\*U => \*Qthe\*U.
2541 See the information on the
2542 .IQ auto-case-abbrev
2543 variable.
2544 .sp 1
2545 There are two kinds of abbreviations: mode specific and global. If you
2546 define a Mode specific abbreviation in C mode, it will expand only in
2547 buffers that are in C mode. This is so you can have the same
2548 abbreviation expand to different things depending on your context.
2549 Global abbreviations expand regardless of the major mode of the buffer.
2550 The way it works is this: \s-2JOVE\s0 looks first in the mode specific
2551 table, and then in the global table. Whichever it finds it in first is
2552 the one that's used in the expansion. If it doesn't find the word it is
2553 left untouched. \s-2JOVE\s0 tries to expand words when
2554 you type a punctuation character or Space or Return. If you are in Auto
2555 Fill mode the expansion will be filled as if you typed it yourself.
2556 .dc "wrap-process-lines" "(variable)"
2557 If this variable is
2558 .IQ on ,
2559 the process output that is captured in a
2560 buffer is wrapped just before the line would have as many characters as
2561 there are columns on the screen.
2562 This introduces extra newlines, but it makes the output more
2563 readable.
2564 Note that the folding does not take into account that some
2565 characters (notably tabs) occupy more than one column of the
2566 display.
2567 The output of the
2568 .IQ filter-region
2569 command is not processed in this way
2570 because the extra newlines are presumed to be undesired in this case.
2571 .dc "wrap-search" "(variable)"
2572 If set, searches will \*Qwrap around\*U the ends of the buffer instead
2573 of stopping at the bottom or top. The default is
2574 .IQ off .
2575 .dc "write-file" "^X\ ^W"
2576 This saves the selected buffer to a specified file, and then makes that
2577 file the default file name for this buffer. If you specify a file
2578 that already exists you are asked to confirm over-writing it.
2579 .dc "write-files-on-make" "(variable)"
2580 When set, all modified files will be written out before calling
2581 make when the
2582 .IQ compile-it
2583 command is executed. The default is
2584 .IQ on .
2585 .dc "write-macros-to-file" "Not Bound"
2586 This writes the currently defined macros to a specified file in a format
2587 appropriate for reading them back in with the
2588 .IQ source
2589 command. The purpose of this command is to allow you to define macros
2590 once and use them in other instances of \s-2JOVE\s0.
2591 See also the
2592 .IQ define-macro
2593 command.
2594 .dc "write-modified-files" "^X\ ^M"
2595 This saves all the buffers that need saving. If you supply a numeric
2596 argument it asks, for each buffer, whether you really want to save it.
2597 .dc "write-region" "Not Bound"
2598 This writes the text in the region to a specified file. If the file
2599 already exists you are asked to confirm over-writing it.
2600 .dc "write-word-abbrev-file" "Not Bound"
2601 This writes the currently defined abbreviations to a specified file.
2602 They can be read back in and automatically defined with
2603 .IQ read-word-abbrev-file .
2604 .dc "xj-mouse-commands" "^X\ m\(**"
2605 Programs such as XJove and JoveTool generate these commands whenever a mouse
2606 button is pressed or released, or the mouse is moved while the button is
2607 pressed. They are followed by parameters giving parameters for the
2608 button pressed, the coordinates of the mouse, etc. They are not
2609 intended for direct use by the normal user.
2610 .sp 1
2611 The individual commands will now be described.
2612 .dc "xj-mouse-copy-cut" "^X\ m8"
2613 Performs a
2614 .IQ copy-region
2615 if the CTRL key was down, or a
2616 .IQ kill-region
2617 if
2618 both CTRL and SHIFT were down.
2619 This command is normally bound to the release of button 2.
2620 .dc "xj-mouse-line" "^X\ m7"
2621 Sets the region to be the whole line containing the cursor.
2622 This command is normally bound to a triple down click of button 2, and
2623 the presumed effects of the preceding double click are first undone.
2624 .dc "xj-mouse-mark" "^X\ m5"
2625 Both point and mark are set to the cursor.
2626 This command is normally bound to the pressing of button 2.
2627 .dc "xj-mouse-point" "^X\ m[01249]"
2628 Point is set to the cursor.
2629 This command is normally bound to the single, double, and triple
2630 down-click and the dragging of button 1; also the dragging of button 2.
2631 .dc "xj-mouse-word" "^X\ m6"
2632 Sets the region to be the word (or the gap between two words)
2633 containing the cursor.
2634 This command is normally bound to a double down click of button 2, and
2635 the presumed effects of the preceding single click are first undone.
2636 .dc "xj-mouse-yank" "^X\ m3"
2637 Performs a
2638 .IQ yank
2639 if the CTRL key was down.
2640 This command is normally bound to the release of button 1.
2641 .dc "xt-mouse" "(variable)"
2642 When set, \s-2JOVE\s0 sends XTerm escape sequences to enable and
2643 disable the mouse messages at appropriate times.
2644 Warning: due to the way XTerm encodes mouse events, if
2645 .IQ meta-key
2646 is set, mouse actions beyond column 95 or row 95 will be misunderstood;
2647 in any case, mouse actions beyond column 223 or row 223 will be misunderstood.
2648 .dc "xt-mouse-commands" "ESC\ [ M\(**"
2649 Programs such as XTerm generate these commands whenever a mouse button
2650 is pressed or released.
2651 XTerm does not give the user as much power as XJove.
2652 They are followed by parameters specifying the
2653 button pressed, the coordinates of the mouse, etc.
2654 They are not intended for direct use by the normal user.
2655 Set the variable
2656 .IQ xt-mouse
2657 on to enable XTerm mouse mode.
2658 .sp 1
2659 The individual commands will now be described.
2660 .dc "xt-mouse-mark" "^X\ m5"
2661 Both point and mark are set to the cursor.
2662 This command is normally bound to the pressing of button 2.
2663 .dc "xt-mouse-point" "^X\ m[01249]"
2664 Point is set to the cursor.
2665 This command is normally bound to the down-click of button 1.
2666 .dc "xt-mouse-up" "^X\ m6"
2667 As the name implies, this command is normally bound to the release
2668 of any button (XTerm does not specify which button was released).
2669 Note that a normally configured XTerm will not pass on mouse events
2670 if the CTRL or SHIFT keys are pressed. Point is set to the cursor.
2671 If the most recently pressed button was button 1 and the CTRL key
2672 was down (and not the SHIFT key), this command performs a
2673 .IQ yank .
2674 If
2675 the most recently pressed button was button 2 and the CTRL key was
2676 down, this command performs a
2677 .IQ copy-region .
2678 If the most recently pressed
2679 button was button 2 and the CTRL and SHIFT keys were down, this
2680 command performs a
2681 .IQ kill-region .
2682 .dc "yank" "^Y"
2683 This inserts the text at the front of the kill ring (as set by an earlier
2684 .IQ copy-region ,
2685 .IQ kill-region ,
2686 etc.) at point.
2687 When you do multiple kill commands in a row, they are
2688 merged so that the
2689 .IQ yank
2690 command yanks back all of them.
2691 .dc "yank-pop" "ESC\ Y"
2692 \s-2JOVE\s0 has a kill ring on which the last sixteen kills are stored.
2693 This command yanks back previous texts from the kill ring.
2694 .IQ yank
2695 yanks a copy of the text at the
2696 front of the ring. If you want one of the last sixteen kills you then use
2697 .IQ yank-pop
2698 which rotates the ring so another different entry is now at the
2699 front. You can use
2700 .IQ yank-pop
2701 only immediately following a
2702 .IQ yank
2703 or
2704 another
2705 .IQ yank-pop .
2706 If you supply a negative numeric argument the ring
2707 is rotated the other way. If you use this command enough times in a
2708 row you will eventually get back to where you started.