🚀 go-pugleaf

I order to speedup epoch start times, I have been trying to use
emacsclient to open extra epoch screens. In general this seems
to work quite well but there are some "nuisance" level problems.

 1) I want the screen to have the name of the file being edited
    at the top. With emacsclient, it always says "Server Screen".
    I modified server.el and fixed this. However,if I load a
    different file into that screen ( C-X C-F) the screen name
    changes just fine but now emacsclient no longer recognizes
    the completion of things when server-edit is done. No doubt
    due to it looking for the screen name. My "work-around"
    is simple but seems a bit kludgy -- just have emacsclient
    terminate immediately rather than sit around waiting to post
    any messages from epoch. Except for the occassional weirdness
    of having elm think the editor has finished before the server
    screen ever manages to appear all seems to work OK. Am I
    missing any reaally vital messages by this kludge? 
 2) When running from several machines using a shared NFS base
    I can't run emacsclient on the second machine if it is running
    on another one. This seems to be due to the .emacs_server
    inter-process file in my home directory. I have changed
    emacsclient, server, and server.el to append the host name
    to the file name as a workaround. This seems to cure the
    problem. 
--
Richard R. Ragan   rrr@svl.cdc.com    (408) 496-4340 
Control Data Corporation - Silicon Valley Operations
5101 Patrick Henry Drive, Santa Clara, CA 95054-1111