public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: akikij@free.fr
To: cygwin@cygwin.com
Subject: Can't start a cygwin terminal(mintty) as admin
Date: Tue, 24 Nov 2020 13:51:59 +0100 (CET)	[thread overview]
Message-ID: <159295841.536767529.1606222319350.JavaMail.root@zimbra93-e16.priv.proxad.net> (raw)
In-Reply-To: <938348063.536233005.1606213898648.JavaMail.root@zimbra93-e16.priv.proxad.net>


From some months, use of a terminal with cygwin is changing and changing but for me with more and more difficult to use.

Prior to 3.1 version of the cygwin package, I could use two kinds of terminals bash and mintty.
I like the bash version because I can launch with it an admin session, simply in telling to shortcut "exec as admin".

But with the pty support provided by the new cygwin package, the bash terminal behavior has changed, relatively to Ctrl-C support.

I have a curses application to launch bash scripts applications through a MMI interface presenting several choices of them.

Before 3.1, for mintty and bash terminals, on a ctrl-C, my application MMI and bash script were stopped cleanly.

But now for a bash terminal, a Ctrl-C quits the curses application in leaving the shell script to continue in background.
To day, I don't know how write one C application with ncurses being compatible with bash and mintty terminals as yesterday.

QUESTION 1 : HOW TO NOW HANDLE CTRL-C in a multi threaded cygwin application regarless of terminal

As I am obliged to use mintty, now I can't launch a mintty terminal session as admin, I don't understand why.

QUESTION 2 : HOW TO LAUNCH A MINTTY SESSION AS ADMIN

My questions with last package versions (or not) for cygwin and mintty.

Thanks for your help




       reply	other threads:[~2020-11-24 12:52 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 [this message]
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
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=159295841.536767529.1606222319350.JavaMail.root@zimbra93-e16.priv.proxad.net \
    --to=akikij@free.fr \
    --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).