From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Escape sequences & console
Date: 1 Mar 2001 11:48:39 -0800 [thread overview]
Message-ID: <97m92n$hpm$1@cesium.transmeta.com> (raw)
In-Reply-To: <"3a9e8dcd3b72e6a5@amyris.wanadoo.fr> <Pine.LNX.4.31.0103011919490.23240-100000@phobos.fachschaften.tu-muenchen.de>
Followup to: <Pine.LNX.4.31.0103011919490.23240-100000@phobos.fachschaften.tu-muenchen.de>
By author: Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>
In newsgroup: linux.dev.kernel
>
> On Thu, 1 Mar 2001, Sébastien HINDERER wrote:
>
> > Could someone tell me where I can find a document listing all the
> > escape-sequences that could be sent to the console (/dev/console) and what
> > they do.
>
> Please don't use those sequences directly, as not everyone has
> /dev/console on a vt. You can find the information you want in your local
> terminfo database under "linux".
>
Well, don't use them directly without checking that $TERM is "linux".
Also, normally they should be sent to the current terminal (/dev/tty,
or just stdout) rather than /dev/console.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-03-01 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"3a9e8dcd3b72e6a5@amyris.wanadoo.fr>
2001-03-01 18:21 ` Escape sequences & console Simon Richter
2001-03-01 19:48 ` H. Peter Anvin [this message]
2001-03-01 19:03 Sébastien HINDERER
2001-03-01 20:01 ` Guest section DW
-- strict thread matches above, loose matches on Subject: below --
2001-03-01 20:48 Sébastien HINDERER
2001-03-01 20:10 ` Guest section DW
[not found] <"3a9ea6fa3b646cc9@citronier.wanadoo.fr>
2001-03-02 21:29 ` Simon Richter
2001-03-05 17:20 ` H. Peter Anvin
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='97m92n$hpm$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox