From: Kacper Michajlow <kasper93@gmail.com>
To: cygwin@cygwin.com
Subject: Re: "tmux open terminal failed: not a terminal" in terminal emulators other than mintty
Date: Fri, 27 Mar 2020 14:27:53 +0100 [thread overview]
Message-ID: <CABPLASTnaENa5stwA12hefbs1wMJ8yF-ca29t+7mjQsj1VY5MA@mail.gmail.com> (raw)
In-Reply-To: <111569852.20200326220436@yandex.ru>
> You can try another pty emulator. F.e. wintty.
Not really interested in some dead projects ;p
Let me rephrase the question, because I misspoke.
Currently Cygwin works acceptably only under Mintty as far as I can see.
Running it from cmd or any of terminal emulators listed before result in
sub-par performance. Even things like Home button to move cursor doesn't
work, as originally stated tmux doesn't work and so on.
Now that Windows is making improvements to their console
https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/
it may be good time to improve Cygwin's compatibility.
Since my first mail I looked at git log and seen pty related changes,
compiled latest Cygwin, but it doesn't work better and even worse, because
mouse stopped working over ssh in tmux.
That said, I guess my really questions are:
1. Is the goal to improve Windows console compatibility?
2. If yes, what is the current status and challenges?
3. And my original question will the tmux work? :)
Projects like Windows Terminal are convenient way to have PS, CMD, Cygwin
and its child MSYS in one window hence I am wondering if it will be
possible without drawbacks.
next prev parent reply other threads:[~2020-03-27 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:52 Kacper Michajlow
2020-03-26 19:04 ` Andrey Repin
2020-03-27 13:27 ` Kacper Michajlow [this message]
2020-03-27 20:15 ` Michael Wild
2020-05-16 19:35 ` Kacper Michajlow
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=CABPLASTnaENa5stwA12hefbs1wMJ8yF-ca29t+7mjQsj1VY5MA@mail.gmail.com \
--to=kasper93@gmail.com \
--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).