From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3979 invoked by alias); 2 Jan 2015 02:40:12 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19652 Received: (qmail 29657 invoked from network); 2 Jan 2015 02:39:59 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_sMJRntg/mQtUBxQ2npQPoQ)" X-Authority-Analysis: v=2.1 cv=T/C1EZ6Q c=1 sm=1 tr=0 a=jwg7e+C1pu9G5Tm+CahlKw==:117 a=jwg7e+C1pu9G5Tm+CahlKw==:17 a=Hpgzp-inWqAA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10 a=gZbpxnkM3yUA:10 a=8pif782wAAAA:8 a=12pvGGsp2ZqI4bI9XT4A:9 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=tCv4_bwoTbrp3c5Tb-EA:9 a=GbWSBlWvLcVsKPP8:21 a=_W_S_7VecoQA:10 Message-id: <54A604FB.2020603@eastlink.ca> Date: Thu, 01 Jan 2015 18:39:55 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.3.0 To: Kurtis Rader Cc: Zsh Users Subject: Re: print color escapes References: <54A4DF80.7040206@eastlink.ca> <141231223506.ZM26289@torch.brasslantern.com> <54A59EE5.7000601@eastlink.ca> <150101132931.ZM27115@torch.brasslantern.com> <54A5D21F.1090701@eastlink.ca> In-reply-to: --Boundary_(ID_sMJRntg/mQtUBxQ2npQPoQ) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 01/01/2015 05:21 PM, Kurtis Rader wrote: > > One of those was the DEC VT100. The "language" it recognized > eventually became the winner. Winner in the sense that by the 1990s > nearly all terminals implemented that language. That de-facto standard > was eventually turned into standard ANSI X3.64 > which is now pretty > much the only terminal control language you'll find in use. > I'm just realizing something that might not be true: In the old days, it would have been the hardware terminal itself that interpreted these codes, but now, it's my 'terminal emulator', not the screen itself, which is why it's called an 'emulator'. Correct? And I can't believe I'm saying this, but too bad that these control characters are part of the data stream, there should have been a 'vi' insert vs. control mode. One special char, and you're in control mode until you toggle out of it again. --Boundary_(ID_sMJRntg/mQtUBxQ2npQPoQ)--