Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: More rabbit-holes with unset variables
- X-seq: zsh-workers 47656
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Felipe Contreras <felipe.contreras@xxxxxxxxx>
- Subject: Re: More rabbit-holes with unset variables
- Date: Thu, 26 Nov 2020 16:23:39 -0800
- Archived-at: <https://zsh.org/workers/47656>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2020-11/CAH%2Bw%3D7Yv1FO4eTSZfTADPJMz%2B%2BCOsFQJ3UKzGbWF4JdCtcV83g%40mail.gmail.com>
- Authentication-results: zsh.org; iprev=pass (mail-oi1-f178.google.com) smtp.remote-ip=209.85.167.178; dkim=pass header.d=brasslantern-com.20150623.gappssmtp.com header.s=20150623 header.a=rsa-sha256; dmarc=none header.from=brasslantern.com; arc=none
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KtjdkVBLy1dbrQoIP+VJv90Z8xwmOpJ4Ls4lr0ynrzE=; b=JGREICmEiaDiSlo1G2mb0nGEjmijTt56S/Xk+0bFDwN60HQH6pECxsA9Dc4IUfu0ux HiwcfO/hzpUnPjPjJegJ3ZuGCqNKvFa4QD1bgNJFK70uulxCdwy5K4Xxthg6siC5dYUy 8UoY6Yi8mB2UljFlBrmBnmTyy2n9/l4W3suWZIJVLsE0iTwXzpv9cFLJouRaqsb9LVO8 QLMvloe3Hbrb6mMAEH2UZ/QnRxxB2CMpyWnkj0JS0NNG36b9QnpAKAL350a6DpruMQYp o1khnpv8mn5+SyKYVCvVr+bhBP8VwlEQjaa6jtd/gmcZfAQnez12tQqRt/iIiAk3txMl v7mQ==
- In-reply-to: <CAMP44s1pMOrXAYR+VO-acM0dc0KN7SUkcdGEF7RfanfDN8aHfg@mail.gmail.com>
- List-archive: <http://www.zsh.org/sympa/arc/zsh-workers>
- List-help: <mailto:sympa@zsh.org?subject=help>
- List-id: <zsh-workers.zsh.org>
- List-owner: <mailto:zsh-workers-request@zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-subscribe: <mailto:sympa@zsh.org?subject=subscribe%20zsh-workers>
- List-unsubscribe: <mailto:sympa@zsh.org?subject=unsubscribe%20zsh-workers>
- References: <CAH+w=7Zag5MG5D=cRS2UMSsqJ0t=iw5MH9j8=HBO1Q77nbs03w@mail.gmail.com> <20201125131921.vay7h3xk5qn4odgg@chazelas.org> <CAMP44s0-ki=TBzTwnqx10FcTLX4mbphwN88UCx0+h97JTecBWA@mail.gmail.com> <20201126061029.in5tpnrg5bplam5k@chazelas.org> <CAMP44s1XgxdDAAL+7nL3_GK=dZUasPmSWZaKqWg0T-v5iq1eYg@mail.gmail.com> <86243-1606389706.499549@-gQx.nNYG.4Z3k> <CAH+w=7bxavq4DMJtTmSAGTOSoXKsFaXPVyUAGqN1cZLF=+57JQ@mail.gmail.com> <CAMP44s3h2q42=y_fbts5mbgb8oYXYVxKrXQUS35k205X1i15OQ@mail.gmail.com> <CAH+w=7ZgzpTtjcnQ4mmZVAZzi=TE_m1dW0AZQm5oLhMDyG8pZg@mail.gmail.com> <CAMP44s1pMOrXAYR+VO-acM0dc0KN7SUkcdGEF7RfanfDN8aHfg@mail.gmail.com>
- Sender: zsh-workers-request@xxxxxxx
On Thu, Nov 26, 2020 at 3:53 PM Felipe Contreras
<felipe.contreras@xxxxxxxxx> wrote:
>
> > There's no way to "see" the export namespace without forking an
> > external process, so only the internal value matters.
>
> No. The exported value exists whether you decide to look at it or not.
The point is that the exported value DOES NOT exist in this example;
if you were to look at the C global "environ" array following "export
FOO", it would not have (a pointer to a string containing) "FOO" in
it.
> > > typeset -x FOO
> > >
> > > Is different than this:
> > >
> > > typeset -x FOO=""
>
> If this is not inconsistent, then nothing is.
Now I'm confused. All along you've been arguing that { typeset FOO }
SHOULD differ from { typeset FOO="" }. Why does adding -x invert your
argument?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author