Thread View: gnu.epoch.misc
1 messages
1 total messages
Started by Stacy Marsella
Wed, 24 Jun 1992 22:55
killing buffers
Author: 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.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads