From: "Martin Anantharaman" <Martin.Anantharaman@web.de>
To: <cygwin@cygwin.com>
Subject: AW: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
Date: Sun, 17 May 2015 08:42:00 -0000 [thread overview]
Message-ID: <8CBDEA451F644AEAAB3A003C80C8AA39@MartinsDell> (raw)
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
next prev parent reply other threads:[~2015-05-17 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 11:36 Martin Anantharaman
2015-05-15 17:27 ` Ken Brown
2015-05-17 8:42 ` Martin Anantharaman [this message]
2015-05-18 3:30 ` AW: " Ken Brown
2015-05-18 9:42 ` Martin Anantharaman
2015-05-18 13:43 ` Ken Brown
2015-05-18 14:48 ` Ken Brown
[not found] ` <39BFBB82ABFA40A3BBE0531B2CDF2906@MartinsDell>
2015-05-19 12:53 ` AW: " Ken Brown
2015-05-27 12:00 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8CBDEA451F644AEAAB3A003C80C8AA39@MartinsDell \
--to=martin.anantharaman@web.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).