From: Anthony Heading <aheading@jpmorgan.com>
To: schaefer@nbn.com
Cc: aheading@jpmorgan.com, zsh-workers@math.gatech.edu
Subject: Re: Tag functions with shell options?
Date: Tue, 2 Jul 1996 23:27:35 +0100 (BST) [thread overview]
Message-ID: <199607022227.XAA25585@gmp-etpres1.uk.jpmorgan.com> (raw)
In-Reply-To: <960702143114.ZM5210@candle.brasslantern.com> from "Bart Schaefer" at Jul 2, 96 02:31:10 pm
Bart wrote:
>
> } The lack of context was sort-of deliberate, since I
> } suspected any interest would be in the wider picture, rather than my
> } particular petty problems. It seemed simply an example of something
> } it would be nice to support elegantly.
>
> This introduces a whole class of problems, which is most obvious in the
> case when you *do not* know the names of the functions that should have
> their local options (or whatever) changed. In that case you almost end
> up needing something like Perl's "package".
Right. I guess this is like what I would have thought of doing as a sort of
closure. So a function, when defined, would snapshot its option-environment.
function setup() {
setopt local_options closure_options sh_word_split
. /someone/elses/setup/file.sh
}
> Because the alias for yfn was introduced *after* xfn1 was defined, xfn1
> still references the "real" yfn, rather than the alias. The presumption
> is that if you're going to use
OK. As if aliases are resolved at parse-time. Or something. Perhaps they are.
I should RTFS. But I understand now.
Thank-you all.
A
prev parent reply other threads:[~1996-07-02 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-02 12:05 Anthony Heading
1996-07-02 13:36 ` Zefram
1996-07-02 14:12 ` Anthony Heading
1996-07-02 15:17 ` Zefram
1996-07-02 15:37 ` Peter Stephenson
1996-07-02 16:57 ` Anthony Heading
1996-07-02 19:07 ` Bart Schaefer
1996-07-02 19:53 ` Anthony Heading
1996-07-02 21:31 ` Bart Schaefer
1996-07-02 22:27 ` Anthony Heading [this message]
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=199607022227.XAA25585@gmp-etpres1.uk.jpmorgan.com \
--to=aheading@jpmorgan.com \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).