[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Minibuffer wipeout: "Auto-saving... done"

From: Kevin Rodgers
Subject: Re: Minibuffer wipeout: "Auto-saving... done"
Date: Tue, 06 Jul 2004 12:13:17 -0600
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv: Gecko/20020406 Netscape6/6.2.2

David Vanderschel wrote:
> I have a program which prepares a multi-line display for interaction
> in the minibuffer.  It behaves as I intend.  However, I have a problem
> in that the content of the buffer is occasionally erased by the 'echo'
> which results from auto-saving.  (My program remains active and will
> react to input correctly even though its display in the minibuffer has
> been wiped out.  Oddly, my enlarged height for the minibuffer remains
> in effect.)  I was aware of the fact that I needed to have
> echo-keystrokes set to 0 to avoid one possible source of such
> preemptions of the minibuffer; but I would like to have some advice
> about how to prevent getting my minibuffer content erased by the
> string "Auto-saving... done."
> I tried executing do-auto-save just before invoking my function.  All
> that did was to _assure_ that my minibuffer content was wiped out -
> even when I put a (sit-for 5) after the do-auto-save and before my
> program selected the minibuffer window and wrote in it.  (I find this
> symptom incomprehensible; so, if someone could enlighten me, I would
> appreciate it.)

Did you specify a non-nil NO-MESSAGE argument to do-auto-save?

> I also tried a let binding on auto-save-interval to
> set it to something large while my minibuffer window was active.  No
> joy.  FWIW, the buffer current when the function can be invoked is not
> itself even subject to auto-saving - it doesn't even have an
> associated file.

Hmmm, I think binding auto-save-interval would have worked.  You might
also try binding auto-save-timeout to a large value.

> A good solution would be a method for temporarily suppressing all
> auto-saves while my interaction is in progress, which should never be
> for more than a few tens of seconds.

Kevin Rodgers

reply via email to

[Prev in Thread] Current Thread [Next in Thread]