From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] getting nroff to underline in v6,v5
Date: Sun, 27 Sep 2015 12:10:02 -0400 [thread overview]
Message-ID: <6179EB54-7939-4C8C-AB68-61A57FF2EB55@ronnatalie.com> (raw)
In-Reply-To: <20150927155118.GC21801@mercury.ccil.org>
And there were a whole slew of filters like nobsp that either stripped out the over(under?)struck characters or reformatted them so it worked on your lineprinter efficently. I remember the lineprinter we had if you fed it line with a backspace it would print the line up to the backspace and then overstrike it going forward. If you had multiple backspaces (like a whole sentene) the thing stuck there just doing the overstrike. It was more efficient to write a filter that changed the _ BS X for each letter to one line of text, a CR (no LF), and then another line of overstrike.
> On Sep 27, 2015, at 11:51 AM, John Cowan <cowan at mercury.ccil.org> wrote:
>
> Mark Longridge scripsit:
>
>> Maybe there was the ability to use overstrike characters on the teletype?
>
> That's inherent in the nature of printing terminals: 'X', BS, '_' worked
> fine on all such terminals to produce an underlined X. Later it was
> found to be better to use '_', BS, 'X', which looked the same on actual
> TTYs or equivalents (LA34/36) and was greatly superior on video terminals.
>
> --
> John Cowan http://www.ccil.org/~cowan cowan at ccil.org
> Any sufficiently-complicated C or Fortran program contains an ad-hoc,
> informally-specified bug-ridden slow implementation of half of Common Lisp.
> --Greenspun's Tenth Rule of Programming (rules 1-9 are unknown)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2015-09-27 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 8:33 Mark Longridge
2015-09-27 15:51 ` John Cowan
2015-09-27 16:10 ` Ronald Natalie [this message]
2015-09-27 23:55 ` scj
2015-09-27 18:00 ` Clem Cole
2015-09-27 18:12 ` Random832
2015-09-27 23:48 Doug McIlroy
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=6179EB54-7939-4C8C-AB68-61A57FF2EB55@ronnatalie.com \
--to=ron@ronnatalie.com \
/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).