From: Bob Newell <bobnewell@bobnewell.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation is bad
Date: Sun, 9 Sep 2018 18:13:17 -1000 [thread overview]
Message-ID: <CADoYgq_d0emg97bd+hBFdjHFtQ2dLxMzg-YRxz4gBDVeofGTdQ@mail.gmail.com> (raw)
In-Reply-To: <CAEU3wuUSNGEQ+OVc9wF8t_Jc9Kzob8EZTTRdzDO_TdoUtm29iQ@mail.gmail.com>
On Sun, Sep 9, 2018 at 4:26 AM, John Stone <johnrstone2011@gmail.com> wrote:
> don't fix the broken the docs then, we'll use a different lisp for this
> project
Please do!
The people on this mailing list are polite, knowledgeable, and
helpful, and represent the best aspects of the free open-source
software community. They share their limited time and extensive
expertise out of a willingness to help others and to give something to
the community.
These are people who deserve our respect and appreciation, and, at a
bare minimum, common courtesy and politeness.
--
Bob Newell
Honolulu, Hawai`i
Via Linux/Emacs/Gnus/BBDB.
next prev parent reply other threads:[~2018-09-10 4:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 1:46 Emacs documentation is bad John Stone
2018-09-09 1:48 ` John Stone
2018-09-09 1:49 ` John Stone
2018-09-09 13:34 ` tomas
2018-09-09 14:26 ` John Stone
2018-09-10 4:13 ` Bob Newell [this message]
2018-09-10 8:54 ` Van L
[not found] ` <mailman.577.1536552821.1284.help-gnu-emacs@gnu.org>
2018-09-12 20:06 ` Emanuel Berg
2018-09-12 22:08 ` Emanuel Berg
[not found] ` <mailman.555.1536503215.1284.help-gnu-emacs@gnu.org>
2018-09-09 21:33 ` Barry Fishman
2018-09-09 21:39 ` Noam Postavsky
[not found] ` <mailman.570.1536529199.1284.help-gnu-emacs@gnu.org>
2018-09-09 22:10 ` Barry Fishman
[not found] ` <mailman.548.1536497190.1284.help-gnu-emacs@gnu.org>
2018-09-09 21:10 ` Ben Bacarisse
2018-09-09 21:22 ` tomas
2018-09-09 21:38 ` Barry Fishman
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=CADoYgq_d0emg97bd+hBFdjHFtQ2dLxMzg-YRxz4gBDVeofGTdQ@mail.gmail.com \
--to=bobnewell@bobnewell.net \
--cc=help-gnu-emacs@gnu.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.
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).