🚀 go-pugleaf

I have a few Epoch questions that I've been saving up. We're using Epoch
3.2 on Sun 3s and Sun 4s. 

* I have been using the `set-window-buffer-hook' to keep the X window names in
sync with the buffer currently displayed in the screen.  I haven't had any
problems with this, but a comment in the source calls it "undocumented" and
"dangerous".  Is there a better way to accomplish this without using the
`set-window-buffer-hook' (or rebinding every command that could possibly
change the buffer being displayed in a screen)?

* Has anyone experimented with or even thought about what would be involved in
supporting "cut and paste" for buttons.  That is, allowing a region with
buttons to killed, and then restoring the buttons when it's yanked into 
another location.

* If I make a selection using the mouse, then move the cursor forward a few
positions with C-f, mouse events seem to be blocked until I do a C-n or C-b
to get the cursor out of the selection.  Has anyone else noticed this
behavior?

* Is there anyway to disable the mouse, while I'm prompting the user for
a response in the minibuffer?  Right now, it seems that a mouse click on a
screen makes Epoch forget about the read-string function that is
executing.

* Is there a simple way to setup a screen so that only the buffer
originally passed to create-screen can be displayed in it (with exceptions
for *Help*, etc.) In other words, I want to tie a screen and a buffer
together until the screen is removed.

Any help would be appreciated. Thanks,

-Mike Sennett
sennett@vistatech.com