From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: typesetting parameters
Date: Sun, 13 Jun 2004 21:58:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0406132153360.32342-100000@toltec.zanshin.com> (raw)
In-Reply-To: <26243486-BDAE-11D8-BDC7-000A95D2C79E@kalama.no-ip.org>
On Sun, 13 Jun 2004, lists wrote:
> I'm having difficulty understanding why one would define a parameter
> with typeset before using it.
One probably wouldn't, when interactively typing commands, unless one
wanted to use the special attributes such as padding, alignment, other
integer bases, or floating-point precision.
The primary time/place and reason to use typeset is when defining shell
functions, to create variables that are local to the function scope. When
you use "local" that's really an alias for typeset.
next prev parent reply other threads:[~2004-06-14 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 2:54 lists
2004-06-14 4:58 ` Bart Schaefer [this message]
2004-06-14 18:24 ` Vincent Stemen
2004-06-15 2:43 ` lists
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=Pine.LNX.4.44.0406132153360.32342-100000@toltec.zanshin.com \
--to=schaefer@brasslantern.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).