New subject: cannot kill last buffer if it is named '*scratch*'

Friday, 13 August 1999

        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&gt; 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 ?! :-) 

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Re: cannot kill last buffer if it is named 'scratch'

Re: cannot kill last buffer if it is named '*scratch*'

Re: cannot kill last buffer if it is named 'scratch'