zsh-workers
 help / color / mirror / code / Atom feed
From: Greg Klanderman <gak@klanderman.net>
To: zsh-workers@zsh.org
Subject: Re: ZSH_SCRIPT
Date: Wed, 02 Mar 2016 16:33:45 -0500	[thread overview]
Message-ID: <87y4a05zuu.fsf@lwm.klanderman.net> (raw)
In-Reply-To: <20160302155610.54c9b388@pwslap01u.europe.root.pri> (Peter Stephenson's message of "Wed, 02 Mar 2016 15:56:10 +0000")

>>>>> On March 2, 2016 Peter Stephenson <p.stephenson@samsung.com> wrote:

> On Wed, 2 Mar 2016 10:48:42 -0500
> Greg Klanderman <gak@klanderman.net> wrote:
>> Did you want this ztrdup in or not:
>> 
>> zsh_script = ztrdup(runscript);

> I think it makes sense (unless it's duplicated again).

well, as it currently stands there is that ztrdup() shown above in
zsh_main() and then another here in createparamtable():

    setsparam("ZSH_SCRIPT", ztrdup(zsh_script));

Yesterday, a few emails back in this thread Bart had said he thought
there should probably be a ztrdup() in zsh_main() but that maybe it
was not needed due to the one in createparamtable().

>> It looks like ZSH_NAME comes from argv[0] immediately after the early
>> metification you pointed out above, but is being re-metified here:
>> 
>> setsparam("ZSH_NAME", ztrdup_metafy(zsh_name));

> That's probably wrong for the reasons I gave, unless I'm missing
> something basic.

OK, I will fix that in the next version of the patch I send.

Greg


  reply	other threads:[~2016-03-02 21:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 17:34 ZSH_SCRIPT Greg Klanderman
2016-02-24 22:31 ` ZSH_SCRIPT Bart Schaefer
2016-02-25  9:33   ` ZSH_SCRIPT Peter Stephenson
2016-02-25 17:59     ` ZSH_SCRIPT Greg Klanderman
2016-02-25 23:04       ` ZSH_SCRIPT Bart Schaefer
2016-02-29 23:36         ` ZSH_SCRIPT Greg Klanderman
2016-03-01  9:27           ` ZSH_SCRIPT Peter Stephenson
2016-03-01 14:39             ` ZSH_SCRIPT Greg Klanderman
2016-03-01 15:07               ` ZSH_SCRIPT Peter Stephenson
2016-03-01 16:36                 ` ZSH_SCRIPT Greg Klanderman
2016-03-01 18:36                   ` ZSH_SCRIPT Bart Schaefer
2016-03-01 20:14                     ` ZSH_SCRIPT Greg Klanderman
2016-03-02  9:30                       ` ZSH_SCRIPT Peter Stephenson
2016-03-02 15:48                         ` ZSH_SCRIPT Greg Klanderman
2016-03-02 15:56                           ` ZSH_SCRIPT Peter Stephenson
2016-03-02 21:33                             ` Greg Klanderman [this message]
2016-03-02 19:34                 ` ZSH_SCRIPT Martijn Dekker
2016-03-02 21:24                   ` ZSH_SCRIPT Greg Klanderman
2016-03-03  9:37                     ` ZSH_SCRIPT Peter Stephenson
2016-03-03 17:26                       ` ZSH_SCRIPT Greg Klanderman
2016-03-03 17:37                         ` ZSH_SCRIPT Peter Stephenson
2016-03-03 19:36                           ` ZSH_SCRIPT Greg Klanderman
2016-03-03 20:39                             ` ZSH_SCRIPT Peter Stephenson
2016-03-03 20:44                             ` ZSH_SCRIPT Bart Schaefer
2016-03-03 20:50                               ` ZSH_SCRIPT Bart Schaefer
2016-03-04  2:07                                 ` ZSH_SCRIPT Greg Klanderman
2016-03-05 16:22                                   ` ZSH_SCRIPT Bart Schaefer
2016-03-05 20:03                                     ` ZSH_SCRIPT Greg Klanderman

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=87y4a05zuu.fsf@lwm.klanderman.net \
    --to=gak@klanderman.net \
    --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).