On Fri, Oct 07, 2005 at 01:26:47PM -0500, Steve Greenland wrote:
> On 07-Oct-05, 12:36 (CDT), Chris Joseph <[EMAIL PROTECTED]> wrote:
> > Several recent reboots have resulted in my receiving a message, reporting
> > that a file has been saved for recovery (ie one identical message
> > each time the system reboots). There is no file at the location given in
> > the message (and the X-vi-recover-file header), however - but there is a
> > binary containing an apparently unedited message (and other data) at the
> > location given by the X-vi-recover-path header.
>
> I'm not quite sure what the bug is, here, or what you're seeing. What
> does 'nvi -r' show?
$ nvi -r
Thu Aug 25 00:35:36 2005: /tmp/mutt-chiark-3002-3
$ ls /tmp/mutt-chiark-3002-3
ls: /tmp/mutt-chiark-3002-3: No such file or directory
I have a sudden sinking feeling that this is a misunderstanding on my
part; I had understood the email (and documentation) to be saying that the
file had *already* been recovered to that location. Whereas what it
actually means is that $ nvi -r /tmp/mutt-chiark-3002-3 will recover the
file (to that location, rather than from it), yes? (Which indeed it does.)
In which case, I'm suffering from #155793 ("sending reminders on
reboot is ineffective") combined with slightly ambiguous wording of the
docs and insufficient sleep. It might be worth a wording change (perhaps
"... when it was saved to [recovery path] for recovery. You..." in the
email sent out by the recovery program), but there isn't anything else
wrong. Apologies for the confusion and waste of your time, Steve.
Chris.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
