🚀 go-pugleaf

I have a weird problem..

I am running epoch and emacsclient. I have defined a function key
to save-all-and-exit sort of thing. This function is as follows..

  (defun save-all-and-exit () (interactive)
    (setq *server-screen* (current-screen))
    (save-buffer t) (kill-buffer (current-buffer)) (server-edit))

I include the kill-buffer so that if I reenter I do not get messages
about whether to start a new buffer and whatnot.

It works fine until I fire up a new screen, edit something and then
exit back to the top level. Any attempt to edit a file, ANY file, 
returns "Selecting deleted buffer" and all grinds to a halt.

My guess is that the screen functions and buffer kill functions
inter-twine in some mysterious fashion, if I just use the first
screen, exit, emacsclient, exit, emacsclient, etc, etc, niet problemski.
If, once a screen is up, I fire up another, lots of problemski.

I need epoch to COMPLETELY forget about a buffer once emacsclient
has performed its final server-edit on that screen.

Any suggestions?
-- 
Lawrence D. Hare        Control Data - Silicon Valley Operations
Consultant              Voice: (408) 496 4339 - C/N [234] 4339
ldh@eagle.svl.cdc.com   Mail: SVLa60  FAX: (408) 496-4106