Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: HP-UX 11.00 tgetenv dilemma

On Jun 12,  5:04pm, Peter Stephenson wrote:
} "Bart Schaefer" wrote:
} > 
} > The remaining problem is that KSH_TYPESET should be set by `emulate bash',
} > which it is not because `emulate bash' is equivalent to `emulate sh'.
} ...and we don't want to set it for that because it's apparently correct for
} the POSIX shell.

Does the POSIX shell even permit parm=value arguments to `export' and
`typeset'?  Maybe we're worrying about an impossibility.  We've rarely
hesitated to allow forward-compatible-only extensions (i.e., in the
emulated shell the extension would cause an actual syntax error) to
remain in effect even during `emulate -R', as we're mainly concerned
that scripts written *without* such extensions will work properly.

} Should we introduce a separate emulation for bash? It's getting
} horribly complicated and we've never been that concerned about bash
} compatilibity for non-POSIX features.

Hrm.  Either we should actually make it work, or we should document that
bash is not fully emulated (the way we document that csh is not fully
emulated).  Or both, as there are probably other bash-isms that we don't
emulate, though we have a whole lot of OPT_ALIAS things for bash.  Or
else remove `emulate bash' again and have only (|c|k|z)sh.

Doesn't seem like it's all that complicated to add another flag, though.

} By the way, bash also seems to have the equivalent of MAGIC_EQUAL_SUBST

Hrm, again.  I suppose we could special-case those two options in the
emulate() function when the argument is `bash', although their default
values would then appear reversed in the output from `setopt'.

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