From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.8-3
Date: Thu, 16 Feb 2017 20:32:00 -0000 [thread overview]
Message-ID: <bb2239bd-8cc3-2992-1554-18a04736ace7@towo.net> (raw)
In-Reply-To: <20170216124949.GF3889@calimero.vinschen.de>
Am 16.02.2017 um 13:49 schrieb Corinna Vinschen:
> On Feb 15 23:19, Thomas Wolff wrote:
>> Am 14.02.2017 um 21:35 schrieb Thomas Wolff:
>>> Am 14.02.2017 um 21:29 schrieb Thomas Wolff:
>>>> Am 14.02.2017 um 20:56 schrieb Eric Blake:
>>>>> On 02/14/2017 01:40 PM, Thomas Wolff wrote:
>>>>>>> No. We're talking about a function in the master side
>>>>>>> of the tty, while
>>>>>>> the applications started in the terminal are on the slave side.
>>>>>> I am not familiar with the concept of setting termios properties on
>>>>>> either the master or slave side of a pty. I've only ever set
>>>>>> them in the
>>>>>> client application, including my tests about IUTF8 which worked. Would
>>>>>> setting on the master side imply it's set for the clients implicitly,
>>>>>> and can it be changed later, e.g. when mintty character encoding is
>>>>>> being changed from the Options dialog?
>>>>>> And you say the function of erasing characters on BS is in the master
>>>>>> side? To be honest, this confuses me. I thought it's a
>>>>>> client function,
>>>>>> like readline() would perform if used (apparently not by
>>>>>> dash), which is
>>>>>> kind of an enhanced version of the tty cooked mode and used
>>>>>> to work even
>>>>>> without the new flag, right?
>>>>> The readline source code does not mention IUTF8; and neither bash nor
>>>>> dash need to reference it, because if the tty handling code sets it
>>>>> correctly for what the terminal is going to display, then the clients
>>>>> that are read()ing from the tty never even see BS in cooked mode (the
>>>>> master side of the terminal handles BS before the read() completes in
>>>>> the slave, if I'm understanding it correctly).
>>>> This does not comply with my (limited) understanding of pty stuff.
>>>> In mintty, forkpty will create a master/slave pty; mintty feeds it
>>>> on the master side, while the client program (usually a shell) reads
>>>> from the slave side. Mintty never handles BS for input, it simply
>>>> feeds it into the pty. "Line disciplines" like cooked mode must be
>>>> handled on the slave side.
>>> Also, I've tried both options in mintty. Setting the flag on the master
>>> side has weird effects, initially blocking the terminal process.
>>> Setting it on the slave side works fine.
>> That was a mistake (got something wrong when testing). It works from either
>> side alike.
>> I've now patched mintty to keep the flag in sync with the character
>> encoding, including on later changes (from Options menu or by escape
>> sequence).
> There's an ESC sequence to change the codeset? Do you mean the
> alternate codeset sequence \e[10m / \e[11m
Oh, that one! Thanks for mentioning, I had overlooked it and fixed
mintty now to consider it.
> or is there something more sophisticated?
I actually meant to adress
https://github.com/mintty/mintty/wiki/CtrlSeqs#locale and there is also
\e%G and \e%@.
I just notice that later changing of the IUTF8 flag from the master side
does not seem to work on a Window 10 system (although it works
initially) while it does work on a Windows 7 system. Weird.
------
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-02-16 20:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 23:40 Eric Blake (cygwin)
2017-01-24 15:58 ` Houder
2017-01-25 1:28 ` Steven Penny
2017-01-25 13:37 ` Houder
2017-01-25 20:31 ` cyg Simple
2017-01-28 14:36 ` Houder
2017-01-26 0:14 ` Steven Penny
2017-01-28 13:44 ` Houder
2017-01-31 10:04 ` Corinna Vinschen
2017-01-31 13:16 ` Corinna Vinschen
2017-01-31 15:02 ` Houder
2017-01-31 15:33 ` Corinna Vinschen
2017-01-31 15:42 ` Eric Blake
2017-02-01 8:46 ` Houder
2017-01-31 17:54 ` Houder
2017-02-01 9:17 ` Corinna Vinschen
2017-02-13 22:03 ` Thomas Wolff
2017-02-14 8:45 ` Corinna Vinschen
2017-02-14 19:40 ` Thomas Wolff
2017-02-14 19:56 ` Eric Blake
2017-02-14 20:29 ` Thomas Wolff
2017-02-14 20:35 ` Thomas Wolff
2017-02-15 22:19 ` Thomas Wolff
2017-02-16 12:49 ` Corinna Vinschen
2017-02-16 20:32 ` Thomas Wolff [this message]
2017-02-17 7:36 ` Thomas Wolff
2017-02-17 9:43 ` Corinna Vinschen
2017-02-17 22:30 ` Thomas Wolff
2017-02-18 22:46 ` Thomas Wolff
2017-02-20 9:11 ` Corinna Vinschen
2017-02-20 21:08 ` Thomas Wolff
2017-02-20 9:07 ` Corinna Vinschen
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=bb2239bd-8cc3-2992-1554-18a04736ace7@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).