From: Frank Terbeck <ft@bewatermyfriend.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Bug with sh emulation; shouldn't KSH_TYPESET be set?
Date: Mon, 30 Jan 2012 23:17:11 +0100 [thread overview]
Message-ID: <87y5so96oo.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAMP44s0Mji0OdU7K-ftazbwD2YYJzXzm1J1yEQOeWc0f2=zjMg@mail.gmail.com> (Felipe Contreras's message of "Mon, 30 Jan 2012 23:46:46 +0200")
Felipe Contreras wrote:
> Frank Terbeck <ft@bewatermyfriend.org> wrote:
[...]
>> 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?
I'm unsure (personally, I wouldn't mind), as to whether the
argument-handling semantics of a random builtin can be changed with
POSIX in mind. Maybe someone with deeper understanding of the standard
can shed some light here.
I'd just do
local foo="$(bar --baz)"
and be done with it. That should be portable over pretty much every
bourne-line shell that supports $(...) and `local',
>> 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.
Unsure, due to fairly limited knowledge of bash's extensions to POSIX.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2012-01-30 22:28 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
2012-01-30 22:17 ` Frank Terbeck [this message]
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=87y5so96oo.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=felipe.contreras@gmail.com \
--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).