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: Sat, 28 Nov 2020 05:28:51 +0100 [thread overview]
Message-ID: <31fc690d-a847-fec8-4c26-f57ba46dd2e1@towo.net> (raw)
In-Reply-To: <55810709.2094334.1606533196052@mail.yahoo.com>
Am 28.11.2020 um 04:13 schrieb Kevin Schnitzius:
> On Wednesday, November 25, 2020, 03:44:30 AM EST, Thomas Wolff
> <towo@towo.net> wrote:
>
> >> 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.
>
> Oops, it's been a while since I looked into it.
>
> D:\cygwin64\bin\mintty.exe -o "KeyFunctions=C+c:break"
> Shift+Ctrl+c does not produce a break for Cygwin or non-Cygwin processes
>
Works for me. Your child process may have disabled the SIGINT signal.
> mintty -o "KeyFunctions=c:break" -o CtrlExchangeShift=true
> Actually, this restores the old behavior of Ctrl+c actually doing a
> break for Cygwin and non-Cygwin processes.
>
> Kevin
>
>
next prev parent reply other threads:[~2020-11-28 4:28 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
2020-11-28 3:13 ` Kevin Schnitzius
2020-11-28 4:28 ` Thomas Wolff [this message]
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=31fc690d-a847-fec8-4c26-f57ba46dd2e1@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).