From xemacs-m  Wed May 21 11:00:23 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id LAA26606
	for <xemacs-beta@xemacs.org>; Wed, 21 May 1997 11:00:21 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcqmy02198; Wed, 21 May 1997 12:00:23 -0400 (EDT)
Date: Wed, 21 May 1997 12:00:23 -0400 (EDT)
Message-Id: <QQcqmy02198.199705211600@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: [PATCH] 20.3-b1: use of first-change-hook causes buffer change
X-Mailer: VM 6.32 under 20.3 XEmacs Lucid (beta1)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Simple braino on someone's part.  The wrong buffer is recorded,
so the buffer unwind in signal_first_change is a no-op.

Recommended for inclusion in the 19.15 official patches.

Wed May 21 11:58:17 1997  Kyle Jones  <kyle@crystal.wonderworks.com>

	* src/insdel.c (signal_first_change):
          record the current buffer for the unwind instead of the 
          buffer that's about to become the current buffer.


--- 1.1	1997/05/21 15:43:41
+++ src/insdel.c	1997/05/21 15:43:56
@@ -2118,7 +2118,7 @@
 {
   /* This function can GC */
   Lisp_Object buffer;
-  XSETBUFFER (buffer, buf);
+  XSETBUFFER (buffer, current_buffer);
 
   if (!in_first_change)
     {

