public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: Kevin Schnitzius <kometes@yahoo.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Can't start a cygwin terminal(mintty) as admin
Date: Wed, 25 Nov 2020 09:44:26 +0100	[thread overview]
Message-ID: <39ef00f6-fcd9-8aaa-4fa1-1d7720b06910@towo.net> (raw)
In-Reply-To: <1940447422.1428712.1606290212521@mail.yahoo.com>



Am 25.11.2020 um 08:43 schrieb Kevin Schnitzius:
> On Tuesday, November 24, 2020, 03:59:19 PM EST, Thomas Wolff 
> <towo@towo.net> wrote:
>
> Am 24.11.2020 um 21:22 schrieb Kevin Schnitzius via Cygwin:
> >> Ctrl-c is broken on mintty.
> > This is a wrong statement. For a terminal, Ctrl+c is just a control
> > character, nothing else. It's the pty device, shell or application that
> > may, or may not, associate it with specific handling like interruption.
>
> D:\cygwin64\bin\mintty.exe -o "KeyFunctions=A+F5:break" -
> alt-F5 is a break that works on both Cygwin and non-Cygwin processes.
>
> D:\cygwin64\bin\mintty.exe -o "KeyFunctions=C+c:break" -
> Ctrl-c is a break that works on Cygwin processes only.
That configuration would assign the break function to Shift+Ctrl+c, not 
just Ctrl+c, so with Ctrl+c you still just send a ^C character while in 
the other case mintty would invoke a BRK signal. So try Shift+Ctrl+c.

>
> This C+c used to work in both cases...  I think we've been over this 
> before and
> the problem very well may be in the pty break handling.
>
> Kevin
>


  reply	other threads:[~2020-11-25  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <938348063.536233005.1606213898648.JavaMail.root@zimbra93-e16.priv.proxad.net>
2020-11-24 12:51 ` akikij
2020-11-24 20:22   ` Kevin Schnitzius
2020-11-24 20:59     ` Thomas Wolff
2020-11-25  7:43       ` Kevin Schnitzius
2020-11-25  8:44         ` Thomas Wolff [this message]
2020-11-28  3:13           ` Kevin Schnitzius
2020-11-28  4:28             ` Thomas Wolff
2020-11-24 23:17   ` Takashi Yano

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=39ef00f6-fcd9-8aaa-4fa1-1d7720b06910@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    --cc=kometes@yahoo.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).