zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: Re: Manpage improvement
Date: Mon, 28 Sep 1998 09:34:34 -0700	[thread overview]
Message-ID: <980928093434.ZM2061@candle.brasslantern.com> (raw)
In-Reply-To: <9809281401.AA32041@ibmth.df.unipi.it>

On Sep 28,  4:00pm, Peter Stephenson wrote:
} Subject: Re: Manpage improvement
}
} > x11amp "${(@f)$(locate Argentina|grep .mp3)}"
} >
} > I hope this might qualify as an example to spice up future zsh
} > manpages.
} 
} Here's a change to the manual source which should make this sort of
} thing a little clearer.

The first hunk of Peter's patch fails if you've applied my collection
of man page patches, posted a couple of months ago over the course of
several weeks.  Here's a patch that will apply on top of my previous
patches.

I've taken the liberty of changing

    prints the variables tt($foo) after deleting both the head and tail
    from the value.

to

    substitues the value of tt($foo) with both tt(head) and tt(tail)
    deleted.

My previous patch had already added a subsection "Parameter Expansion
Flags" where Peter's added "Flags".

If you tried to apply Peter's patch and got one failed hunk and one
succeeded hunk, you can delete the second hunk from the patch below
and apply only the first hunk.

Index: Doc/Zsh/expn.yo
===================================================================
--- expn.yo	1998/08/27 15:56:33	1.6
+++ expn.yo	1998/09/28 16:32:22
@@ -450,7 +450,11 @@
 If a tt(${)...tt(}) type parameter expression or a
 tt($LPAR())...tt(RPAR()) type command substitution is used in place of
 var(name) above, it is substituted first and the result is used as if
-it were the value of var(name).
+it were the value of var(name).  Thus it is
+possible to perform nested operations:  tt(${${foo#head}%tail})
+substitues the value of tt($foo) with both tt(head) and tt(tail)
+deleted.  The form with tt($LPAR())...tt(RPAR()) is often useful in
+combination with the flags described next; see the example below.
 
 subsect(Parameter Expansion Flags)
 cindex(parameter expansion flags)
@@ -567,6 +571,17 @@
 Include the length of the match in the result.
 )
 enditem()
+subsect(Example)
+The flag tt(f) is useful to split a double-quoted substitution line by
+line.  For example,
+
+nofill(var(cmd) tt("${)tt(LPAR()f)tt(RPAR()$)tt(LPAR()<)var(file)tt(RPAR()}"))
+
+will substitue the contents of var(file) divided so that one line is
+supplied per argument to var(cmd).  Compare this with the effect of
+tt($)tt(LPAR()<)var(file)tt(RPAR()) alone, which divides the file
+up by words, or the same inside double quotes, where the entire
+contents of the file are passed as a single argument.
 texinode(Command Substitution)(Arithmetic Expansion)(Parameter Expansion)(Expansion)
 sect(Command Substitution)
 cindex(command substitution)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1998-09-28 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.02.9809271745400.19479-100000@astmatix.ida.liu.se>
1998-09-28 14:00 ` Peter Stephenson
1998-09-28 16:34   ` Bart Schaefer [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=980928093434.ZM2061@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@math.gatech.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.
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).