public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robinow, David" <drobinow@dayton.adroit.com>
To: cygwin@sources.redhat.com
Subject: RE: NTEmacs shell/CygWin: should control-C work?
Date: Fri, 12 Jan 2001 14:31:00 -0000	[thread overview]
Message-ID: <80575AFA5F0DD31197CE00805F650D7602CE54@wilber.adroit.com> (raw)

> From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
> At 04:25 PM 1/12/2001, Ehud Karni wrote:
>>> Do you mean it's a known problem that crops up (for some people), or
that
>>> it simply doesn't work at all (for anyone combining Emacs and CygWin)?
>>I think he meant it is a general problem for everyone. The base of this
>>is that the emacs shell buffer is not a tty. You can check it by doing
>>`stty', you'll get: "stty: standard input: Not a character device".
>>
>>And hence, it is not a tty ==> it will not generate SIGINT for ^C.
>>
>>Ehud.
> Forgive me for coming late to the party.  I didn't digest that this 
> conversation was about NTEmacs (i.e. the Windows port).  I'll leave 
> aside whether or not ^C should work in this context.  I really don't
> know whether it should/would/ever did.  I don't use Emacs.  However, 
> I can say you'll have better luck with a Cygwin version of Emacs, like
> XEmacs.  You'll find Cygwin applications work much better with other 
> Cygwin applications, especially in areas of detail like this.
 Larry has a point.

 NTEmacs:  "stty: standard input: Not a character device"  BREAK does not
work
 XEmacs for NT: "stty: standard input: Not a character device"  BREAK does
not work
 cygwin XEmacs: stty works correctly.   BREAK works.

 Note that results are the same whether typing C-c C-c, selecting BREAK
from the "Signals" menu, or typing M-x comint-interrupt-subjob  (as one 
would expect)

 Setting CYGWIN=TTY does not seem to matter. (Not sure if I tried all
combos)

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2001-01-12 14:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12 14:31 Robinow, David [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-22 10:45 Mike Bresnahan
     [not found] <Daniel>
     [not found] ` <Barclay's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Fri,>
     [not found]         ` <12>
     [not found]           ` <Jan>
     [not found]             ` <2001>
     [not found]               ` <14:46:36>
     [not found]                 ` <-0500>
2001-01-11 14:23                   ` Daniel Barclay
2001-01-11 15:00                     ` David M. Karr
2001-01-12 11:48                       ` Daniel Barclay
2001-01-12 11:54                         ` David M. Karr
2001-01-12 12:30                           ` Larry Hall (RFK Partners, Inc)
2001-01-12 12:43                             ` David M. Karr
2001-01-12 13:12                               ` Daniel Barclay
2001-01-12 13:13                               ` Larry Hall (RFK Partners, Inc)
2001-01-12 13:06                           ` Daniel Barclay
2001-01-12 13:26                         ` Ehud Karni
2001-01-12 13:57                           ` Larry Hall (RFK Partners, Inc)
2001-01-16 11:14                             ` Daniel Barclay
2001-01-16 11:27                               ` Larry Hall (RFK Partners, Inc)
2001-01-18  8:21                                 ` Daniel Barclay
2001-01-18  8:27                                   ` Larry Hall (RFK Partners, Inc)
2001-01-18 16:47                                     ` Dr. Volker Zell
     [not found] <Larry>

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=80575AFA5F0DD31197CE00805F650D7602CE54@wilber.adroit.com \
    --to=drobinow@dayton.adroit.com \
    --cc=cygwin@sources.redhat.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).