From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Paul LeoNerd Evans <leonerd@leonerd.org.uk>
Subject: Re: [PATCH] vt: Do not clear UTF when resetting console
Date: Tue, 03 Apr 2007 08:53:32 +0800 [thread overview]
Message-ID: <1175561612.7267.22.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.61.0704030220140.18387@yvahk01.tjqt.qr>
On Tue, 2007-04-03 at 02:23 +0200, Jan Engelhardt wrote:
> On Apr 3 2007 08:16, Antonino A. Daplas wrote:
> >
> >That would be the cleanest and purest behavior. But it's possible to set
> >one console to UTF-8 and another to legacy mode.
>
> The question would be: why would you want to have mixed consoles?
> Switching to UTF8 IMO does not take away any characters, and I mean
> no-framebuffer 80x25 that is limited to 256 glyphs.
As long as we provide the users the capability to support mixed
encodings, the why is not important, it will happen. If we want to be
more restrictive, I guess, we can remove support for
echo -e '\033%G' and '\033%@'
Tony
next prev parent reply other threads:[~2007-04-03 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:13 [PATCH] vt: Do not clear UTF when resetting console Antonino A. Daplas
2007-04-02 17:35 ` H. Peter Anvin
2007-04-03 0:16 ` Antonino A. Daplas
2007-04-03 0:23 ` Jan Engelhardt
2007-04-03 0:53 ` Antonino A. Daplas [this message]
2007-04-03 0:55 ` H. Peter Anvin
2007-04-03 21:14 ` Paul LeoNerd Evans
2007-04-02 19:10 ` Jan Engelhardt
2007-04-03 0:16 ` Antonino A. Daplas
2007-04-03 11:41 ` Martin Mares
2007-04-03 14:51 ` Paul LeoNerd Evans
2007-04-03 15:37 ` Martin Mares
2007-04-04 5:42 ` Antonino A. Daplas
2007-04-04 8:12 ` Jan Engelhardt
2007-04-04 8:26 ` Paul LeoNerd Evans
2007-04-04 16:53 ` Martin Mares
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=1175561612.7267.22.camel@daplas \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=leonerd@leonerd.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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