All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Alexander E. Patrakov" <patrakov@gmail.com>
Subject: Re: [patch] vt: deactive Shift In/Out in unicode mode
Date: Tue, 20 Apr 2010 16:49:28 -0700	[thread overview]
Message-ID: <4BCE3D88.4010502@zytor.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1004191812570.25222@obet.zrqbmnf.qr>

On 04/19/2010 09:20 AM, Jan Engelhardt wrote:
> 
> On Monday 2010-04-19 16:31, Alan Cox wrote:
>>>
>>> I am proposing the patch below for inclusion.
>>> Also pullable via
>>> 	git://dev.medozas.de/linux siso
>>
>> It seems to do a lot of other things as well. Can you split out just the
>> relevant bit ?
> 
> It's really just the top commit. Perhaps I should rebase it to a
> v2.6.34-rcX tag so that shortlog does what one expects.
> 
> Alexander mentioned:
> 
> [quoting the gmane nntp posting which was stripped of To:s and Cc:s]
>>
>> Since KOI7 is not used by any glibc locale, your use case is now 
>> extinct. I think that, unless someone finds out a different use case, 
>> these SI and SO characters should be deactivated completely (and not 
>> just in unicode mode).
> 
> Alan, do you agree that the entire SI/SO can/should be removed?

VT line drawing characters are generally assumed to be accessible using
SI/SO (as they are by default.)

	-hpa

  reply	other threads:[~2010-04-20 23:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 13:57 [patch] vt: deactive Shift In/Out in unicode mode Jan Engelhardt
2010-04-19 14:29 ` Alexander E. Patrakov
2010-04-20 19:56   ` James Cloos
2010-04-19 14:31 ` Alan Cox
2010-04-19 16:20   ` Jan Engelhardt
2010-04-20 23:49     ` H. Peter Anvin [this message]
2010-04-22  8:39       ` Jan Engelhardt
2010-04-22 13:26         ` H. Peter Anvin

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=4BCE3D88.4010502@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.