From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel Subject: Re: "No further undo information" clutters *Messages* buffer Date: Wed, 26 Oct 2005 10:11:55 -0600 Message-ID: References: <435C998C.3030801@gmx.at> <435F7197.1080108@gmx.at> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1130344332 7397 80.91.229.2 (26 Oct 2005 16:32:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 26 Oct 2005 16:32:12 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 18:32:10 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EUo7a-0000OP-AX for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2005 18:27:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EUo7Z-0003DV-Mi for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2005 12:27:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EUo7L-0003CI-EX for emacs-devel@gnu.org; Wed, 26 Oct 2005 12:27:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EUo7J-0003BS-Nl for emacs-devel@gnu.org; Wed, 26 Oct 2005 12:27:11 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EUo7J-0003BK-Hi for emacs-devel@gnu.org; Wed, 26 Oct 2005 12:27:09 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1EUo7J-0007rZ-Gw for emacs-devel@gnu.org; Wed, 26 Oct 2005 12:27:09 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EUnym-0003T5-02 for emacs-devel@gnu.org; Wed, 26 Oct 2005 18:18:20 +0200 Original-Received: from 207.167.42.60 ([207.167.42.60]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Oct 2005 18:18:19 +0200 Original-Received: from ihs_4664 by 207.167.42.60 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Oct 2005 18:18:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 37 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 207.167.42.60 User-Agent: Mozilla Thunderbird 0.9 (X11/20041105) X-Accept-Language: en-us, en In-Reply-To: <435F7197.1080108@gmx.at> X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:44905 Archived-At: martin rudalics wrote: > > Is it inevitable that `undo-more' raises an error when there is no > > further undo information? > > > > That seems like the right thing to do. > > Eventually > > Undo! > undo-more: No further undo information > > occupied more than 90% of my `*Messages*' buffer which made it quite > difficult to trace more interesting error messages. I finally turned > this off by making `undo-more' display a non-logged message and ding > when there was no more undo information. Hardly the right thing to do > but I didn't know better. You could do that fairly cleanly with advice: (defadvice undo-more (around disable-message-log activate) "Don't log \"No further undo information\" error messages." ;; Note that the "Undo!" messages are displayed by `undo', which ;; calls `undo-more' directly and via `undo-start'. `undo-start' ;; also logs "No undo information in this buffer" error messages. (let ((message-log-max nil)) ad-do-it)) > Ideally, I wanted `undo' issue `Undo...', `Redo...', etc. first. If the > operation succeeded it would display `Undo...done', `Redo...done', etc. > Otherwise, it would issue `Undo...', `Redo...', etc. with the according > error text appended. In any case `message_log_check_duplicate' would > take care of the rest. Hmmm... -- Kevin Rodgers