From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47895 invoked by alias); 17 May 2015 07:44:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 47873 invoked by uid 89); 17 May 2015 07:44:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mout.web.de Received: from mout.web.de (HELO mout.web.de) (212.227.15.4) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 17 May 2015 07:44:11 +0000 Received: from MartinsDell ([79.194.119.1]) by smtp.web.de (mrweb001) with ESMTPSA (Nemesis) id 0Lw1CH-1ZFBlL0XYz-017kec for ; Sun, 17 May 2015 09:44:06 +0200 From: "Martin Anantharaman" To: References: <555620B6.3090000@cornell.edu> Subject: AW: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs" Date: Sun, 17 May 2015 08:42:00 -0000 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> X-UI-Out-Filterresults: notjunk:1; X-SW-Source: 2015-05/txt/msg00208.txt.bz2 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