From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: undoing changes automatically Date: Wed, 09 Jan 2008 00:24:41 -0500 Message-ID: References: <18231.43165.842097.720674@tfkp07.physik.uni-erlangen.de> <853avbp6ie.fsf@lola.goethe.zz> <18232.50129.24712.310255@tfkp07.physik.uni-erlangen.de> <18308.10385.319747.688235@tfkp07.physik.uni-erlangen.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199856295 2765 80.91.229.12 (9 Jan 2008 05:24:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Jan 2008 05:24:55 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: "Roland Winkler" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 09 06:25:17 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JCTRE-0007B8-IG for ged-emacs-devel@m.gmane.org; Wed, 09 Jan 2008 06:25:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JCTQr-0007Z1-5V for ged-emacs-devel@m.gmane.org; Wed, 09 Jan 2008 00:24:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JCTQm-0007YB-Un for emacs-devel@gnu.org; Wed, 09 Jan 2008 00:24:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JCTQk-0007X2-SZ for emacs-devel@gnu.org; Wed, 09 Jan 2008 00:24:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JCTQk-0007Wz-Jp for emacs-devel@gnu.org; Wed, 09 Jan 2008 00:24:46 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JCTQh-0001Yp-69; Wed, 09 Jan 2008 00:24:43 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAAPpg0fO+IQqdGdsb2JhbACQGwEwmHiBAQ X-IronPort-AV: E=Sophos;i="4.24,260,1196658000"; d="scan'208";a="12448558" Original-Received: from smtp.pppoe.ca ([65.39.196.238]) by ironport2-out.pppoe.ca with ESMTP; 09 Jan 2008 00:24:41 -0500 Original-Received: from pastel.home ([206.248.132.42]) by smtp.pppoe.ca (Internet Mail Server v1.0) with ESMTP id PGH78141; Wed, 09 Jan 2008 00:24:41 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 5BF988231; Wed, 9 Jan 2008 00:24:41 -0500 (EST) In-Reply-To: <18308.10385.319747.688235@tfkp07.physik.uni-erlangen.de> (Roland Winkler's message of "Wed, 9 Jan 2008 02:51:13 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:86621 Archived-At: >> I don't know if anyone has as yet used atomic-change-group. >> I'd be interested to know if it actually works well for you. > While testing various error scenarios in bibtex.el that should be > handled by atomic-change-group, I once got the error message > cancel-change-group: Undoing to some unrelated state > followed by > cancel-change-group: Wrong type argument: listp, t > I wanted to debug this error, but I couldn't reproduce it. > I looked at the code of cancel-change-group. It's not clear to me > what "Undoing to some unrelated state" means. I'd expect that > atomic-change-group should not produce any errors by itself. I guess the message means that cancel-change-group couldn't find the path (through undo entries) going from the current state to the original state. More specifically, it means that the current undo-log does not contains as one of its nthcdr the head of the original undo logs. That might be the case if the changes to undo are too numerous and the undo-log has been truncated to the point where the undo-info needed to revert the change are not present any more. Stefan