From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: environment stuff.
Date: Wed, 26 Nov 2014 18:25:17 -0800 [thread overview]
Message-ID: <54768B8D.8000901@eastlink.ca> (raw)
In-Reply-To: <141126180307.ZM11187@torch.brasslantern.com>
On 11/26/2014 06:03 PM, Bart Schaefer wrote:
> On Nov 26, 5:23pm, Ray Andrews wrote:
> }
> } When you do a complete dump of the environment, there's this
>
> Let me point out that if you get any "typeset -A ..." then you're NOT
> doing a complete dump of the environment. You're doing a complete dump
> of the internal parameter space. Some things get copied back and forth
> from the internal parameter space to the environment, and you can use
> parameter references to examine the environment, but the two are not
> the same. The environment is the exported subset of the parameter
> space, and you can't export arrays, especially associative ones.
Good to know. I trust this parameter space is off limits and I don't have
to know anything more about it for now?
> } ginormous thing that starts:
> }
> } typeset -A _comps
> }
> } What on Earth is it? Where does stuff like that get set?
>
> That's the list of all command names mapped to functions that implement
> the completions for them. It's populated by compinit.
Such a load of work!
next prev parent reply other threads:[~2014-11-27 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 1:23 Ray Andrews
2014-11-27 2:03 ` Bart Schaefer
2014-11-27 2:25 ` Ray Andrews [this message]
2014-11-27 3:45 ` Bart Schaefer
2014-11-27 22:14 ` Ray Andrews
2014-11-27 23:05 ` Bart Schaefer
2014-11-28 21:58 ` Roman Neuhauser
2014-11-28 22:55 ` Ray Andrews
2014-11-29 10:53 ` Roman Neuhauser
2014-11-29 16:21 ` Ray Andrews
2014-11-30 3:59 ` TJ Luoma
2014-11-30 4:16 ` Lawrence Velázquez
2014-11-28 23:37 ` Bart Schaefer
2014-11-29 9:35 ` Roman Neuhauser
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=54768B8D.8000901@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).