zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: question about parameter expansion
Date: Sat, 26 Sep 2015 14:34:04 -0700	[thread overview]
Message-ID: <150926143404.ZM17641@torch.brasslantern.com> (raw)
In-Reply-To: <56070A12.7090907@eastlink.ca>

On Sep 26,  2:11pm, Ray Andrews wrote:
}
} Where is this sort of thing discussed in the manual?

Under "Parameter Expansion".

Perhaps unfortunately, you need to get familar with shell language
terminology.  The strings $1, $2, etc. are referred to as "positional
parameters" whereas $a, $foo, $PATH, etc. are "named parameters".
The signifier "$" is said to introduce an expansion.  (It used to
be that it only introduced a parameter expansion, and parts of the
doc still talk about it that way, but now it also introduces other
expansions like command substitution and arithmetic.)

The word "variable" is usually a synonym for "named parameter," but
might also refer to named strings in the process environment, which
can be referenced as if they were named parameters.

} In any case looking for 'parameter expansion' in the index is no help.

This is a thing about the yodl/info documentation model that I don't
like.  I think all the (sub)section headings should be in the index.
Instead the section headings are in "menus" (which don't show up at all
in the manpage-formatted documentation) and you can't find them with an
index search.

In this specific case, though, "parameter expansion" does appear in the
index, along with "parameter expansion flags", "parameter modifiers",
etc.  How were you searching the index?

} 'Variable' doesn't exist in the index at all

??

* variables:                             Parameters.         (line    6)
* variables, environment:                Parameters.         (line   25)

Again, exactly how are you searching what index?  Have you tried always
searching case-insensitively?


  reply	other threads:[~2015-09-26 21:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26 10:18 Dmitri Vereshchagin
2015-09-26 13:37 ` Mikael Magnusson
2015-09-26 17:41   ` ZyX
2015-09-26 17:57     ` Mikael Magnusson
2015-09-26 18:08   ` Dmitri Vereshchagin
2015-09-26 18:33     ` Mikael Magnusson
2015-09-26 18:57       ` Dmitri Vereshchagin
2015-09-26 21:11         ` Ray Andrews
2015-09-26 21:34           ` Bart Schaefer [this message]
2015-09-26 22:02             ` Ray Andrews
2015-09-27 16:58               ` Bart Schaefer
2015-09-27 18:29                 ` Ray Andrews
2015-09-27 18:43                   ` ZyX
2015-10-02 14:10                 ` Simon Ruderich
2015-10-02 16:35                   ` Ray Andrews
2015-10-02 19:07                     ` Simon Ruderich
2015-10-02 19:50                       ` Ray Andrews
2015-10-02 20:03                         ` latest manual Ray Andrews
2015-10-02 20:23                           ` Ray Andrews
2015-10-02 20:53                             ` Bart Schaefer
2015-10-02 21:55                               ` Ray Andrews
2015-10-03 18:49                                 ` Bart Schaefer
2015-10-03 10:01                               ` Simon Ruderich
2015-10-02 20:58                             ` Andrew Janke

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=150926143404.ZM17641@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).