From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Paul Eggert <eggert@CS.UCLA.EDU>, Junio C Hamano <junkio@cox.net>,
Robert Fitzsimons <robfitz@273k.net>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org, Kai Ruemmler <kai.ruemmler@gmx.net>
Subject: Re: [PATCH] Try URI quoting for embedded TAB and LF in pathnames
Date: Wed, 12 Oct 2005 13:21:03 -0700 [thread overview]
Message-ID: <434D702F.4060409@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510121220230.15297@g5.osdl.org>
Linus Torvalds wrote:
>
> Nope. The traditional vt100 escape sequence is "ESC" followed by a
> character to indicate the type of sequence (the most common one is '[').
> That's all 7-bit and fine.
>
> HOWEVER, they made the 8-bit extension be such that any of these vt100
> begin sequences where the second character is in the appropriate range can
> be instead shortened by one character, by instead using a single 8-bit
> character of "0x80+(char-0x40)". Ie the traditional "ESC + '['" (\x1b\x5b)
> can also be written as a single '\x9b' character, aka CSI.
>
> In other words, 0x80-0x9f are _all_ just vt100 shorthand for ESC+'@'
> through ESC+'_'.
>
> (I guess it's not strictly "vt100" any more - it's the extended vt220
> format).
>
Actually, it's even trickier than that.
CSI is character 0x1b of control code set C1; there are two "windows"
for control codes -- CL (0x00-0x1f) and CR (0x80-0x9f). Normally CL is
mapped to C0 and CR is mapped to CL, but ESC will temporarily map C1
into CL.
VT1xx didn't support this since they didn't support 8-bit anything.
Anyway, a *lot* of character sets -- not just UTF-8 -- use the CR range
of bytes for printables.
-hpa
next prev parent reply other threads:[~2005-10-12 20:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 19:35 [RFC] embedded TAB and LF in pathnames Junio C Hamano
2005-10-07 23:29 ` Alex Riesen
2005-10-07 23:44 ` Junio C Hamano
2005-10-08 6:45 ` Alex Riesen
2005-10-08 9:10 ` Junio C Hamano
2005-10-08 13:30 ` [PATCH] Try URI quoting for " Robert Fitzsimons
2005-10-08 18:30 ` Junio C Hamano
2005-10-08 20:19 ` Junio C Hamano
2005-10-11 6:20 ` Paul Eggert
2005-10-11 7:37 ` Junio C Hamano
2005-10-11 15:17 ` Linus Torvalds
2005-10-11 18:03 ` Paul Eggert
2005-10-11 18:37 ` Linus Torvalds
2005-10-11 19:42 ` Paul Eggert
2005-10-11 20:56 ` Linus Torvalds
2005-10-12 6:51 ` Paul Eggert
2005-10-12 14:59 ` Linus Torvalds
2005-10-12 19:07 ` Daniel Barkalow
2005-10-12 19:52 ` Linus Torvalds
2005-10-12 20:21 ` H. Peter Anvin [this message]
[not found] ` <87vf02qy79.fsf@penguin.cs.ucla.edu>
2005-10-12 21:02 ` Junio C Hamano
2005-10-12 21:05 ` Linus Torvalds
2005-10-12 21:09 ` H. Peter Anvin
2005-10-12 21:15 ` Johannes Schindelin
2005-10-12 21:33 ` Junio C Hamano
2005-10-14 0:57 ` Paul Eggert
2005-10-14 5:43 ` Linus Torvalds
2005-10-12 21:24 ` Linus Torvalds
2005-10-14 0:16 ` Paul Eggert
2005-10-14 5:20 ` Linus Torvalds
2005-10-14 17:18 ` H. Peter Anvin
2005-10-14 6:59 ` Junio C Hamano
2005-10-09 10:42 ` Junio C Hamano
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=434D702F.4060409@zytor.com \
--to=hpa@zytor.com \
--cc=barkalow@iabervon.org \
--cc=eggert@CS.UCLA.EDU \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kai.ruemmler@gmx.net \
--cc=raa.lkml@gmail.com \
--cc=robfitz@273k.net \
--cc=torvalds@osdl.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.