From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rc funny - still perplexed
Date: Fri, 3 Jan 2003 11:27:23 -0500 [thread overview]
Message-ID: <f9ed6f785fe51ee9d86d66c549f18ba9@plan9.bell-labs.com> (raw)
Perhaps I wasn't clear. It's not just
that EOF2 has to go in the first column.
The here document does not start until all the
braces close.
If you want the second example to print "ls | mc"
rather than run that command, you have to say
{
cat <<'EOF2'
other commands here
}
# here document for cat starts here
ls | mc
EOF2
next reply other threads:[~2003-01-03 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:27 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 16:20 steve.simon
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=f9ed6f785fe51ee9d86d66c549f18ba9@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.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).