DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=lFE8oJhSq+CtMLXlBH0Nn3T7928/6wAsm5eXRufaHKI
	99pkFjJOkhArMZy3Fh2TqzVD1vGtU6eDsJ0r4iBVX5RP6Nu+Q+EMTMtalrVwq4uy
	Vf8jBi0Hg7fN0DqmcWBg+D+PTSoB4eoWX+UwgLEi+VYlzW+M+xnygG0ya9nqciM8
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <54D4EB79.3090004@cornell.edu>
Date: Fri, 06 Feb 2015 11:27:37 -0500
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.34-6
References: <1423166859.53474.YahooMailBasic@web120105.mail.ne1.yahoo.com> <20150206103622.GE2635@calimero.vinschen.de>
In-Reply-To: <20150206103622.GE2635@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2/6/2015 5:36 AM, Corinna Vinschen wrote:
> On Feb  5 12:07, gjnospam2014-cygwinproblems@yahoo.com wrote:
>> This update appears to break the no-X emacs daemon.  Specifically, the
>> process seems to hang, gettingas far as displaying
>> "Starting Emacs daemon." but not (visibly) further.  If you start an
>> emacsclient from a different window, it is unable to find/connect to
>> the server.  If you are trying to start the server using
>> $ emacsclient -t --alternate-editor=""
>> then it will just sit there.
>
> I can't reproduce this.  Note that I'm not an emacs user.  What I do:
>
> In one mintty I start emacs and pressed M-x server-start.
>
> In a second mintty I run `emacsclient -t --alternate-editor=""'.  I get
> the typical emacs buffer window.  I can type some text and press C-x 5 0
> and this exits emacs.
>
> Then I run `emacsclient -t --alternate-editor=""' again, and emacs starts
> with a buffer filled with the text I typed in the first client session.
>
> Looks entirely normal to me, as far as I can judge this as emacs noob.
>
>> Reverting to cygwin-1.7.33 "fixes" it.
>
> Ken, can you take a look, perhaps?  I'm just not familiar enough with
> emacs...

I can't reproduce it either.  I think we need more details from the OP, 
including detailed step-by-step instructions, as well as attached cygcheck 
output (http://cygwin.com/problems.html).  It might also be useful to see the 
ACL on the directory /tmp/emacs<uid> that the emacs server uses for its socket. 
  OP, can we see the results of 'ls -l' and 'getfacl' on that directory?  You 
might also try deleting that directory and letting emacs create a new one the 
next time it starts a server.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple