Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: sourcing a sh file in zsh
- X-seq: zsh-workers 26416
- From: Richard Hartmann <richih.mailinglist@xxxxxxxxx>
- To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- Subject: Re: sourcing a sh file in zsh
- Date: Sat, 24 Jan 2009 21:47:19 +0100
- Cc: zsh-workers@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kOa+oklwLyc19GTw6Cz+jcYqgNqWmuvfDeMQQyO3+ks=; b=Wie0YU5DSSuu9zfiiMPSN8qxhDzC0Ken30KYsRJGbUcaer+nFtekvqnqHUi1uFpKRa +tna/dnuB2rPRX7ra9sKzAjScvgrwKG5ki6xC9SK/hQ4eIllmTyp5UnTmZ0wa3gNqqg9 pC93gwDOCFkDlrTXNZ3UiQ9OGAIJQI59HJpPE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=n2R2BUha6KMk3zwoK0579JHBnD22YRV1yE2TAwi0UnT1f5bh/BF6ax9O14oyPJ2fU4 ku5VuSXd7xYOmiy54IC3SkC6e8kqZ9gWbkgbLUHKFQ1NSJoRZst8Z5Wqhln9hwMRSqxD BdqfTQgMtTi7jljNRVLE9rsvggNyK0xO2mOIE=
- In-reply-to: <20090124173836.64403fdc@pws-pc>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <BD9D2405-AD6A-4336-9C8A-85149165B6B8@xxxxxxxxx> <200901161939.54651.arvidjaar@xxxxxxxxxx> <090116102934.ZM22119@xxxxxxxxxxxxxxxxxxxxxx> <200901241859.30029.arvidjaar@xxxxxxxxx> <20090124173836.64403fdc@pws-pc>
On Sat, Jan 24, 2009 at 18:38, Peter Stephenson
<p.w.stephenson@xxxxxxxxxxxx> wrote:
> I don't think functions should
> *always* inherit the emulation because it changes the current behaviour
> too much---we would be resetting a whole load of options before every
> function call.
Me neither. If people think this is useful, it might make sense as an
option, but it's way too magical for my taste.
> I would guess we don't want to apply it to autoloaded functions which
> already have their own rules. We can also add commands to tweak the
> emulation mode for individual functions, but that can be done
> separately.
>
> We do need to be quite clear on the rules to avoid tying ourselves in
> knots with things like "emaulate -LRE sh autoload foo". "foo", in my
> interpretation, would not inherit sh behaviour here. I think nested
> "emulate"s should be unproblematic, however.
Agreed.
Richard
Messages sorted by:
Reverse Date,
Date,
Thread,
Author