Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Assigning to $0 (formerly: PATCH: funcstack[-1])
- X-seq: zsh-workers 37978
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Assigning to $0 (formerly: PATCH: funcstack[-1])
- Date: Mon, 15 Feb 2016 07:51:32 +0100
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=shUSc3Lyj7MjI2cMTFNQu4KmjCYUNKHYjc7yGpTXhq8=; b=z6ojNz3fwC7oeHQtLBUu5+ovPvOti5PXHZAlhdCB4UNLgU5z4xtt69pSyusE6trwd6 3eltUqSGWOG2LODkeGz8n2q1+8acHhBvm8G0OcGKKbA73gzRB0PQB3SeanJuoipumVep hBd7XQjSqF+Y00+qwl0hcsPp+40Sdk5HaDa4+YZLMsrBjiu9f6WCqWsh3uaXH4LTiv/u ySXJHE6dpGMJ6Ymw3mFNQk8KW7BNKQxIn8hH6nvGbGqjf/PXvvPy8fiCJxnILy/q51gN ojy6hbAjcawRELOnX5FnqKP/6DVKAW00ydH3EfFSxvs4Pt92BdLRRnnB1oUcbuKJlWVK I9YQ==
- In-reply-to: <160214135247.ZM3326@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20151230104531.GA20496@linux.vnet.ibm.com> <5683F898.7010907@inlv.org> <20160205100902.GA14979@linux.vnet.ibm.com> <20160205102735.1f09973a@pwslap01u.europe.root.pri> <20160205104444.2437ad33@pwslap01u.europe.root.pri> <20160205160236.1274aa5b@pwslap01u.europe.root.pri> <20160205222750.1fda3574@ntlworld.com> <160214135247.ZM3326@torch.brasslantern.com>
On Sun, Feb 14, 2016 at 10:52 PM, Bart Schaefer
<schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Feb 5, 10:27pm, Peter Stephenson wrote:
> }
> } By the way, looking at the code I just notice that the following isn't
> } an error even though it doesn't do what you presumably expect:
> }
> } % setopt posixargzero
> } % print $0
> } zsh
> } % 0=foo
> } % print $0
> } zsh
> }
> } Maybe that's OK so far, but you don't even get the value back when you
> } unset the option; it's silently lost.
>
> So what behavior would be preferable?
>
> 1. POSIXARGZERO makes $0 report an error on assignment (read only?)
>
> 2. the value is stored and reappears when POSIXZERO is unset?
>
> 3. as (2) but a warning is printed?
>
> As another by-the-way:
>
> torch% print $0; () { typeset -g 0=argzero; print $0 }; print $0
> Src/zsh
> argzero
> Src/zsh
>
> So typeset will accept 0 as a valid name and -g as a valid option, but
> can't actually set the global $0.
http://www.zsh.org/mla/workers/2015/msg01400.html Some time before
that patch, assigning to $0 was always possible, but at some point it
stopped working.
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author