From: Willy Tarreau <w@1wt.eu>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [2.6 patch] UTF-8 fixes in comments
Date: Tue, 29 Apr 2008 22:05:05 +0200 [thread overview]
Message-ID: <20080429200505.GA15596@1wt.eu> (raw)
In-Reply-To: <48177775.4000306@kernel.org>
On Tue, Apr 29, 2008 at 12:31:01PM -0700, H. Peter Anvin wrote:
> Willy Tarreau wrote:
> >
> >Well, I accidentally used a freshly installed laptop running mandriva 2008.
> >I was typing in a terminal inside KDE (I don't know the program name, sort
> >of an xterm, but with huge borders all around). I made a typo in a word and
> >typed in a "é" (e acute). Pressing backspace to fix it showed me that I
> >remove more chars than typed. I tried again. Pressing this letter 5 times,
> >then 10 times backspace. I removed 5 chars from the prompt. I suspect that
> >if I had used some chars with wider encoding (eg 4 bytes), I could have
> >removed as many... Clearly those tools are not ready.
> >
>
> Presumably, this was konsole.
Possible. It was the one you get by clicking on a terminal icon.
Huuhhh what an horror, I'm discussing icons and GUIs on LKML. I must
take my meds :-)
> konsole works fine with UTF-8 (I use it
> that way every day); the most common cause of this kind of problems is
> people explicitly clobbering the locale or charset class defaults in
> their login scripts.
I really doubt the miss would have done this. Or someone would have done
it for her which I really doubt in such a small time frame after a fresh
install from the day before. I will investigate though.
Willy
next prev parent reply other threads:[~2008-04-29 20:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 15:40 [2.6 patch] UTF-8 fixes in comments Adrian Bunk
2008-04-28 23:05 ` Willy Tarreau
2008-04-29 1:29 ` H. Peter Anvin
2008-04-29 5:06 ` Willy Tarreau
2008-04-29 6:04 ` H. Peter Anvin
2008-04-29 7:29 ` Adrian Bunk
2008-04-29 8:14 ` Willy Tarreau
2008-04-29 9:06 ` Helge Hafting
2008-04-29 9:33 ` Alan Cox
2008-04-29 10:09 ` Willy Tarreau
2008-04-29 10:10 ` Alan Cox
2008-04-29 10:33 ` Willy Tarreau
2008-04-29 10:34 ` Alan Cox
2008-04-29 22:12 ` Willy Tarreau
2008-04-29 22:15 ` Alan Cox
2008-04-29 23:05 ` Willy Tarreau
2008-05-01 20:18 ` H. Peter Anvin
2008-05-01 9:46 ` Alexander E. Patrakov
2008-04-29 19:33 ` H. Peter Anvin
2008-04-29 10:42 ` Adrian Bunk
2008-04-29 11:06 ` Willy Tarreau
2008-04-29 11:27 ` Adrian Bunk
2008-04-29 11:32 ` Adrian Bunk
2008-04-29 20:18 ` Jeremy Fitzhardinge
2008-04-30 9:15 ` Helge Hafting
2008-04-30 19:22 ` Adrian Bunk
2008-04-30 19:42 ` H. Peter Anvin
2008-04-29 9:43 ` Adrian Bunk
2008-04-29 19:31 ` H. Peter Anvin
2008-04-29 20:05 ` Willy Tarreau [this message]
2008-04-29 20:09 ` H. Peter Anvin
2008-05-09 12:48 ` David Kågedal
2008-04-29 9:01 ` Alan Cox
2008-04-29 9:19 ` Jan Engelhardt
2008-04-29 9:34 ` Willy Tarreau
2008-04-29 9:41 ` Alan Cox
2008-04-29 12:18 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2008-04-30 0:08 Samuel Thibault
2008-04-30 3:38 ` Chris Adams
2008-04-30 9:38 ` Samuel Thibault
2008-04-30 19:45 ` Willy Tarreau
2008-04-30 19:49 ` Willy Tarreau
2008-05-03 23:50 ` Samuel Thibault
2008-05-04 8:55 ` Willy Tarreau
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=20080429200505.GA15596@1wt.eu \
--to=w@1wt.eu \
--cc=bunk@kernel.org \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 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.