From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 36206@debbugs.gnu.org
Subject: bug#36206: [PATCH] Change `user-error' docstring from "pilot error" to "user error"
Date: Fri, 14 Jun 2019 15:13:00 +0200 [thread overview]
Message-ID: <87tvcsnwdf.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmnfc0+QAQX3D=e5SkCcLr31p0kD5xi9cWjV_AMkDfarUQ@mail.gmail.com> (Stefan Kangas's message of "Fri, 14 Jun 2019 13:09:06 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> The documentation of `user-error' says that it will "Signal a pilot
> error", which I personally find confusing. For starters, "pilot"
> could also mean "done as an experiment or test before being introduced
> more widely".
>
> It's more clear to say "user error". I don't have any data on this,
> but in my experience this is also more in line with how other
> programming languages names this class of errors.
Please don't change. "Pilot error" is a known term, see
<http://www.hacker-dictionary.com/terms/pilot-error>.
> Thanks,
> Stefan Kangas
Best regards, Michael.
next prev parent reply other threads:[~2019-06-14 13:13 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 [this message]
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
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=87tvcsnwdf.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=36206@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.