Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site hadron.UUCP
Path: utzoo!linus!decvax!decwrl!pyramid!ut-sally!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: An oldie and a newie.
Message-ID: <149@hadron.UUCP>
Date: Sun, 29-Dec-85 15:22:06 EST
Article-I.D.: hadron.149
Posted: Sun Dec 29 15:22:06 1985
Date-Received: Tue, 31-Dec-85 01:00:15 EST
References: <525@smeagol.UUCP> <156@vcvax1.UUCP> <530@smeagol.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Distribution: net
Organization: Hadron, Inc., Fairfax, VA
Lines: 24

In article <530@smeagol.UUCP> kwan@smeagol.UUCP (Richard Kwan) writes:
>>In <525@smeagol.UUCP>, Greg Earle writes:
>>> So, how do you get
>>> "\n"s into an [nt]roff document without them being interpreted?
>In <156@vcvax1.UUCP>, paul@vcvax1 response:
>> The way to get a `\' in the output is to use a `\e' in the input.
>> So use `\en' to get `\n'.
>Allow me to play dumb for a moment... (cause on this one, I really
>am.)  All these responses seem to focus on useing "\e" to get a
>literal "\".
>3.  What is the recommended way to include source code into a
>    document?

The problem is that all too often text which you think is just going
to go in and come out actually gets caught in a diversion and re-
processed elsewhere and elsewhen.  This was the problem with the old
solution of multiple escape chars: how many escapes escape an escape?
Similarly, how many levels of .eo<NL>\.eo<NL> should we use?

I believe there's a way to include something at the last minute (after
most all processing's done), but it escapes me at the moment ...
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}