From: Greg Hill <gregoryohill@gmail.com>
To: Drew Adams <drew.adams@oracle.com>, help-gnu-emacs@gnu.org
Subject: Re: Maintenance of *info* documentation of Emacs/Elisp
Date: Sun, 23 Feb 2020 15:48:04 -0800 [thread overview]
Message-ID: <CADSjfO6-HT+eJv0G75xAa-YkZu050nPb-VZpiQMDHaG36RfBRA@mail.gmail.com> (raw)
In-Reply-To: <b2549037-c8e0-4837-aedc-1c9bb1e83d54@default>
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.
On Sun, Feb 23, 2020 at 2:02 PM Drew Adams <drew.adams@oracle.com> wrote:
> > is there someone who is in charge of keeping the *info*
> > documentation up to date, to whom I could make occasional suggestions
> about
> > how it could be improved with just a little tweak, like by adding one
> > sentence here or there?
>
> It's great that you have specific suggestions for
> improving Emacs doc.
>
> For any Emacs Info manual, use `M-x report-emacs-bug'
> to report a problem or to suggest an improvement.
> That will guide you through preparing and sending a
> reporting email to Emacs developers, who will take a look.
>
>
>
next prev parent reply other threads:[~2020-02-23 23:48 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 [this message]
2020-02-24 0:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=CADSjfO6-HT+eJv0G75xAa-YkZu050nPb-VZpiQMDHaG36RfBRA@mail.gmail.com \
--to=gregoryohill@gmail.com \
--cc=drew.adams@oracle.com \
--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.
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.