From: Ken Brown <kbrown@cornell.edu>
To: Martin Anantharaman <Martin.Anantharaman@web.de>,
cygwin <cygwin@cygwin.com>
Subject: Re: AW: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
Date: Tue, 19 May 2015 12:53:00 -0000 [thread overview]
Message-ID: <555B2ACA.7010203@cornell.edu> (raw)
In-Reply-To: <39BFBB82ABFA40A3BBE0531B2CDF2906@MartinsDell>
On 5/19/2015 1:52 AM, Martin Anantharaman wrote:
> Ken,
>
> you were on the right track there: I do not run bash in a windows console,
> but not in mintty either - I have been using Console2 for many years as
> common terminal for cmd, msys and cygwin. When I run my test in a mintty
> windows everything works, i.e. emacsclient makes the emacs-server start a
> window on the mintty terminal. /usr/bin/tty there shows /dev/pty0 in
> contrast to /dev/cons0 in the Console2 window. So should I consider use of
> Console2 (and the /dev/cons0 device) unsupported or is it a bug in
> /dev/cons0?
I don't know. Maybe Corinna will have some insight into this when she returns
from vacation.
> Regarding the other problem (crash in About Emacs): There I was running in
> mintty anyway, as I had not installed Cosole2 on that machine at all - I
> will be lookign at that with debugingo in due course.
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-19 12:21 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 ` 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 ` Ken Brown [this message]
2015-05-27 12:00 ` AW: " 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=555B2ACA.7010203@cornell.edu \
--to=kbrown@cornell.edu \
--cc=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).