jove [-d directory] [-w] [-t tag] [+[n] file] [-p file] [files] jove -r
JOVE works on any reasonable display terminal that is described in the termcap file (see TERMCAP(5) for more details). When you start up JOVE, it checks to see whether you have your TERM environment variable set. On most systems that will automatically be set up for you, but if it's not JOVE will ask you what kind of terminal you are using. To avoid having to type this every time you run JOVE you can set your TERM environment variable yourself. How you do this depends on which shell you are running. If you are running the C Shell, as most of you are, you type
% setenv TERM
type
and with the Bourne Shell, you type
$ TERM=
type
; export TERM
where type is the name of the kind of terminal you are using (e.g., vt100). If neither of these works get somebody to help you.
The names of all of the files specified on the command line are saved in a buffer, called *minibuf*. The mini-buffer is a special JOVE buffer that is used when JOVE is prompting for some input to many commands (for example, when JOVE is prompting for a file name). When you are being prompted for a file name, you can type C-N (that's Control-N) and C-P to cycle through the list of files that were specified on the command line. The file name will be inserted where you are typing and then you can edit it as if you typed it in yourself.
JOVE recognizes the following switches:
alias cd 'cd \!*; setenv CWD $cwd' alias popd 'popd \!*; setenv CWD $cwd' alias pushd 'pushd \!*; setenv CWD $cwd'
Recover looks for JOVE buffers that are left around and are owned by you. (You cannot recover other peoples' buffers, obviously.) If there were no buffers that were modified at the time of the crash or there were but recover can't get its hands on them, you will be informed with the message, "There is nothing to recover." Otherwise, recover prints the date and time of the version of the buffers it has, and then waits for you type a command.
To get a list of the buffers recover knows about, use the list command. This will list all the buffers and the files and the number of lines associated with them. Next to each buffer is a number. When you want to recover a buffer, use the get command. The syntax is get buffer filename where buffer is either the buffer's name or the number at the beginning of the line. If you don't type the buffer name or the filename, recover will prompt you for them.
If there are a lot of buffers and you want to recover all of them, use the recover command. This will recover each buffer to the name of the buffer with ".#" prepended to the name (so that the original isn't over-written). It asks for each file and if you want to restore that buffer to that name you type "yes". If you want to recover the file but to a different name, just type the new name in. If you type "no" recover will skip that file and go on to the next one.
If you want to look at a buffer before deciding to recover it, use the print command. The syntax for this is print buffer where buffer again is either its name or the number. You can type ^C if you want to abort printing the file to the terminal, and recover will respond with an appropriate message.
When you're done and have all the buffers you want, type the quit command to leave. You will then be asked whether it's okay to delete the tmp files. Most of the time that's okay and you should type "yes". When you say that, JOVE removes all traces of those buffers and you won't be able to look at them again. (If you recovered some buffers they will still be around, so don't worry.) So, if you're not sure whether you've gotten all the buffers, you should answer "no" so that you'll be able to run recover again at a later time (presumably after you've figured out which ones you want to save).
If you type ^C at any time other than when you're printing a file to the terminal, recover will exit without a word. If you do this but wish you hadn't, just type "jove -r" to the shell again, and you will be put back with no loss.
Once you know the name of a command, you can find out what it does with the describe-command command, which you can invoke quickly by typing "ESC ?". The apropos command will give you a list of all the command with a specific string in their names. For example, if you want to know the names of all the commands that are concerned with windows, you can run "apropos" with the keyword window.
If you're not familar with the EMACS command set, it would be worth your while to use run TEACHJOVE. Do do that, just type "teachjove" to your shell and you will be placed in JOVE in a file which contains directions. I highly recommend this for beginners; you may save yourself a lot of time and headaches.
You can also change the way JOVE behaves in little ways by changing the value of some variables with the set command. The syntax is "set <variable> value", where value is a number or a string, or "on" or "off", depending on the context. For example, if you want JOVE to make backup files, you set the "make-backup-files" variable to "on". To see the value of a variable, use the "print <variable>" command.
set match-regular-expressions on auto-execute-command auto-fill /tmp/Re\|.*drft bind-to-key i-search-forward ^\ bind-to-key i-search-reverse ^R bind-to-key find-tag-at-point ^[^T bind-to-key scroll-down ^C bind-to-key grow-window ^Xg bind-to-key shrink-window ^Xs(Note that the Control Characters can be either two character sequences (e.g. ^ and C together as ^C) or the actual control character. If you want to use an ^ by itself you must BackSlash it (e.g., bind-to-key grow-window ^X\^ binds grow-window to "^X^").
set allow-^S-and-^Q onin your initialization file.
If your terminal has a metakey, JOVE will use it if you turn on the "meta-key" variable. JOVE will automatically turn on "meta-key" if the METAKEY environment variable exists. This is useful for if you have different terminals (e.g., one at home and one at work) and one has a metakey and the other doesn't.
~/.joverc - personal initialization file
TMPDIR - where temporary files are stored
LIBDIR/teach-jove - the interactive tutorial
LIBDIR/portsrv - for running shells in windows (pdp11 only)
ed(1) - for a description of regular expressions teachjove(1) - for an interactive JOVE tutorial.
Searches can't cross line boundaries.