--- Begin Message ---
|
Subject: |
kill-buffer gives an error on killing dead buffers |
|
Date: |
Sun, 10 Jun 2012 12:57:49 +0200 |
|
User-agent: |
Gnus/5.130004 (Ma Gnus v0.4) Emacs/23.3 (gnu/linux) |
Hi,
This is a strange behavior which was not happening in previous versions
of emacs. Though quite an unusual use, I decided to report it as it
might be a symptom for a more serious problem.
Create a buffer "test.tmp" and create an indirect buffer:
(with-current-buffer (make-indirect-buffer "test.tmp" "test1")
(add-hook 'kill-buffer-hook
'(lambda ()
(setq kill-buffer-hook nil)
(kill-buffer (buffer-base-buffer)))
t t))
(The above triggers the killing of the base buffer when an indirect
buffer is killed)
Now, kill the base buffer "test.tmp", which raises:
signal(error ("Buffer #<killed buffer> is not a live buffer"))
error("Buffer %s is not a live buffer" #<killed buffer>)
window-normalize-buffer(#<killed buffer>)
replace-buffer-in-windows(#<killed buffer>)
kill-buffer(#<killed buffer>)
(if (and (boundp (quote sub-kill-buffer-and-its-windows))
sub-kill-buffer-and-its-windows (fboundp (quote kill-buffer-and-its-windows)))
(kill-buffer-and-its-windows (current-buffer)) (kill-buffer (current-buffer)))
This doesn't occur when killing an indirect buffer.
Vitalie.
In GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
of 2012-06-08 on lakoocha, modified by Debian
(emacs-snapshot package, version 2:20120608-1~ppa1~precise1)
Windowing system distributor `The X.Org Foundation', version 11.0.11103000
Configured using:
`configure '--build' 'i686-linux-gnu' '--host' 'i686-linux-gnu'
'--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib'
'--localstatedir=/var' '--infodir=/usr/share/info'
'--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs-snapshot:/etc/emacs:/usr/local/share/emacs/24.1.50/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.1.50/site-lisp:/usr/share/emacs/site-lisp'
'--without-compress-info' '--with-crt-dir=/usr/lib/i386-linux-gnu/'
'--with-x=yes' '--with-x-toolkit=gtk3' '--with-imagemagick=yes'
'build_alias=i686-linux-gnu' 'host_alias=i686-linux-gnu'
'CFLAGS=-DDEBIAN -DSITELOAD_PURESIZE_EXTRA=5000 -g -O2' 'LDFLAGS=-g
-Wl,--as-needed -znocombreloc' 'CPPFLAGS=-D_FORTIFY_SOURCE=2''
Important settings:
value of $LANG: en_US.UTF-8
locale-coding-system: utf-8-unix
default enable-multibyte-characters: t
Major mode: Emacs-Lisp
Minor modes in effect:
TeX-PDF-mode: t
highlight-parentheses-mode: t
global-auto-complete-mode: t
auto-complete-mode: t
diff-auto-refine-mode: t
global-auto-revert-mode: t
keyfreq-autosave-mode: t
keyfreq-mode: t
sr-popviewer-mode: t
shell-dirtrack-mode: t
eldoc-mode: t
display-time-mode: t
ido-everywhere: t
show-paren-mode: t
savehist-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
hs-minor-mode: t
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#11665: kill-buffer gives an error on killing dead buffers |
|
Date: |
Mon, 18 Jun 2012 09:24:37 +0200 |
There seem more occasions where this problem could strike. Also, we
should return t when we find out that the buffer name has been reset to
nil under our feet. Patch attached, comments welcome.
Changes applied to trunk, bug closed.
martin
--- End Message ---