Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Export problem
- X-seq: zsh-workers 14741
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "Zsh Hackers" <zsh-workers@xxxxxxxxxxxxxx>
- Subject: Re: Export problem
- Date: Wed, 6 Jun 2001 10:06:59 +0000
- In-reply-to: <000801c0ee4d$6b321270$21c9ca95@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <000801c0ee4d$6b321270$21c9ca95@xxxxxxxxxxxxxx>
On Jun 6, 9:56am, Andrej Borsenkow wrote:
} Subject: RE: Export problem
}
} 2. Both bash and ksh88 (version that I have) do not split export arguments.
} That calls for compatibility option.
}
} I am not sure how to call it. May be it is time to start POSIX_* set of
} options. POSIX_EXPORT_SPLIT?
Hrm; POSIX_EXPORT_SPLIT would be *on* by default, then, as bash/ksh do
not split. And it's not just `export', it's also `typeset' etc. Maybe
KSH_TYPESET would be a better option name, and we could also check it
to see whether we should force compatibility with ksh's `typeset' flag
letter meanings in case of collisions (same way ksh emulation changes
the interpretation of `set' single-letter-options).
Unless we're already incompatibile with POSIX typeset flag letters, or
unless we're worried about bash compatibility and bash has yet a third
set of options, in which case we've got a deeper hole to dig out of.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author