From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: typeset -g (was Re: rsync --progress stops completion)
Date: Sun, 21 Sep 2014 14:54:29 -0700 [thread overview]
Message-ID: <140921145429.ZM1550@torch.brasslantern.com> (raw)
In-Reply-To: <lvngb9$v5o$1@ger.gmane.org>
On Sep 21, 11:35pm, Yuri D'Elia wrote:
}
} Can you explain a bit in more detail what is the difference between an
} undeclared global and typeset -g? The manpage wasn't clear to me.
There are only two:
The WARN_CREATE_GLOBAL option will trigger on the first assignment to
an undeclared global, so for best behavior it should be declared.
In the absence of -g, typeset inside a function will create local, so
-g is needed if you want to apply other flags such as -a or -H.
next prev parent reply other threads:[~2014-09-21 21:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 15:00 rsync --progress stops completion Yuri D'Elia
2014-09-16 15:09 ` Vadim A. Misbakh-Soloviov
2014-09-16 17:50 ` Yuri D'Elia
2014-09-17 0:51 ` Bart Schaefer
2014-09-17 8:08 ` Yuri D'Elia
2014-09-17 15:51 ` Bart Schaefer
2014-09-18 9:42 ` Yuri D'Elia
2014-09-18 16:36 ` Bart Schaefer
2014-09-19 2:01 ` Bart Schaefer
2014-09-19 3:22 ` Mikael Magnusson
2014-09-19 11:40 ` Oliver Kiddle
2014-09-21 0:48 ` Bart Schaefer
2014-09-20 13:25 ` Yuri D'Elia
2014-09-20 18:20 ` Bart Schaefer
2014-09-21 16:43 ` Yuri D'Elia
2014-09-21 17:20 ` Bart Schaefer
2014-09-21 17:33 ` Yuri D'Elia
2014-09-21 19:38 ` Bart Schaefer
2014-09-21 20:27 ` Yuri D'Elia
2014-09-21 20:37 ` Yuri D'Elia
2014-09-21 22:07 ` Bart Schaefer
2014-09-21 22:29 ` Yuri D'Elia
2014-09-22 6:58 ` Bart Schaefer
2014-09-21 21:08 ` Bart Schaefer
2014-09-21 21:35 ` Yuri D'Elia
2014-09-21 21:54 ` Bart Schaefer [this message]
2014-09-21 18:52 ` Yuri D'Elia
2014-09-21 18:59 ` Yuri D'Elia
2014-09-20 13:20 ` Yuri D'Elia
2014-09-23 14:23 ` Oliver Kiddle
2014-09-23 14:43 ` Peter Stephenson
2014-09-16 15:25 ` Vadim A. Misbakh-Soloviov
2014-09-16 16:28 ` Bart Schaefer
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=140921145429.ZM1550@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).