From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vt
Date: Mon, 9 Apr 2001 15:34:26 +0000 [thread overview]
Message-ID: <3AD1CFF0.D62827D@arl.army.mil> (raw)
In-Reply-To: <20010409090719.A8A2419A03@mail.cse.psu.edu>
Russ Cox wrote:
> i'm scared.
Well, I did forget to set the initial tab stops (fixed in the version
I sent to Dave), which was a different form of a bug in the base code.
Otherwise, why be scared? It'll all described in the manuals,
especially the VT100 Technical Manual, except for a handful of
corrections that I penciled into my copy of the manuals over the
decades.
next prev parent reply other threads:[~2001-04-09 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 9:07 Russ Cox
2001-04-09 15:34 ` Douglas A. Gwyn [this message]
2001-04-10 9:00 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 15:49 forsyth
2001-04-18 14:06 ` David Lukes
2001-04-18 18:55 ` Boyd Roberts
2001-04-07 1:22 presotto
2001-04-09 8:36 ` Boyd Roberts
2001-04-09 15:22 ` Douglas A. Gwyn
2001-04-10 8:59 ` Boyd Roberts
2001-04-06 17:04 presotto
2001-04-09 8:36 ` Douglas A. Gwyn
2001-04-04 6:08 Micah Stetson
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=3AD1CFF0.D62827D@arl.army.mil \
--to=gwyn@arl.army.mil \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).