From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: interpreting ^Hs in text files
Date: 20 Jan 2003 08:50:34 +0100 [thread overview]
Message-ID: <m3znpyg6s9.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: 20030116143715532-0500@news.rcn.com
>>>>> "Dan" == Dan Kalikow <DrDan@Kalikow.com> writes:
Dan> E.g., to print and underscore the word "the" the sequence of
Dan> characters transmitted would be the^H^H^H___ where ^H was
Dan> ctrl-H.
This would result in "___" being displayed on a dumber CRT terminal.
So, most people would rather do it with "___^H^H^Hthe", which is more
fault-proof. :)
Dan> It could also be used to strike through or
Dan> obliterate a previously-typed letter. It survived in that
Dan> mode for awhile as "glass TTYs" supplanted paper terminals,
Dan> but gradually fell into disuse in that mode.
And some smarter CRT terminals actually emulated those effects to some
extent.
Dan> Nowadays, I normally see such ^H stuff used as a "figure of
Dan> net-speech" like this -- ===== Microsoft Windows is the most
Dan> excellent^H^H^H^H^H^Hinsidious operating system known to
Dan> exist today. ===== HTH^H^H^HI don't care if this helps or
Dan> not to tell you the truth :-)
But that's not a real Control-H. It's 2 characters: ^ and H. Anyway,
that's the convention to represent a Control-H with visible
characters. How many people can still appreciate those uses of ^ and
H?
--
Lee Sau Dan 李守敦(Big5) ~{@nJX6X~}(HZ)
E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee
next prev parent reply other threads:[~2003-01-20 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 15:22 interpreting ^Hs in text files Maciej Kalisiak
2003-01-16 15:43 ` David Kastrup
2003-01-17 18:39 ` Maciej Kalisiak
2003-01-17 19:37 ` Alan Shutko
2003-01-17 19:41 ` Henrik Enberg
2003-01-16 19:37 ` Dan Kalikow
2003-01-20 7:50 ` Lee Sau Dan [this message]
2003-01-16 19:58 ` Kai Großjohann
2003-01-20 7:50 ` Lee Sau Dan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3znpyg6s9.fsf@mika.informatik.uni-freiburg.de \
--to=danlee@informatik.uni-freiburg.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).