public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Can't start a cygwin terminal(mintty) as admin
Date: Tue, 24 Nov 2020 21:59:05 +0100	[thread overview]
Message-ID: <b5b9d72d-0ebf-82f9-c13f-3b4933ecf0c5@towo.net> (raw)
In-Reply-To: <824848490.1294388.1606249323648@mail.yahoo.com>

Am 24.11.2020 um 21:22 schrieb Kevin Schnitzius via Cygwin:
> On Tuesday, November 24, 2020, 07:52:11 AM EST, akikij@free.fr <akikij@free.fr> wrote:
>
>>   QUESTION 1 : HOW TO NOW HANDLE CTRL-C in a multi threaded cygwin application regarless of terminal
> 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.

>    I use this:
>      D:\cygwin64\bin\mintty.exe -o "KeyFunctions=A+F5:break" -
>
> And use alt-F5 as a break that works on both Cygwin and non-Cygwin processes.
>> QUESTION 2 : HOW TO LAUNCH A MINTTY SESSION AS ADMIN
> cygstart --action=runas mintty.exe
>
> Kevin
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple


  reply	other threads:[~2020-11-24 20:59 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 [this message]
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
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=b5b9d72d-0ebf-82f9-c13f-3b4933ecf0c5@towo.net \
    --to=towo@towo.net \
    --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).