zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: first adventures
Date: Sat, 1 Nov 2014 21:11:26 +0000	[thread overview]
Message-ID: <20141101211126.4c26682c@pws-pc.ntlworld.com> (raw)
In-Reply-To: <54554194.80109@eastlink.ca>

On Sat, 01 Nov 2014 13:24:52 -0700
Ray Andrews <rayandrews@eastlink.ca> wrote:
> > If you want text not to be processed by the shell, the best way of doing
> > that is to pass it via standard input and output rather than the command
> > line, using "read -r" and "print -r".
> 
> Can you give me an example of that, please?

It doesn't really fit in the case you're looking at.

The point was more that if you had the choice, which you don't, and you
had to pass raw chunks of text around you'd do things like

read -r line < input
print -r -- $line > output

and not actually worry about what was in $line at all.

Perhapse the real point is what you're looking at is an unusual case in
that you've been passed a piece of raw shell input and you're thinking
about what it would look like if it wasn't raw any more.  This is hairy
stuff that most people who consider themselves shell language gurus
probably never have to think about --- extracting bits of semi-parsed
chunks of input is something most people would do in a language like
Lisp rather than a shell.  So it's not surprising you're a bit
bamboozled when you're coming to this out of nowhere.

pws


  reply	other threads:[~2014-11-01 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <544D2D6F.8030505@eastlink.ca>
     [not found] ` <20141026175257.2611487b@pws-pc.ntlworld.com>
     [not found]   ` <544FD6DD.7010806@eastlink.ca>
     [not found]     ` <141028210510.ZM10784@torch.brasslantern.com>
     [not found]       ` <54510A96.20009@eastlink.ca>
     [not found]         ` <141029134624.ZM15681@torch.brasslantern.com>
     [not found]           ` <545178DF.1040600@eastlink.ca>
     [not found]             ` <141029210738.ZM15833@torch.brasslantern.com>
     [not found]               ` <5452ED18.7070208@eastlink.ca>
     [not found]                 ` <141030195906.ZM30057@torch.brasslantern.com>
2014-10-31 18:10                   ` Ray Andrews
2014-10-31 19:59                     ` Peter Stephenson
2014-11-01  4:26                       ` Ray Andrews
2014-11-01  7:51                         ` Mikael Magnusson
2014-11-01 16:35                           ` Ray Andrews
2014-11-01 18:40                             ` Peter Stephenson
2014-11-01 20:24                               ` Ray Andrews
2014-11-01 21:11                                 ` Peter Stephenson [this message]
2014-11-01 23:23                                   ` Ray Andrews

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=20141101211126.4c26682c@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \
    /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).