zsh-workers
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: More rabbit-holes with unset variables
Date: Thu, 26 Nov 2020 17:45:36 -0600	[thread overview]
Message-ID: <CAMP44s0WSt_J7TjyPEKvH9TxzWBvTVFTB-pK26G+9SacYeQrAw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bHCrpwbkZBOgwjwF7M9uo+1_ZEa53hxSwE2fuuBuQfyw@mail.gmail.com>

On Thu, Nov 26, 2020 at 4:41 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Thu, Nov 26, 2020 at 1:21 PM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> >
> > I asked who objected to the specific behavior I quoted.
>
> I'm not going to dig through the austin-group archives to try to
> distinguish which of the two parts of the quoted behavior (inherit, or
> otherwise not set) was the source of anyone's objection.  I concede
> that the explanatory paragraph in the rationale did not call out
> either of those behaviors.

The question was not addressed to you, but to the person that brought
up the bug report.

A quick look at the bug report doesn't show anyone objecting to that.

> > On Thu, Nov 26, 2020 at 2:42 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> >
> > > so a the only useful "declared but not set" variable is a simple
> > > scalar.
> >
> > And by scalar I suppose you mean string.
>
> I mean the simplest form of what zsh refers to as "scalar" internally.
> Yes, that's ordinarily representable in C by "char[]", but in the
> abstract that doesn't matter.

Strings in C are typically declared as "char *", not "char []".

-- 
Felipe Contreras



  reply	other threads:[~2020-11-26 23:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  7:02 Bart Schaefer
2020-11-25 13:19 ` Stephane Chazelas
2020-11-25 22:17   ` Felipe Contreras
2020-11-26  6:10     ` Stephane Chazelas
2020-11-26  7:20       ` Felipe Contreras
2020-11-26 11:21         ` Oliver Kiddle
2020-11-26 11:29           ` Roman Perepelitsa
2020-11-26 19:08             ` Felipe Contreras
2020-11-26 19:29           ` Felipe Contreras
2020-11-26 21:13           ` Bart Schaefer
2020-11-26 21:31             ` Felipe Contreras
2020-11-26 23:29               ` Bart Schaefer
2020-11-26 23:32                 ` Bart Schaefer
2020-11-26 23:53                 ` Felipe Contreras
2020-11-27  0:23                   ` Bart Schaefer
2020-11-27  1:51                     ` Felipe Contreras
2020-11-27 20:01                       ` Bart Schaefer
2020-11-27 21:49                         ` Felipe Contreras
2020-11-27 22:06                           ` Bart Schaefer
2020-11-27 23:35                             ` Felipe Contreras
2020-11-26 22:07       ` Bart Schaefer
2020-11-26 20:41     ` Bart Schaefer
2020-11-26 20:49       ` Stephane Chazelas
2020-11-26 21:20       ` Felipe Contreras
2020-11-26 22:41         ` Bart Schaefer
2020-11-26 23:45           ` Felipe Contreras [this message]
2020-11-27  0:09             ` Bart Schaefer
2020-11-27  0:30               ` Felipe Contreras
2020-11-27  0:51                 ` Bart Schaefer
2020-11-27  1:30                   ` Felipe Contreras
2020-11-27 20:54                     ` Bart Schaefer
2020-11-27 22:10                       ` Felipe Contreras
2020-11-27 22:39                         ` Bart Schaefer
2020-11-28  0:00                           ` Felipe Contreras
2020-11-28  0:04                             ` Bart Schaefer
2020-11-28 10:52                               ` Felipe Contreras
2020-11-28  0:36                             ` The emulation rabbit-hole RE typeset/unset Bart Schaefer
2020-11-28 11:35                               ` Felipe Contreras
2020-11-28 16:56                                 ` Bart Schaefer
2020-12-01  8:49                                   ` Felipe Contreras

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=CAMP44s0WSt_J7TjyPEKvH9TxzWBvTVFTB-pK26G+9SacYeQrAw@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).