From: "Clifford Caoile" <piyokun@email.com>
To: <zsh-users@sunsite.dk>
Subject: RE: (feature request) Shell script within shell script
Date: Sun, 2 Feb 2003 02:58:54 +0900 [thread overview]
Message-ID: <BBEKIEKOHGEFJBFLEENGCEFFCGAA.piyokun@email.com> (raw)
In-Reply-To: <20030201165641.GB13822@hq.newdream.net>
Quotes... mmm zsh-goodness... Thanks for the heads up I didn't know that.
,-~-.
< ^ ; ~, Clifford Escobar CAOILE (aka "Piyo-kun")
(_ _,
J~~> _.___...:.__..__.: __.:_. .:_.__::_..:._::._... _____ p(^_^)q
| -----Original Message-----
| From: Will Yardley [mailto:william@hq.dreamhost.com]
| Sent: Sunday, February 02, 2003 01:57
| To: zsh-users@sunsite.dk
| Subject: Re: (feature request) Shell script within shell script
|
|
| On Sun, Feb 02, 2003 at 12:48:01AM +0900, Clifford Caoile wrote:
|
| > I am not an expert, but I was exploring here documents in bash
| and zsh just
| > this last week. Let me see if I get this right:
| >
| > In zsh-4.0.x, you can use "here documents" or "here-strings". A here
| > document has this syntax (note there is no double quotations necessary):
| >
| > >> /etc/hosts <<EOF
| > 192.168.0.26 mynewcomputer.zsh.org
| > EOF
| >
| > This adds the line to the /etc/hosts file. The cat command is implicit.
| > (It's still a useless cat trick, right?)
|
| Zsh can already do heredocs; whether you use quotes or not affects how
| quotes and stuff are treated in the actual heredoc.
|
| --
| "Since when is skepticism un-American?
| Dissent's not treason but they talk like it's the same..."
| (Sleater-Kinney - "Combat Rock")
|
|
next prev parent reply other threads:[~2003-02-01 17:59 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 [this message]
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
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=BBEKIEKOHGEFJBFLEENGCEFFCGAA.piyokun@email.com \
--to=piyokun@email.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).