* bug#4061: marked as done (23.1.50; C-x C-v and saveplace)
2009-08-06 3:29 ` bug#4061: 23.1.50; C-x C-v and saveplace Leo
2009-08-15 20:18 ` Leo
@ 2009-09-05 16:45 ` Emacs bug Tracking System
2009-09-05 16:54 ` Leo
1 sibling, 1 reply; 4+ messages in thread
From: Emacs bug Tracking System @ 2009-09-05 16:45 UTC (permalink / raw)
To: Karl Fogel
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Your message dated Sat, 05 Sep 2009 12:39:02 -0400
with message-id <873a7173dl.fsf@red-bean.com>
and subject line Re: bug#4061: 23.1.50; C-x C-v and saveplace
has caused the Emacs bug report #4061,
regarding 23.1.50; C-x C-v and saveplace
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)
--
4061: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4061
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
[-- Attachment #2: Type: message/rfc822, Size: 2751 bytes --]
From: Leo <sdl.web@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.1.50; C-x C-v and saveplace
Date: Thu, 06 Aug 2009 04:29:21 +0100
Message-ID: <m0zlady60e.fsf@cam.ac.uk>
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
With saveplace enabled, it will be nice if place (point) can survive C-x
C-v. At the moment, C-x C-v will move the point to a 'random' place.
Leo
[-- Attachment #3: Type: message/rfc822, Size: 2898 bytes --]
From: Karl Fogel <kfogel@red-bean.com>
To: 4061-done@emacsbugs.donarmstrong.com
Cc: Leo <sdl.web@gmail.com>
Subject: Re: bug#4061: 23.1.50; C-x C-v and saveplace
Date: Sat, 05 Sep 2009 12:39:02 -0400
Message-ID: <873a7173dl.fsf@red-bean.com>
Okay, this is fixed now:
$ cat log-message.txt
* lisp/files.el (find-alternate-file): Run `kill-buffer-hook' manually
before killing the old buffer, since by the time `kill-buffer' is
run so many buffer variables have been set to nil that it may not
behave as expected. (Bug#4061)
$ cvs ci -F log-message.txt files.el ChangeLog
/sources/emacs/emacs/lisp/files.el,v <-- files.el
new revision: 1.1078; previous revision: 1.1077
/sources/emacs/emacs/lisp/ChangeLog,v <-- ChangeLog
new revision: 1.16100; previous revision: 1.16099
Mailing notification to emacs-diffs@gnu.org... sent.
$
Leo, please test if you get a chance and let us know if you run into any
problems.
Notes on closing:
I'm closing this report now by sending this mail to 4061-done@, as
documented on http://emacsbugs.donarmstrong.com/Developer#closing. I'm
not positive that's the Right Way to do it, but since much of the
documentation is still written in terms of Debian GNU/Linux instead of
Emacs, and http://emacsbugs.donarmstrong.com/server-control#fixed
doesn't clarify either (for example, what should the "version" be? The
version the bug was reported against, or the version the fix is likely
to be be released in?), this is as good a guess as any. If someone
knows the Right Way, please tell me, or better yet, document it where
developers are likely to find it.
-Karl
^ permalink raw reply [flat|nested] 4+ messages in thread