Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Problem with an exported array
- X-seq: zsh-workers 19122
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh <zsh-workers@xxxxxxxxxx>
- Subject: Re: Problem with an exported array
- Date: Mon, 22 Sep 2003 18:03:59 +0000
- In-reply-to: <20030922174410.GB12493@DervishD>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <1030922142208.ZM19975@xxxxxxxxxxxxxxxxxxxxxxx> <7352.1064245936@xxxxxxx> <20030922174410.GB12493@DervishD>
On Sep 22, 7:44pm, DervishD wrote:
}
} > 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."
Other commands only have to "store" the option for the lifetime of
the command execution, not potentially forever. There's a generic
mechanism for that, shared by all builtin commands.
If the only choices are colon or space, a one-bit boolean flag in an
existing flag word is sufficient; if it's a character (or a function)
that has to be stored in some new location that doesn't yet exist.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author