From: John (Most modern computers would break if you stood on them) Mackin <john@ civil.su.oz.au>
To: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: varaiable expansion and here documents
Date: Mon, 18 Jan 1993 21:57:45 -0500 [thread overview]
Message-ID: <199301191357.1902.rc.bafok@civil.su.oz.au> (raw)
In-Reply-To: <9301180723.AA13510@utopia.mv.us.adobe.com>
these rules are simple. let's not confuse matters by allowing
arbitrary expression syntax to heredocs.
I agree 100% with Paul. It's not necessary and would just be
a feeping creature.
OK,
John.
next prev parent reply other threads:[~1993-01-19 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-01-18 7:23 Paul Haahr
1993-01-19 2:57 ` John Mackin [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-01-18 16:33 Byron Rakitzis
1993-01-18 6:47 Scott Merrilees
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=199301191357.1902.rc.bafok@civil.su.oz.au \
--to=john@civil.su.oz.au \
--cc=rc@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).