From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: What's the problem? Date: 13 Dec 2003 13:08:48 +0900 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87iskl741b.fsf@tc-1-100.kawasaki.gol.ne.jp> References: <4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu> <5bad69zd43.fsf@lister.roxen.com> <4noeuon378.fsf@lockgroove.bwh.harvard.edu> <4ny8tsgxy6.fsf@lockgroove.bwh.harvard.edu> <4nhe0ggv0u.fsf@lockgroove.bwh.harvard.edu> <4nk75bwjaf.fsf@lockgroove.bwh.harvard.edu> <4nsmjv8d32.fsf@collins.bwh.harvard.edu> <87iskpbloe.fsf@mail.jurta.org> Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AV19e-0002KH-00 for ; Sat, 13 Dec 2003 05:13:22 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AV19e-0001Fo-00 for ; Sat, 13 Dec 2003 05:13:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AV23N-0006lK-J2 for emacs-devel@quimby.gnus.org; Sat, 13 Dec 2003 00:10:57 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AV23I-0006kk-Du for emacs-devel@gnu.org; Sat, 13 Dec 2003 00:10:52 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AV22l-0006Xl-5s for emacs-devel@gnu.org; Sat, 13 Dec 2003 00:10:51 -0500 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AV22k-0006XW-NG for emacs-devel@gnu.org; Sat, 13 Dec 2003 00:10:18 -0500 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AV15H-0004kd-00 for ; Sat, 13 Dec 2003 05:08:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AV15F-0004kV-00 for ; Sat, 13 Dec 2003 05:08:49 +0100 Original-Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AV15F-0006dn-00 for ; Sat, 13 Dec 2003 05:08:49 +0100 Original-Lines: 26 Original-X-Complaints-To: usenet@sea.gmane.org System-Type: i686-pc-linux-gnu X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18665 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18665 Richard Stallman 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