From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh <zsh-workers@sunsite.dk>
Subject: Re: Problem with an exported array
Date: Mon, 22 Sep 2003 18:03:59 +0000 [thread overview]
Message-ID: <1030922180359.ZM20397@candle.brasslantern.com> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2003-09-22 18:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 8:30 DervishD
2003-09-22 9:08 ` Oliver Kiddle
2003-09-22 9:31 ` DervishD
2003-09-22 9:48 ` Peter Stephenson
2003-09-22 11:33 ` DervishD
2003-09-22 13:44 ` Peter Stephenson
2003-09-22 14:04 ` DervishD
2003-09-22 14:22 ` Bart Schaefer
2003-09-22 14:45 ` Danek Duvall
2003-09-22 16:30 ` DervishD
2003-09-22 17:58 ` Bart Schaefer
2003-09-22 18:06 ` Danek Duvall
2003-09-22 15:52 ` Peter Stephenson
2003-09-22 17:44 ` DervishD
2003-09-22 18:03 ` Bart Schaefer [this message]
2003-09-23 7:52 ` DervishD
2003-09-22 19:28 ` Wayne Davison
2003-09-23 9:44 ` Peter Stephenson
2003-09-23 7:57 ` Oliver Kiddle
2003-09-23 16:02 ` Peter Stephenson
2003-09-24 13:09 ` DervishD
2003-09-22 16:33 ` DervishD
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=1030922180359.ZM20397@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).