Xref: utzoo gnu.emacs:343 comp.emacs:5103
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!blake!ogccse!littlei!omepd!mipos3!nate
From: nate@hobbes.intel.com (Nate Hess)
Newsgroups: gnu.emacs,comp.emacs
Subject: Re: Bug (?) in emacs server
Message-ID: <3447@mipos3.intel.com>
Date: 18 Jan 89 16:21:00 GMT
References: <10864@umn-cs.CS.UMN.EDU>
Sender: news@mipos3.intel.com
Reply-To: woodstock@hobbes.intel.com (Nate Hess)
Followup-To: gnu.emacs
Organization: Intel Corporation, Santa Clara, CA
Lines: 13
In-reply-to: randy@umn-cs.CS.UMN.EDU (Randy Orrison)
Posting-Front-End: Gnews 2.0

In article <10864@umn-cs.CS.UMN.EDU>, randy@umn-cs (Randy Orrison) writes:
>the only way I've found to let the client continue on is to exit emacs.

You can always go back to the "Waiting for Emacs..." message and type
'C-c' to kill the emacsclient process -- you don't have to do anything
to the Emacs process.

--woodstock
--
	   "What I like is when you're looking and thinking and looking
	   and thinking...and suddenly you wake up."   - Hobbes

woodstock@hobbes.intel.com   ...!{decwrl|hplabs!oliveb|amd}!intelca!mipos3!nate