Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Problem with an exported array
- X-seq: zsh-workers 19126
- From: DervishD <raul@xxxxxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Problem with an exported array
- Date: Tue, 23 Sep 2003 09:52:26 +0200
- Cc: Zsh <zsh-workers@xxxxxxxxxx>
- In-reply-to: <1030922180359.ZM20397@xxxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, Zsh <zsh-workers@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Organization: Pleyades
- References: <1030922142208.ZM19975@xxxxxxxxxxxxxxxxxxxxxxx> <7352.1064245936@xxxxxxx> <20030922174410.GB12493@DervishD> <1030922180359.ZM20397@xxxxxxxxxxxxxxxxxxxxxxx>
Hi Bart :)
* Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> dixit:
> } > As I said before, there's nowhere in struct param to store the
> } > character; else it's not that hard. Maybe you can see a trick.
> } Surely I'm clueless, but other options in other builtins have
> } characters or numbers following an option: where are they stored?
> By "stored" PWS here means "preserved for the entire life of the
> variable, so that every time $pager is assigned we remember what to
> use to transform it to $PAGER."
OK, gotcha. I didn't think about it, although it's obvious: every
assignment must be 'synced' with the other variable, so the joining
character must be permanent stored, not only during the execution of
typeset. Thanks for the explanation :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author