From: Drew Adams <drew.adams@oracle.com>
To: Greg Hill <gregoryohill@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Maintenance of *info* documentation of Emacs/Elisp
Date: Sun, 23 Feb 2020 16:59:56 -0800 (PST) [thread overview]
Message-ID: <a223c985-f0ad-49cb-9f6d-4c79aa6d9163@default> (raw)
In-Reply-To: <CADSjfO6-HT+eJv0G75xAa-YkZu050nPb-VZpiQMDHaG36RfBRA@mail.gmail.com>
> 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.
Perhaps you misunderstood. Or perhaps Steve meant that _he_ couldn't help with that. But that doesn't mean that someone else can't.
Is the bug you filed closed? If not then you can hope that someone will see it, agree about the problem, and have the time and will to fix it.
next prev parent reply other threads:[~2020-02-24 0:59 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
2020-02-24 0:59 ` Drew Adams [this message]
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
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=a223c985-f0ad-49cb-9f6d-4c79aa6d9163@default \
--to=drew.adams@oracle.com \
--cc=gregoryohill@gmail.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.
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).