From: Anthony Heading <aheading@jpmorgan.com>
To: schaefer@nbn.com
Cc: aheading@jpmorgan.com, pws@ifh.de, A.Main@dcs.warwick.ac.uk,
zsh-workers@math.gatech.edu
Subject: Re: Tag functions with shell options?
Date: Tue, 2 Jul 1996 20:53:37 +0100 (BST) [thread overview]
Message-ID: <199607021953.UAA05899@et-sun4.uk.jpmorgan.com> (raw)
In-Reply-To: <960702120736.ZM4601@candle.brasslantern.com> from "Bart Schaefer" at Jul 2, 96 12:07:32 pm
> Right; it doesn't seem that Anthony has given us enough context. Do
> the functions get defined and then executed all within /etc/profile,
> for example? Or do they act as wrappers around actual applications,
> so they don't run until you execute them "manually"? (Sounds like the
> latter, but ...)
Yes, the latter. 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.
> it seems to me that a much simpler implementation of sws_fn is:
[wrapping the function, and then aliasing the wrapper to the original]
> The only drawback to this is that other functions that may already have
> been defined won't see the alias -- but presumably those functions will
> themselves be given the sws_fn treatment, so it's moot.
Hmm. Don't understand the first point, but I'll experiment.
Thanks
Anthony
next prev parent reply other threads:[~1996-07-02 20:03 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 [this message]
1996-07-02 21:31 ` Bart Schaefer
1996-07-02 22:27 ` Anthony Heading
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=199607021953.UAA05899@et-sun4.uk.jpmorgan.com \
--to=aheading@jpmorgan.com \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=pws@ifh.de \
--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).