From: dana <dana@dana.is>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Document imperfections in POSIX/sh compatibility
Date: Sat, 10 Apr 2021 19:19:22 -0500 [thread overview]
Message-ID: <F56FD538-0428-4D03-BBE2-6E53154EC0EA@dana.is> (raw)
In-Reply-To: <CAH+w=7aAZKpT0f5LT7RaoCehyO6UZe6FimzuQqOP4o=+EwZs2w@mail.gmail.com>
On 10 Apr 2021, at 18:50, Bart Schaefer <schaefer@brasslantern.com> wrote:
> Any particular ones?
I had someone pull the logs. It looks like the person was just warned by
someone else that the sh mode's accuracy is 'iffy' and that zsh doesn't have
POSIX compliance as an actual project goal. There was no specific
functionality mentioned
Since you asked, off the top of my head, zsh's getopts isn't POSIX-compliant
due to its handling of '+'-prefixed options. I think i had a patch somewhere
to make that respect POSIX_BUILTINS
dana
next prev parent reply other threads:[~2021-04-11 0:19 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 23:31 dana
2021-04-10 23:50 ` Bart Schaefer
2021-04-11 0:19 ` dana [this message]
2021-04-11 16:54 ` Bart Schaefer
2021-04-11 17:57 ` sh emulation POSIX non-conformances (Was: [PATCH] Document imperfections in POSIX/sh compatibility) Stephane Chazelas
2021-04-11 18:13 ` Bart Schaefer
2021-04-11 19:18 ` sh emulation POSIX non-conformances (no word splitting upon arithmetic expansion) Stephane Chazelas
2021-04-22 15:03 ` Vincent Lefevre
2021-04-22 18:27 ` Bart Schaefer
2021-04-11 19:31 ` sh emulation POSIX non-conformances ("inf"/"Inf" in arithmetic expressions) Stephane Chazelas
2021-04-12 20:41 ` Bart Schaefer
2021-04-13 7:17 ` Stephane Chazelas
2021-04-22 15:31 ` Vincent Lefevre
2021-04-22 18:55 ` Bart Schaefer
2021-04-22 20:45 ` Daniel Shahaf
2021-04-22 21:25 ` Bart Schaefer
2021-04-23 16:45 ` Vincent Lefevre
2021-04-23 20:31 ` Bart Schaefer
2021-04-23 22:46 ` Oliver Kiddle
2021-04-23 23:34 ` Bart Schaefer
2021-04-24 2:10 ` Daniel Shahaf
2021-04-24 3:42 ` Bart Schaefer
2021-04-24 7:33 ` Stephane Chazelas
2021-04-24 16:04 ` Bart Schaefer
2021-04-24 23:02 ` Vincent Lefevre
2021-04-25 2:18 ` Bart Schaefer
2021-04-25 20:17 ` Vincent Lefevre
2021-04-25 21:58 ` Bart Schaefer
2021-04-26 10:28 ` Vincent Lefevre
2021-04-25 22:00 ` Bart Schaefer
2021-04-26 10:34 ` Vincent Lefevre
2021-04-26 23:25 ` Vincent Lefevre
2021-04-11 19:33 ` sh emulation POSIX non-conformances (some of zsh's special variables) Stephane Chazelas
2021-04-11 19:42 ` sh emulation POSIX non-conformances (printf %10s and bytes vs character) Stephane Chazelas
2021-04-13 15:57 ` Daniel Shahaf
2021-04-13 18:03 ` Stephane Chazelas
2021-04-13 21:09 ` Bart Schaefer
2021-04-22 13:59 ` Vincent Lefevre
2021-04-22 14:28 ` Vincent Lefevre
2021-04-22 19:22 ` Bart Schaefer
2021-04-23 16:53 ` Vincent Lefevre
2021-04-23 23:01 ` Oliver Kiddle
2021-04-24 21:41 ` Vincent Lefevre
2021-04-24 21:46 ` Vincent Lefevre
2021-04-24 7:09 ` Stephane Chazelas
2021-04-24 21:52 ` Vincent Lefevre
2021-04-24 22:28 ` Bart Schaefer
2021-04-24 23:18 ` Vincent Lefevre
2021-04-25 2:20 ` Bart Schaefer
2021-04-25 11:07 ` Vincent Lefevre
2021-04-11 23:04 ` [PATCH] Document imperfections in POSIX/sh compatibility dana
2021-04-13 16:01 ` Daniel Shahaf
2021-04-13 16:12 ` Peter Stephenson
2021-04-13 20:28 ` Oliver Kiddle
2021-04-13 21:40 ` dana
2021-04-13 22:02 ` Bart Schaefer
2021-04-14 12:38 ` Daniel Shahaf
2021-04-18 4:50 ` dana
2021-04-20 21:26 ` Daniel Shahaf
2021-05-03 23:42 ` dana
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=F56FD538-0428-4D03-BBE2-6E53154EC0EA@dana.is \
--to=dana@dana.is \
--cc=schaefer@brasslantern.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).