From: Richard Stallman <rms@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: stefan@marxist.se, michael.albinus@gmx.de, 36206@debbugs.gnu.org
Subject: bug#36206: [PATCH] Change `user-error' docstring from "pilot error" to "user error"
Date: Fri, 14 Jun 2019 23:33:27 -0400 [thread overview]
Message-ID: <E1hbzRX-00044c-5x@fencepost.gnu.org> (raw)
In-Reply-To: <CAAeL0SQA8DgsvKPMDuFm7Cpnf0xq=qdofHJsn47spJWJnZzxog@mail.gmail.com> (message from Juanma Barranquero on Fri, 14 Jun 2019 16:40:10 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I think "pilot error" is too jargony. We don't want to force people to
> look for unusual idioms in nerdy dictionaries while they're reading
> documentation. At least, not on purpose. And certainly looking for
> "pilot error" in Google will only add to their confusion.
> There's a place for clever. Documentation is not that place, IMHO.
I agree.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-06-15 3:33 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 [this message]
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=E1hbzRX-00044c-5x@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=36206@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=michael.albinus@gmx.de \
--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.