From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
Date: Fri, 15 May 2015 17:27:00 -0000 [thread overview]
Message-ID: <555620B6.3090000@cornell.edu> (raw)
In-Reply-To: <AEA7990E4CC045CDBAC2150A4E05AE19@MartinsDell>
On 5/15/2015 7:22 AM, Martin Anantharaman wrote:
> - Crash in server-mode: One of the advantages of Cygwin emacs-w32 is that it
> supports the server-mode via invocation with --daemon (also coming soon to
> official Emacs!). But using emacsclient wihtout any options first gives an
> error and then crashes emacs-w32. See attachment "emacs-test"
I can't reproduce this. And I'm puzzled by the output:
> $ emacsclient .shrc
> emacsclient: can't find socket; have you started the server?
> To start the server in Emacs, type "M-x server-start".
> Waiting for Emacs...
> *ERROR*: Could not open file: /dev/cons0
On my system if emacsclient can't find the socket (which only happens if
there's no server running), I see the following in a Cygwin Terminal
(mintty):
$ emacsclient-w32 foo
emacsclient-w32: can't find socket; have you started the server?
To start the server in Emacs, type "M-x server-start".
emacsclient-w32: No socket or alternate editor. Please use:
--socket-name
--server-file (or environment variable EMACS_SERVER_FILE)
--alternate-editor (or environment variable ALTERNATE_EDITOR)
I also don't understand why emacsclient would be trying to open
/dev/cons0. Do you by any chance have EMACS_SERVER_FILE set in your
environment to /dev/cons0?
> - Crash in About Emacs: On another machine with (in contrast to my primary
> machine) very lean installation (see attachment 3) emacs-w32 crashes when I
> open the About Emacs page from the Help menu.
I can't reproduce this either. I tried it in a fresh Cygwin install,
just choosing emacs-w32 and its dependencies. I ran 'emacs-w32&' in a
Cygwin Terminal, emacs opened in a new window, and there was no problem
after clicking on "About Emacs".
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
next prev parent reply other threads:[~2015-05-15 16:37 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 [this message]
2015-05-17 8:42 ` AW: " Martin Anantharaman
2015-05-18 3:30 ` 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=555620B6.3090000@cornell.edu \
--to=kbrown@cornell.edu \
--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).