From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.8-3
Date: Sat, 18 Feb 2017 22:46:00 -0000 [thread overview]
Message-ID: <eae638e5-efec-fdd8-c690-dc16f777f409@towo.net> (raw)
In-Reply-To: <6bac1397-8542-8283-5146-4dffcce7c905@towo.net>
Am 17.02.2017 um 23:29 schrieb Thomas Wolff:
> Am 17.02.2017 um 10:43 schrieb Corinna Vinschen:
>> On Feb 17 08:36, Thomas Wolff wrote:
>>> Am 16.02.2017 um 21:32 schrieb Thomas Wolff:
>>>> Am 16.02.2017 um 13:49 schrieb Corinna Vinschen:
>>>>> 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.
>>> Now tested on 2 Windows 7 systems and 2 Windows 10 systems. Does not
>>> work on Windows 10.
>>> Any idea?
Actually, I'm not sure but I think this problem only occurs if mintty is
started in a non-UTF-8 locale.
If it's started in UTF-8, later switching seems to work.
The strace shows that errno is set to 88 ENOSYS at some place (but I
don't know where).
>> Whatever you're observing, there's nothing Windows version-specific
>> here. The tcsetattr function indiscriminately copies the incoming
>> termios structure over. Maybe the bg_check function fails for some
>> reason? Can you strace setting the flag via tcsetattr?
> Attached. There are lots of strace output even without interaction.
> I've tried to isolate the switching moment tightly.
>> There should be some output from tcsetattr as well as from
>> fhandler_termios::bg_check.
>>
>> Can you check?
> You mean the termios_printf trace? How would I activate it (without
> recompiling cygwin)?
------
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-18 22:46 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
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 [this message]
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=eae638e5-efec-fdd8-c690-dc16f777f409@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).