zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Parameter exansion, correction and small patch
Date: Mon, 14 Jun 1999 16:46:22 +0200	[thread overview]
Message-ID: <9906141446.AA40350@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Kiddle, Oliver""'s message of "Mon, 14 Jun 1999 13:52:47 DFT." <4FBF540FF16FD1119D9600A0C94B2B51F29E83@napier.logica.co.uk>

"Kiddle, Oliver" wrote:
> Two questions:
> 
> First, how do I take the output of a command in $(...) and use the parameter
> expansion flags to split the output into an array for each line. I'm sure
> I've done this before but can't get it to work anymore. I've tried most
> things I can think of without success. For example:
>   echo ${${(f)$(ps)}% *}
> I would expect this to apply the '% *' substitution for each line of the
> output of ps but it does it for all the lines combined.

The key problem is with quoting.  We just introduced a tweak so that you
can now do
  echo ${${(f)"$(ps)"}% *}
since an unquoted $(ps) does word-splitting on all spaces.  The traditional
way of doing this was
  echo "${(@)${(@f)$(ps)}% *}"
but that's more cumbersome.

> Second, correction seems to be applied when I declare a function which can
> be annoying. e.g.
> zsh -f
> setopt correct
> les() {
> zsh: correct 'les' to 'els' [nyae]? n
> function>
> 
> You might consider this to be a bug but if not, is there any way of
> preventing it?

`correct' isn't all that flexible at the moment.  There ought to be a way
of fixing it internally.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


      reply	other threads:[~1999-06-14 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-14 12:52 Kiddle, Oliver
1999-06-14 14:46 ` Peter Stephenson [this message]

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=9906141446.AA40350@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.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).