From: Castor Fu <castor@drizzle.Stanford.EDU>
To: john@physiol.su.oz.au (John)
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: How do I reference carriage returns?
Date: Mon, 17 Jan 1994 11:54:08 -0500 [thread overview]
Message-ID: <199401171654.IAA29249@drizzle.Stanford.EDU> (raw)
In-Reply-To: <199401172126.27123.sam.babad@physiol.su.oz.au> from "John" at Jan 17, 94 05:26:51 am
> They work great, inserting themselves when typed, and functioning correctly
> inside commands. (You may have problems _displaying_ these characters,
> since they come down to the font you are using, presumably under X --
> try to use a font which displays control characters somehow.)
>
Of course, once you display them, you can cut and paste them pretty
easily. This is what I usually do.
-castor
next prev parent reply other threads:[~1994-01-17 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-01-17 10:07 Beirne Konarski
1994-01-17 10:26 ` John Mackin
1994-01-17 16:54 ` Castor Fu [this message]
1994-01-18 2:47 Byron Rakitzis
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=199401171654.IAA29249@drizzle.Stanford.EDU \
--to=castor@drizzle.stanford.edu \
--cc=john@physiol.su.oz.au \
--cc=sam-fans@hawkwind.utcs.toronto.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).