From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: (feature request) Shell script within shell script
Date: Sat, 8 Feb 2003 02:31:26 +0000 [thread overview]
Message-ID: <1030208023126.ZM27171@candle.brasslantern.com> (raw)
In-Reply-To: <20030207202324.GA31158@node1.opengeometry.net>
On Feb 7, 3:23pm, William Park wrote:
}
} A classic solution:
}
} function test1 () {
} exec 10<<"EOF"
} ...
} ...
} EOF
} awk -f /dev/fd/10
} exec 10<&-
} }
}
} I didn't have to patch anything. I just have to keep track of fd's
} instead of external files.
Did you actually try that? It certainly doesn't work for me. You
can't use two-or-more-digit numbers to represent FDs for redirection:
zagzig% cat 10<<EOF
heredoc> foo bar
heredoc> EOF
cat: 10: No such file or directory
It works if you change 10 to 9, but it's overkill. All you need is:
awk -f /dev/fd/9 9<<\EOF
...
...
EOF
And if you happen to encounter a command that requires a real seekable
file for its input, you can do this:
awk -f =(<&9) 9<<\EOF
...
...
EOF
However, I'd like to point out that this is not what you originally
asked for. You asked how to create a script, complete with #! line,
and execute it, not how to feed a here-document to a command that
expects a file name.
next prev parent reply other threads:[~2003-02-08 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030128042243.GA3888@node1.opengeometry.net>
[not found] ` <20030128104034.GA6470@node1.opengeometry.net>
[not found] ` <20030131204945.GA1189@node1.opengeometry.net>
2003-02-01 7:36 ` William Park
2003-02-01 15:48 ` Clifford Caoile
2003-02-01 16:56 ` Will Yardley
2003-02-01 17:58 ` Clifford Caoile
2003-02-01 17:04 ` William Park
2003-02-01 19:29 ` Bart Schaefer
2003-02-03 10:31 ` Peter Stephenson
2003-02-03 23:15 ` William Park
2003-02-04 9:18 ` Bart Schaefer
2003-02-04 9:28 ` William Park
2003-02-04 17:24 ` Bart Schaefer
2003-02-04 17:39 ` William Park
2003-02-07 20:23 ` William Park
2003-02-08 2:31 ` Bart Schaefer [this message]
2003-02-08 19:37 ` William Park
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=1030208023126.ZM27171@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).