From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31583 invoked by alias); 27 May 2007 02:33:18 -0000 Received: (qmail 31573 invoked by uid 22791); 27 May 2007 02:33:17 -0000 X-Spam-Check-By: sourceware.org Received: from 204-133-123-27.dia.static.slbbi.com (HELO mail.chez-thomas.org) (204.133.123.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 27 May 2007 02:33:15 +0000 Received: by mail.chez-thomas.org (Postfix, from userid 999) id 8D5C819500FE; Sat, 26 May 2007 20:33:13 -0600 (MDT) Received: from [192.168.1.101] (hermes_local [192.168.1.101]) by mail.chez-thomas.org (Postfix) with ESMTP id C3FE61950090; Sat, 26 May 2007 20:33:09 -0600 (MDT) Message-ID: <4658EDE4.1090908@mlbassoc.com> Date: Sun, 27 May 2007 10:12:00 -0000 From: Gary Thomas User-Agent: Thunderbird 1.5.0.10 (X11/20070301) MIME-Version: 1.0 To: Grant Edwards CC: ecos-discuss@sources.redhat.com References: <20070526163810.GA13155@ubuntu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Re: diag_printf refuses to print ANSI escape sequences? X-SW-Source: 2007-05/txt/msg00135.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Grant Edwards wrote: > On 2007-05-26, Sergei Gavrikov wrote: >> On Sat, May 26, 2007 at 03:19:42PM +0000, Grant Edwards wrote: >>> In the "not a big deal" department... >>> >>> I'm trying to send ANSI escape sequences using diag_printf, and >>> diag_printf refuses. If I put the escape character in the format >>> string it says >>> >>> >> FB93FFDC> >>> >>> If there's an escape character in a string that is to be printed using >>> the "%s" format, it says: >>> >>> >>> >>> I understand that it's useful to attempt to avoid printing random >>> binary garbage, but I would think that ASCII ESC might be allowed in >>> strings. >>> >>> I've found that insterting the escape characters using %c works, but >>> that's a bit awkward. >> >> There are nice diag_dump_buf* functions in the eCos infra layer >> (cyg/infra/diag.h). I do use that. > > I'm aware of the daig_dump_buf fuctions, but I don't see how > they solve my problem. AFAIR, they dump out buffer contents in > hex. What I'm trying to do is: > > diag_printf("\033[34mBlue Text \033[31mRed Text \033[mNormal Text\n"); > > diag_printf refuses to do that, so I have to do something like > this instead: > > diag_printf("%c[34mBlue Text %c[31mRed Text %c[mNormal Text\n",033,033,033); > > and that seems awkward to me. > > One could argue that embedding escape seqences in strings is a > bit hackish... > Why not just make a patch that allows for such escape sequences? There's nothing to say that we didn't think of everything some 10 years ago and that today's world could accept some improvements :-) If you're coy about such changes, make it conditional with some CDL, e.g. spelling out what non "printable" characters are allowed, etc. - -- - ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGWO3jmaKbSsQGV8ARAoLkAJ4hxSqYVCLvGv1gST78UKD86dTS1ACfUW+u EmdmXl2naFYXaGXYOKPGHB8= =ZFnw -----END PGP SIGNATURE----- -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss