From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] I swear! I rtfm'ed
Date: Thu, 01 Jan 2015 16:03:05 +0100 [thread overview]
Message-ID: <54A561A9.6030808@update.uu.se> (raw)
In-Reply-To: <13336.1420075794@cesium.clock.org>
On 2015-01-01 02:29, Erik E. Fair wrote:
> All those terminal quirks made writing termcap entries challenging
> (I wrote a few), and made the comments in the termcap file interesting
> reading for the frustration and cursing of terminal firmware authors.
> All kinds of history of the evolution of terminals is captured therein.
>
> The removal of the ability to read the source is - IMHO - what
> greatly impeded adoption of the AT&T "termlib" replacement for
> termcap: they stopped distributing the terminal database source
> (they distributed just the binary "compiled" versions), and made it
> harder to write new entries.
I was way to removed from the action to know, but why did people slowly
move over to termlib? Was there really any advantages over termcap?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next prev parent reply other threads:[~2015-01-01 15:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.116.1420056874.3354.tuhs@minnie.tuhs.org>
2014-12-31 23:52 ` Johnny Billquist
2015-01-01 1:29 ` Erik E. Fair
2015-01-01 15:03 ` Johnny Billquist [this message]
2015-01-01 15:59 ` Mary Ann Horton
2015-01-01 20:18 ` Dave Horsfall
2015-01-01 20:11 ` Dave Horsfall
2015-01-01 16:01 ` Clem Cole
2015-01-01 16:11 ` Johnny Billquist
2015-01-01 16:59 ` Clem Cole
2014-12-31 16:25 Noel Chiappa
[not found] <mailman.110.1420006566.3354.tuhs@minnie.tuhs.org>
2014-12-31 10:37 ` Johnny Billquist
2014-12-31 11:13 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 22:56 Jacob Ritorto
2014-12-30 22:59 ` Milo Velimirovic
2014-12-30 23:03 ` Larry McVoy
2014-12-31 0:03 ` Steve Nickolas
2014-12-30 23:05 ` Warren Toomey
2014-12-31 0:01 ` Jacob Ritorto
2014-12-31 2:22 ` Dan Stromberg
2014-12-31 2:33 ` Mary Ann Horton
2014-12-31 5:44 ` Jacob Ritorto
2014-12-31 6:24 ` Dave Horsfall
2014-12-31 6:36 ` Lyndon Nerenberg
2014-12-31 14:58 ` Tim Bradshaw
2014-12-31 15:31 ` arnold
2014-12-31 15:37 ` Milo Velimirovic
2014-12-31 17:37 ` Derrik Walker v2.0
2014-12-31 20:09 ` Larry McVoy
2014-12-31 22:25 ` Jacob Ritorto
2014-12-31 16:11 ` Mary Ann Horton
2014-12-31 20:14 ` Clem Cole
2014-12-31 20:45 ` Erik E. Fair
2014-12-31 21:05 ` Clem Cole
2014-12-31 22:30 ` Jacob Ritorto
2014-12-31 23:06 ` Mary Ann Horton
2014-12-31 23:11 ` Jacob Ritorto
2015-01-01 15:45 ` Clem Cole
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=54A561A9.6030808@update.uu.se \
--to=bqt@update.uu.se \
/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).