public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Fri, 15 May 2020 20:45:30 +0900	[thread overview]
Message-ID: <20200515204530.4301a63ec4fe2e985af63409@nifty.ne.jp> (raw)
In-Reply-To: <CABPLASQTuP+VmaCvCfZOa6=w+CTu5EUAX+rJndJ5-4_SO1sAew@mail.gmail.com>

On Fri, 15 May 2020 11:34:33 +0200
Kacper Michajlow wrote:
> Windows Terminal:
> 
> $ echo $TERM
> xterm-256color
> $ stty
> speed 38400 baud; line = 0;
> eol = M-^?; eol2 = M-^?;
> -brkint -imaxbel iutf8
> -echoe -echok -echoctl -echoke
...
> Mintty:
> 
> $ echo $TERM
> xterm-256color
> $ stty
> speed 38400 baud; line = 0;
> eol = M-^?; eol2 = M-^?;
> -brkint ixany iutf8

Then,
stty echoe echok echoctl echoke
should solve the problem.

This causes because cygwin does not set ECHOE, ECHOK, ECHOCTL and ECHOKE
by default. Mintty sets them by itself. Tcsh seems also to set them.
However, bash does not.

Could someone please tell me whether cygwin should set them by default?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2020-05-15 11:45 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
     [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 [this message]
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=20200515204530.4301a63ec4fe2e985af63409@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).