From: Stefan Kangas <stefan@marxist.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 36206@debbugs.gnu.org
Subject: bug#36206: [PATCH] Change `user-error' docstring from "pilot error" to "user error"
Date: Sun, 23 Jun 2019 17:41:02 +0200 [thread overview]
Message-ID: <CADwFkmkX0n9x4bQR7V0bBF97B9zSXuikgTy3yH1t7Vg2zT5A7g@mail.gmail.com> (raw)
In-Reply-To: <71cf083c-441c-6e94-772a-68550161b455@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu> writes:
> Although it appears that the proposal has
> substantial support, some reviewers like the phrase "pilot error". So I propose
> the attached additional patch, which keeps the phrase "pilot error" and says
> that it means the same thing as "user error" - a point that will help people
> unfamiliar with the term "pilot error".
Thank you. This is a good compromise and in my opinion fully
sufficient to remove any confusion.
> This patch also takes the bikeshedding opportunity to improve the doc strings
> further by ordering them more logically and tightening up the wording.
This also looks like an improvement to me.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-06-23 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 11:09 bug#36206: [PATCH] Change `user-error' docstring from "pilot error" to "user error" Stefan Kangas
2019-06-14 13:13 ` Michael Albinus
2019-06-14 13:25 ` Stefan Kangas
2019-06-14 13:35 ` Michael Albinus
2019-06-14 13:51 ` Stefan Kangas
2019-06-14 14:08 ` Michael Albinus
2019-06-14 15:02 ` Drew Adams
2019-06-14 14:40 ` Juanma Barranquero
2019-06-15 3:33 ` Richard Stallman
2019-06-14 14:32 ` Drew Adams
2019-06-14 14:42 ` Dmitry Gutov
2019-06-14 19:15 ` Juri Linkov
2019-06-15 22:34 ` Juri Linkov
2019-06-23 0:39 ` Paul Eggert
2019-06-23 1:00 ` Noam Postavsky
2019-06-23 9:00 ` Michael Albinus
2019-06-27 9:37 ` Paul Eggert
2019-06-23 15:41 ` Stefan Kangas [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkX0n9x4bQR7V0bBF97B9zSXuikgTy3yH1t7Vg2zT5A7g@mail.gmail.com \
--to=stefan@marxist.se \
--cc=36206@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).