From: "Lawrence Velázquez" <larryv@zsh.org>
To: zeurkous@volny.cz
Cc: zsh-workers@zsh.org
Subject: Re: revised patch: zshmisc(1) clarify non-successful exit statuses
Date: Fri, 23 Apr 2021 16:39:45 -0400 [thread overview]
Message-ID: <fbc952c6-c458-498c-ab38-8c954296a0fc@www.fastmail.com> (raw)
In-Reply-To: <20210423222912.3060F674@volny.cz>
On Fri, Apr 23, 2021, at 4:29 PM, zeurkous@volny.cz wrote:
> YMMV -- especially the word "non-script" is awkward to me.
That final clause is admittedly difficult to express cleanly, and
I'm not completely pleased with my result. But "is not a script
and in a format unrecognized by the operating system" is ungrammatical
and shouldn't be committed as is.
Perhaps:
"The executable file has insufficient permissions, is a directory
or special file, or is not a script and is in a format unrecognized
by the operating system."
> But that's bikeshedding...
I don't consider grammar correction to be bikeshedding.
--
vq
next prev parent reply other threads:[~2021-04-23 20:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 12:15 zeurkous
2021-04-13 15:52 ` Daniel Shahaf
2021-04-13 18:03 ` zeurkous
2021-04-14 11:03 ` Daniel Shahaf
2021-04-14 11:40 ` zeurkous
2021-04-23 12:18 ` revised " zeurkous
2021-04-23 16:07 ` Daniel Shahaf
2021-04-23 16:15 ` Daniel Shahaf
2021-04-23 20:25 ` zeurkous
2021-04-23 20:14 ` Lawrence Velázquez
2021-04-23 20:29 ` zeurkous
2021-04-23 20:39 ` Lawrence Velázquez [this message]
2021-04-23 20:57 ` zeurkous
2021-04-23 20:51 ` Bart Schaefer
2021-04-23 21:03 ` zeurkous
2021-04-23 21:12 ` Bart Schaefer
2021-04-23 21:18 ` zeurkous
2021-04-23 22:31 ` Bart Schaefer
2021-04-26 16:25 ` zeurkous
2021-04-29 14:20 ` Daniel Shahaf
2021-05-09 19:04 ` Lawrence Velázquez
2021-05-31 1:09 ` Lawrence Velázquez
2021-05-31 4:09 ` Bart Schaefer
2021-05-31 4:37 ` Lawrence Velázquez
2021-06-30 17:51 ` zeurkous
2021-06-30 22:12 ` Lawrence Velázquez
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=fbc952c6-c458-498c-ab38-8c954296a0fc@www.fastmail.com \
--to=larryv@zsh.org \
--cc=zeurkous@volny.cz \
--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).