Path: utzoo!mnetor!uunet!lll-winken!netsys!ames!pasteur!ucbvax!ICST-CMR.ARPA!rbj
From: rbj@ICST-CMR.ARPA (Root Boy Jim)
Newsgroups: comp.emacs
Subject: Need Info: Server Mode
Message-ID: <8803182102.AA07523@icst-cmr.arpa>
Date: 18 Mar 88 21:02:26 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23


   Why so much work?  Why doesn't emacsclient write its message and
   then SIGCONT the stopped emacs, which then would discover a message
   on the socket and read "keystrokes" from the socket rather than
   stdin and either display directly (modulo tostop) or send the
   display to emacsclient (which could just "cat" it)?  It'd certainly
   be easier for the user than having to ^Z/fg all over the place, and
   it doesn't sound all that difficult to write.  (Okay, maybe you
   can't get away with it -- but I'm fairly certain I could use a
   "permanently" backgrounded emacs with message queues under System V
   to do it.)  --

Because that's not how it was designed to work. The emacs server may
already be running in another window. In this case, the `window' exists
in time rather than in space. Anyway, how would the server know how to
get back to the client? You'd only have solved half the problem.

		 Brandon S. Allbery, moderator of comp.sources.misc
	  {well!hoptoad,uunet!hnsurg3,cbosgd,sun!mandrill}!ncoast!allbery

	(Root Boy) Jim Cottrell	<rbj@icst-cmr.arpa>
	National Bureau of Standards
	Flamer's Hotline: (301) 975-5688
	--- I have seen the FUN ---