Article View: gnu.epoch.misc
Article #1262killing buffers
From: Stacy Marsella
Date: Wed, 24 Jun 1992 22:55
Date: Wed, 24 Jun 1992 22:55
15 lines
1327 bytes
1327 bytes
I have just started using epoch 3.2 and have noticed weird behavior in
some code written by a user here. The code creates a screen and buffer
with the same name. Now if the user does a kill-buffer on that buffer
then bufferp will still return t and that buffer still appears in the
list of buffers. However, set-buffer will return an error ("selected
deleted buffer"). The trouble is that the code uses bufferp to
determine whether or not to (re)-create the buffer before doing the
set-buffer.
Offhand this seems inconsistent, but as I said I just started using
epoch and perhaps this code should not be using bufferp. So,
is there a more appropriate way to handle this test (or alternatively
is this a bug in 3.2 that is fixed in epoch 4.0)
Thanks for any help.
Technical Details
Message-ID:
<Jun.24.18.55.28.1992.7493@dartagnan.rutgers.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!igor.rutgers.edu!dartagnan.rutgers.edu!marsellaShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc7ee,32f226489256259a,start X-Google-Attributes: gidfc7ee,public X-Google-ArrivalTime: 1992-06-24 10:31:12 PST Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!igor.rutgers.edu!dartagnan.rutgers.edu!marsella From: marsella@dartagnan.rutgers.edu (Stacy Marsella) Newsgroups: gnu.epoch.misc Subject: killing buffers Message-ID: <Jun.24.18.55.28.1992.7493@dartagnan.rutgers.edu> Date: 24 Jun 92 22:55:30 GMT Organization: Rutgers Univ., New Brunswick, N.J. Lines: 15