Re: cannot kill last buffer if it is named '*scratch*'
This has nothing to do with the buffer name. The beep is coming from
the new gutter code. The particular place you bombed doesn't do any
bounds checking so it should do the same thing with any last buffer
regardless of the name.
Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org:
wmperry(a)aventail.com (William M. Perry) wrote:
> Bleeeeep!
> [...] (setq fuckme buffers) [...]
I have no idea where this code is from.
Waddya expect anyway ?! :-)