Date: Sat, 19 Jun 2004 03:43:29 +0200 (CEST)
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Stop printk printing non-printable chars
In-Reply-To: <pan.2004.06.19.01.23.34.471323@smurf.noris.de>
Message-ID: <Pine.LNX.4.56.0406190337110.17899@jjulnx.backbone.dif.dk>
References: <20040618205355.GA5286@newtoncomputing.co.uk>
 <Pine.LNX.4.58.0406181407330.6178@ppc970.osdl.org>
 <Pine.LNX.4.56.0406190032290.17899@jjulnx.backbone.dif.dk>
 <pan.2004.06.19.01.23.34.471323@smurf.noris.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1229
Lines: 34

On Sat, 19 Jun 2004, Matthias Urlichs wrote:

> Hi, Jesper Juhl wrote:
>
> > [ printing control characters as "meaningful" C escapes ]
> > or am I not making sense?
>
> No, you're not. ;-)
>
Ok, I had a feeling that might be so. But I did not intend them to be
printed as '"meaningful" C escapes', I meant "why filter out \v or \f,
someone might find a clever use for them and they do no real harm
otherwhise"...


> Reason: They're not intended to be meaningful. If the kernel prints them,
> the reason isn't that somebody actually used an \a or \v in there, so
> doing that isn't helpful. (Quick, what's the ASCII for \v?)
>
What I meant was not for the kernel to attempt to print something like \a
, but it could be useful for it's original purpose of making a sound.. If
it's simply filtering out what goes to the screen (log, serial line,
whatever), but not preventing other uses, then my comments made no
sense... and 0x0B is \v I believe...


--
Jesper Juhl <juhl-lkml@dif.dk>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/