Re: emacs should quiz that #backups# exist by default

[Dan Jacobson <jidanni@dman.ddts.net>]

>>>>> "RMS" == Richard Stallman <rms@gnu.org> writes:

RMS> Emacs normally displays a message at startup
RMS> when there is a .saves file that indicates that a session crashed.

RMS> Does this message appear when you start Emacs?

$ LC_ALL=C emacs --no-site-file -q -nw qqqqq
then hold down a key until you have enough chars that 'auto saving'
flashes in the minibuffer then hit C-z
[1]+  Stopped                 LC_ALL=C emacs --no-site-file -q -nw qqqqq
$ kill %
[1]+  Terminated              LC_ALL=C emacs --no-site-file -q -nw qqqqq
$ LC_ALL=C emacs --no-site-file -q -nw 
one sees just the cheery usual stuff, including the
   If an Emacs session crashed recently, type M-x recover-session RET
   to recover the files you were editing.
which is not good enough for busy Dan.

anyways, what I want is a yes or no querying the user if anything bad
happened that he hasn't fully acknowledged yet that he is aware of.

i.e. not just some message that will surely get covered up when his
xsesson file calls emacs -f gnus& next monday upon return to work
after the power failure and after he forgot what file he was editing
or that there ever was a power failure or that some file is messed up.

also he might have 3 emacs's open and already seen your warning but
didn't answer "yes" before he was called away and logoffed and now
logged in again [so he should be warned again].

P.S. I see there is a
$ ll -ta /home/jidanni/.backups|head
-rw-r--r--    1 jidanni  jidanni        62 2004-05-15 16:43 .saves-8856-localhost.localdomain~
file from year 2004 that somehow is there... maybe that is blocking
the action, I'll remove it

sorry, still didn't see anything. maybe what RMS is talking about
isn't enabled by default.  anyway http://jidanni.org/comp/emacs.txt is
what I use.

Eli> Does "M-x recover-session RET" do what you want?

Indeed, that does a great job.

What I want is "what about the user who left work on Friday when power
failed, and boozed it up over the weekend, and now its Monday, and
nobody has reminded him that one of the project files is in
trouble..." emacs know it but won't tell him unless asked.