🚀 go-pugleaf

Hi,

	I've been using epoch for some time, and using server-mode
	fairly exclusively. However, it has some annoying "features",
	so I was wondering if someone has constructed a _very_
	simplistic client/server mechanism. Basically, I don't care
	about automatic switching to the next client buffer requested;
	one buffer at a time is fine with me, with manual intervention
	required. I also don't care about multiple file editing; when
	I server-edit something, it's always _one_ file.

	For what it's worth, here are the problems that I have found
	with the existing mechanism:

	- You cannot ever kill a buffer, or the server stops working.
	  Killing several buffers (via C-xk, or in Buffer-Menu mode)
	  causes the next emacsclient request to fail with "selecting
	  deleted buffer". Note that the buffers killed have _nothing_
	  to do with the server mechanism; they are simply other files
	  that I have visited via the main emacs, not by using
	  emacsclient.

	- If you <DEL> out of the emacsclient by mistake, the entire
	  server becomes useless.

	- The mechanism does not delete the buffer after it is done;
	  it just buries it. I end up with a slew of buffers that I
	  really don't want anymore, and, because of my first point, I
	  can't kill them.

	There are other problems, but these are the ones that bother
	me the most. My emacs lisp is passable, but I'm not good
	enough to re-implement a simple server/client interface. The
	concept, however, is wonderful, especially in X and epoch.

	There must be an easier way...

	Thanks.
-- 

A#          uunet!sco!asharpe
-----------------------------
Semper Dowland, Semper Dolens