From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] late to the party - Here docs
Date: Thu, 8 Nov 2007 00:24:48 +0100 [thread overview]
Message-ID: <20071107232448.GB866@shodan.homeunix.net> (raw)
In-Reply-To: <77641a070de2f2fa7e7b1adb6cf41014@quanstro.net>
* erik quanstrom (quanstro@quanstro.net) wrote:
> so if i wanted
>
> for(i in 1 2 3){
> cat <<!
> fu
> !
> echo give me a break
> }
>
> what contortions do i need?
>
> - erik
That would be
for(i in 1 2 3){
cat <<!
echo give me a break
}
fu
!
Martin
next prev parent reply other threads:[~2007-11-07 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 20:31 maht-9fans
2007-11-06 21:07 ` erik quanstrom
2007-11-07 16:41 ` dave.l
2007-11-07 20:19 ` erik quanstrom
2007-11-07 21:20 ` geoff
2007-11-07 21:23 ` erik quanstrom
2007-11-07 22:58 ` Martin Neubauer
2007-11-07 23:04 ` erik quanstrom
2007-11-07 23:24 ` Martin Neubauer [this message]
2007-11-08 0:37 ` dave.l
2007-11-08 1:21 ` Gregory Pavelcak
2007-11-06 21:54 ` arisawa
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=20071107232448.GB866@shodan.homeunix.net \
--to=m.ne@gmx.net \
--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).