From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Console doesn't work correctly under anything else than cmd or mintty
Date: Wed, 13 May 2020 19:34:21 +0900 [thread overview]
Message-ID: <20200513193421.0de070302883f349c14ad5de@nifty.ne.jp> (raw)
In-Reply-To: <CABPLASQ=PJV_tYGvzuHV=-GPMrzfgVSHd+qP+bnkqOn9n8H6Zw@mail.gmail.com>
On Tue, 12 May 2020 22:26:07 +0200
Kacper Michajlow via Cygwin <cygwin@cygwin.com> wrote:
> I was testing latest master (e637d53) and console is clunky in anything
> that isn't cmd.exe or mintty. I tested Microsoft Terminal and ConEmu.
>
> For example navigating with arrows doesn't work in vim. In zsh searching
> history with up arrow when there is beginning of the command doesn't work.
> And so on, sometimes Home button doesn't work to jump to beginning of the
> line or Backspace to clear input.
As for ConEmu, please use cygwin-connector.
https://conemu.github.io/en/CygwinMsysConnector.html
What do you mean by "Microsoft Terminal"? Also, do you use cygwin vim?
If you mean "Windows Terminal" and cygwin vim, I cannot reproduce your
problem. Arrow keys are working correctly in vim with Windows Terminal
as well as with console (command prompt).
> It used to work better. I have tried CYGWIN=disable_pcon but didn't help
> really.
disable_pcon does not affect cygwin console behaviour. It is for pty.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2020-05-13 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 20:26 Kacper Michajlow
2020-05-13 8:50 ` Eric Lilja
2020-05-13 10:34 ` Takashi Yano [this message]
[not found] ` <CABPLASQf4L0WN6wOFd2C6=6ZY1hM9mCL6LaNLsQRa4yGbP6=Mw@mail.gmail.com>
2020-05-14 3:33 ` Takashi Yano
2020-05-14 17:48 ` Kacper Michajlow
2020-05-14 23:47 ` Takashi Yano
2020-05-15 9:34 ` Kacper Michajlow
2020-05-15 11:45 ` Takashi Yano
2020-05-15 15:41 ` Kacper Michajlow
2020-05-15 20:57 ` Brian Inglis
2020-05-16 4:58 ` Takashi Yano
2020-05-16 12:10 ` Brian Inglis
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=20200513193421.0de070302883f349c14ad5de@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).