Re: What's the problem?

[Miles Bader <miles@gnu.org>]

Richard Stallman <rms@gnu.org> writes:
>     Sure; I hate auto-save delays too (even more annoying is the !@#$%!
>     purposeful-delay-to-give-an-error-message autosave does when it can't
>     write a file)
> 
> It would be easy to change that.  The question is, what other way
> should it make sure the user sees that there is an error?

Some things that come to mind are:

 * Make sure the pause is cleanly canceled if you hit ^G (I'm not really
   sure what it does now, but it acts very strangely if you hit ^G)

 * Only pause to show the error message the first time the autosave for
   a particular file fails; if subsequent autosaves fail, just show the
   error message with no pause (however, if autosave then _succeeds_ at
   some point, it should presumably reset the state so that it pauses
   upon any failure after that)

 * maybe put a big obvious warning in the modeline for buffers where
   autosave failed (text, uppercase, red, blinking... :-)

-Miles
-- 
"Most attacks seem to take place at night, during a rainstorm, uphill,
 where four map sheets join."   -- Anon. British Officer in WW I