From: Brian Raiter <breadbox@muppetlabs.com>
To: linux-assembly@vger.kernel.org
Subject: Re: bios interuppts
Date: Tue, 4 Mar 2003 12:28:55 -0800 [thread overview]
Message-ID: <15973.3207.212962.958382@eidolon.muppetlabs.com> (raw)
In-Reply-To: <3E64EAB9.5070000@hampshire.edu>
> The simplest way to do it is to use terminal escape codes.
vt100 escape codes aren't guaranteed to work everywhere, though.
If you don't care much about portability, then use the escape codes
that are shared between VT100, ANSI, and xterm. That will probably
work fine 99% of the time, on a Linux machine.
If you don't care at all about portability, then use whatever escape
codes your own particular terminal uses.
If you do care about portability, then use ncurses. Or else don't even
try to draw on the screen. After all, the "screen" might actually be a
TTY (at least in theory).
b
next prev parent reply other threads:[~2003-03-04 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 12:07 bios interuppts Anant Aneja
2003-03-04 16:24 ` hp
2003-03-04 18:04 ` Emanuele Altieri
2003-03-04 20:28 ` Brian Raiter [this message]
2003-03-04 20:34 ` Vince Weaver
2003-03-05 6:55 ` hp
2003-03-05 19:42 ` Brian Raiter
2003-03-05 20:54 ` hp
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=15973.3207.212962.958382@eidolon.muppetlabs.com \
--to=breadbox@muppetlabs.com \
--cc=linux-assembly@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