From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>,
A.Main@dcs.warwick.ac.uk (Zefram),
zsh-workers@math.gatech.edu
Subject: Re: more dependencies on emulation
Date: Thu, 18 Jul 1996 19:44:51 -0700 [thread overview]
Message-ID: <960718194451.ZM784@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: more dependencies on emulation" (Jul 19, 2:12am)
On Jul 19, 2:12am, Zoltan Hidvegi wrote:
> Subject: Re: more dependencies on emulation
> Zefram wrote:
> > After this, the only use of emulation is in the emulate builtin itself,
> > and in initialisation (where it's difficult to avoid).
>
> I did not want to introduce new options like FUNCTION_ARGZERO and
> SH_FILE_SUBST because I consider these options useful only in sh/ksh
> compatibility mode.
Does that mean you're not planning to include these patches in 3.0?
Or does this:
> But my solition was certainly not very good.
mean that you ARE planning to include them?
> Increasing the number of settable options makes it
> more and more difficult to write zsh functions which are independent of the
> current options setting.
Actually, the only options that make this difficult are those that (1)
affect non-interactive behavior and (2) are not tied to an emulation.
As long as the "emulate" command sets/unsets all the appropriately-
tagged options, you can always do:
zshfoo() {
setopt localoptions
emulate zsh
# Now do stuff using default zsh settings
}
Note, though, that for this to work "emulate" should never turn OFF
localoptions -- I note that it turns it ON for ksh, so right now it
probably also turns it off sometimes.
> > My comments in article 1669 about the option patch in article 1275 apply
> > here also. Applying this patch by hand if you don't have the option
> > patch applied is not difficult. If anyone wants an updated copy of the
> > option patch, mail me.
>
> I'd like one. I wanted to include this in pre3 but again I had no time.
Ooooh. I think I'd rather it stayed out for 3.0.
next prev parent reply other threads:[~1996-07-19 2:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-18 14:23 Zefram
1996-07-18 22:18 ` Bart Schaefer
1996-07-19 1:34 ` Zoltan Hidvegi
1996-07-19 2:59 ` Bart Schaefer
1996-07-19 14:21 ` Zefram
1996-07-19 14:17 ` Zefram
1996-07-19 14:07 ` Zefram
1996-07-19 0:12 ` Zoltan Hidvegi
1996-07-19 2:44 ` Bart Schaefer [this message]
1996-07-19 14:26 ` Zefram
1996-07-19 18:14 ` Bart Schaefer
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=960718194451.ZM784@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=hzoli@cs.elte.hu \
--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).