![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to recover.nr CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSD / contrib / jove / doc|
Return to recover.nr CVS log | Up to [CSRG BSD Unix] / 43BSD / contrib / jove / doc |
1.1 root 1: .TH JOVE_RECOVER 1 "12 February 1986"
2: .ad
3: .SH NAME
4: jove_recover - recover JOVE buffers after a system/editor crash
5: .SH SYNOPSIS
6: jove_recover [-syscrash] [-d directory]
7: jove -r
8: .SH DESCRIPTION
9: JOVE_RECOVER lets you recover your work in the JOVE editor in the event of a
10: system or JOVE crash. It is designed to put invoked through JOVE with the
11: "-r" switch. JOVE_RECOVER looks for JOVE buffers that are left around and
12: are owned by you. (You cannot recover other peoples' buffers, obviously.)
13: When the system is rebooted after a crash, you type "jove -r" after you've
14: logged in. If there were no buffers that were modified at the time of the
15: crash or there were but JOVE_RECOVER can't get its hands on them, you will be
16: informed with the message, There is nothing here for you. Otherwise,
17: JOVE_RECOVER prints the date and time of the version of the buffers it has,
18: and then waits for you type a command.
19: .LP
20: To get a list of the buffers JOVE_RECOVER knows about, use the
21: .I list
22: command. This will list all the buffers and the files and the number of
23: lines associated with them. Next to each buffer is a number. When you want
24: to recover a buffer, use the
25: .I get
26: command. The syntax is
27: .I get buffer filename
28: where
29: .I buffer
30: is either the buffer's name or the number at the beginning of the line. If
31: you don't type the buffer name or the filename, JOVE_RECOVER will prompt you
32: for them.
33: .LP
34: If there are a lot of buffers and you want to recover all of them, use the
35: .I recover
36: command. This will recover each buffer to the name of the buffer with ".#"
37: prepended to the name (so that the original isn't over-written). It asks
38: for each file and if you want to restore that buffer to that name you type
39: "yes". If you want to recover the file but to a different name, just type
40: that name in. If you type "no" JOVE_RECOVER will skip that file and go on
41: to the next one.
42: .LP
43: If you want to look at a buffer before deciding to recover it, use the
44: .I print
45: command. The syntax for this is
46: .I print buffer
47: where
48: .I buffer
49: again is either its name or the number. You can type ^C if you want to
50: abort printing the file to the terminal, and JOVE_RECOVER will respond with
51: an appropriate message.
52: .LP
53: When you're done and have all the buffers you want, type the
54: .I quit
55: command to leave. You will then be asked whether it's okay to delete the
56: tmp files. Most of the time that's okay and you should type "yes". When
57: you say that, JOVE removes all traces of those buffers and you won't be able
58: to look at them again. (If you recovered some buffers they will still be
59: around, so don't worry.) So, if you're not sure whether you've gotten all
60: the buffers, you should answer "no" so that you'll be able to run
61: JOVE_RECOVER again at a later time (presumably after you've figured out
62: which ones you want to save).
63: .LP
64: If you type ^C at any time other than when you're printing a file to the
65: terminal, JOVE_RECOVER will exit without a word. If you do this but wish you
66: hadn't, just type "jove -r" to the shell again, and you will be put back
67: with no loss.
68: .SH A SAMPLE SESSION
69: .sp 1
70: .nf
71: % jove -r
72: Found 2 buffers (last updated: Sun Apr 14 14:13:38 1985).
73: (Type '?' for options): list
74: 1) buffer recover.1 "/u/staff/jpay/doc/recover.1" (120 lines)
75: 2) buffer recover.c "/u/staff/jpay/jove/recover.c" (635 lines)
76: (Type '?' for options): get recover.1 recover.save
77: "recover.save" 53 lines, 1821 characters.
78: (Type '?' for options): quit
79: Should I delete the tmp files? yes
80: %
81: .fi
82: .LP
83: Here I "got" the buffer
84: .I recover.1
85: and restored it to the temporary file
86: .I recover.save.
87: It's generally a good idea to recover buffers to temporary files and then
88: compare them to the original or at least look them over before putting them
89: back in their real name. This is just in case you were restoring what you
90: thought you were restoring.
91: .fi
92: .SH FILES
93: TMPDIR - where temporary files are stored.
94: .SH SEE ALSO
95: JOVE(1) - for this to make any sense to you.
96: .SH DIAGNOSTICS
97: JOVE_RECOVER diagnostics are meant to be self-explanitory.
98: .SH BUGS
99: It works well enough...
100: .SH AUTHOR
101: Jonathan Payne
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.