From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rc here docs
Date: Sun, 31 Aug 2003 21:05:37 -0400 [thread overview]
Message-ID: <f715870610921193e5a128cc87b5ce58@plan9.bell-labs.com> (raw)
In-Reply-To: <57dbcd0684da6830d1654755467e74ad@sdgm.net>
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
So what's the fix? For that matter, what should the semantics be?
Should it be correct that while scanning a function body, the
action of <<token should be in abeiance? That seems reasonable
to me, but I don't write very complicated shell scripts. Is there
anyone that disagrees?
[-- Attachment #2: Type: message/rfc822, Size: 2065 bytes --]
From: boyd@sdgm.net
To: 9fans@cse.psu.edu
Subject: [9fans] rc here docs
Date: Sun, 31 Aug 2003 20:58:31 -0400
Message-ID: <57dbcd0684da6830d1654755467e74ad@sdgm.net>
this is a a horrible bug:
brahma% fn foo {
cat <<!
echo foo
!
}
!
brahma% whatis foo
fn foo {<<'/tmp/here1aa7.0000' cat;echo foo;! }
brahma% ls -l /tmp
--rw------- M 5073 boyd boyd 0 Aug 31 19:53 /tmp/A6818.boydsam
--rw-r--r-- M 5073 boyd boyd 0 Aug 31 19:27 /tmp/here18cc.0000
brahma% foo
/tmp/here1aa7.0000: rc: can't open: '/tmp/here1aa7.0000' directory entry not found
brahma% date
Sun Aug 31 20:56:57 EDT 2003
next prev parent reply other threads:[~2003-09-01 1:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 0:58 boyd
2003-09-01 1:05 ` David Presotto [this message]
2003-09-01 1:43 ` Scott Schwartz
2003-09-01 3:03 ` boyd, rounin
2003-09-01 3:10 ` Scott Schwartz
2003-09-01 3:14 ` boyd, rounin
2003-09-01 6:48 ` Charles Forsyth
2003-09-01 2:23 ` Geoff Collyer
2003-09-01 2:56 ` boyd, rounin
2003-09-01 3:19 ` Geoff Collyer
2003-09-01 3:33 ` boyd, rounin
2003-09-01 8:36 ` Douglas A. Gwyn
2003-09-01 3:35 ` boyd, rounin
2003-09-01 5:30 ` andrey mirtchovski
2003-09-01 5:36 ` boyd, rounin
2003-09-09 17:12 ` rog
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=f715870610921193e5a128cc87b5ce58@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).