From: Felipe Contreras <felipe.contreras@gmail.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: zsh-workers@zsh.org, Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: Bug with sh emulation; shouldn't KSH_TYPESET be set?
Date: Mon, 30 Jan 2012 23:46:46 +0200 [thread overview]
Message-ID: <CAMP44s0Mji0OdU7K-ftazbwD2YYJzXzm1J1yEQOeWc0f2=zjMg@mail.gmail.com> (raw)
In-Reply-To: <878vkoapkq.fsf@ft.bewatermyfriend.org>
On Mon, Jan 30, 2012 at 10:43 PM, Frank Terbeck <ft@bewatermyfriend.org> wrote:
> Felipe Contreras wrote:
> [...]
>> local t=$(echo foo --bar)
> [...]
>> But not in zsh, with sh emulation. Enabling KSH_TYPESET makes it work.
>>
>> Shouldn't it be enabled with sh emulation?
>>
>> BTW. What exactly is 'emulate sh' supposed to emulate? I would like to
>> run that shell to check for compatibility issues, and apparently it's
>> not bash.
>
> "emulate sh" is POSIX shell emulation (we did amend this mode in the
> past to work as much as possible as POSIX describes). Neither typeset
> nor local are part of POSIX (at least not SUSv3 - I don't know about
> v4).
>
> So, I don't think it should be enabled.
But it wouldn't hurt either, right? It would be nice to have some
'bash' emulation mode, but since there isn't any, why not enable this
harmless option?
> FWIW, dash and posh behave like zsh's sh-mode here. Ksh93 doesn't work
> at all, because it has no `local' (only typeset). Mksh, pdksh and bash
> work like KSH_TYPESET was set in zsh.
Hmm, I see, but there's no bash emulation mode =/
I guess it's time to compare the differences between ksh and sh
emulation to see which is closer.
--
Felipe Contreras
next prev parent reply other threads:[~2012-01-30 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 20:21 Felipe Contreras
2012-01-30 20:43 ` Frank Terbeck
2012-01-30 21:46 ` Felipe Contreras [this message]
2012-01-30 22:17 ` Frank Terbeck
2012-01-30 22:20 ` Vincent Lefevre
2012-01-31 9:43 ` Peter Stephenson
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='CAMP44s0Mji0OdU7K-ftazbwD2YYJzXzm1J1yEQOeWc0f2=zjMg@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=ft@bewatermyfriend.org \
--cc=zsh-workers@zsh.org \
/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).