This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: console vs ^X
On Sep 29 12:28, Andy Koppe wrote:
> Trying the latest DLL with Corinna's patches (thanks!), I noticed the
> following issue in the console.
>
> With the charset configured to something other than UTF-8, if you
> press a key that isn't in that charset, the console will send a
> ^X-UTF8 sequence. ^X is special to readline though, hence weird
> effects might ensue.
On output? It's just printed to the console so what should happen?!?
> Changing ^X to yet another control character wouldn't help, because
> they all either already have a special meaning or might be assigned
> one by the user or applications.
>
> Therefore, I'd say the console should not be employing the ^X and F0xx
> schemes designed for filenames (but it does need to continue to use
> the charset determined at process startup).
Chicken? Egg?
Typically the console prints the chars it gets via write() and if
the character isn't in the charset, it prints a replacement string
Ctrl-X + all invalid bytes as byte values.
What do you expect it should print?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat