From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Maintenance of *info* documentation of Emacs/Elisp
Date: Mon, 24 Feb 2020 01:58:56 +0100 [thread overview]
Message-ID: <877e0c7qcv.fsf@ebih.ebihd> (raw)
In-Reply-To: CADSjfO6-HT+eJv0G75xAa-YkZu050nPb-VZpiQMDHaG36RfBRA@mail.gmail.com
Greg Hill wrote:
> Thank you, Drew, but I tried reporting my
> problems with documentation like that as
> a "bug" first, got a reply from Steve Berman
> (actually we exchanged several emails, and he
> helped me out a lot with answers to a number
> of other non- "bug" questions I had while we
> were at it), and my understanding of what he
> told me about my suggestions re: improving
> the documentation was that he couldn't really
> help me with that, so I should probably take
> it to help-gnu-emacs.
The formally correct method to suggest
a hands-on improvement to Emacs documentation
is `report-emacs-bug', if you want to bring it
up on a mailing list, while it is certainly not
off topic here, probably it is better still to
bring it up at gmane.emacs.devel/emacs-devel
<emacs-devel@gnu.org>
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-02-24 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 19:46 Maintenance of *info* documentation of Emacs/Elisp Greg Hill
2020-02-23 20:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-02-23 20:18 ` Eli Zaretskii
2020-02-23 22:00 ` Drew Adams
2020-02-23 23:48 ` Greg Hill
2020-02-24 0:58 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-02-24 0:59 ` Drew Adams
2020-02-24 3:38 ` Noam Postavsky
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=877e0c7qcv.fsf@ebih.ebihd \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.