DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:subject:date:message-id
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=ygMAXXv/oDEAL9upcHQKQNB9SPx88T
	6nsP2/KTDo+5KZH+qVrh8oDBCxeLwCta8bFJLupbFVtErEIeyhROAUeaxPjHK7cd
	0q7XRoLMFiEmp0emXHU1j9g3nJsx3LtZ+64IR8LRJFWH8locrn91O+2M3j7zQbQr
	OEUGHT/FMzs8g=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: "Martin Anantharaman" <Martin DOT Anantharaman AT web DOT de>
To: <cygwin AT cygwin DOT com>
References: <555620B6 DOT 3090000 AT cornell DOT edu>
Subject: AW: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
Date: Sun, 17 May 2015 09:44:04 +0200
Message-ID: <8CBDEA451F644AEAAB3A003C80C8AA39@MartinsDell>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <555620B6.3090000@cornell.edu>

Ken,

thanks for your quick reply. Regarding the problem with emacs --daemon I
should have given the following background:
1) The commands in my listing (it was actually an attached text-file - which
automagically got inlined into the posting) need to be executed in that
sequence, i.e. emacs --daemon needs to be executed before executing
emacsclient - then emacsclient connects to the emacs-server and does not
give the error you got. IFF the environment-variable ALTERNATE_EDITOR is set
but empty (="") then one can actually omit the call to emacs --daemon as
emacsclient does it on its own. This IMHO is the best usage-pattern: Always
call emacsclient which starts emacs (with --daemon) on its own if necessary.
2) I use the setting (server-use-tcp t) in my .emacs init-file to switch
from the default socket connection-method to TCP - which allows the official
emacsclient (which cannot use local sockets due to MinGW limitations) to
connect as well. On the other hand emacsclient still seems to default to the
socket-connection, so it gives an error-message "emacsclient: can't find
socket; have you started the server? ..." - but then connect via TCP anyway.
So without this setting (the default) that particular error-message would
not appear.

Can you re-produce the error now? My suspicion is that since emacs --daemon
right after start-up does not have any open frame, so when called by
emacsclient (without the -c option which creates a new frame) it tries to
open a window on a console-terminal - which it does not have.

Regarding the crash in About Emacs on the second machine I did a clean
re-install but get the same error - so it could be specific to the Windows
XP (yes, I am ashamed to admit it) configuration on that machine. How could
I go about analyzing this, maybe using the stackdump and/or debuginfo?

Regards, Martin


--
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