From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Greg Hill <gregoryohill@gmail.com>
Subject: Re: Maintenance of *info* documentation of Emacs/Elisp
Date: Sun, 23 Feb 2020 22:38:45 -0500 [thread overview]
Message-ID: <CAM-tV-_ZpXAGtYFQ1wFauN9=ZD1XfO5U3O=c-TPhx9G-orbVWg@mail.gmail.com> (raw)
In-Reply-To: <a223c985-f0ad-49cb-9f6d-4c79aa6d9163@default>
On Sun, 23 Feb 2020 at 20:00, Drew Adams <drew.adams@oracle.com> 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.
>
> 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.
It seems to be #39624 which is currently closed, but most of the
discussion happened off-list. I'm sure concrete suggestions for
improving the docs would be welcome there though.
https://debbugs.gnu.org/39624
prev parent reply other threads:[~2020-02-24 3:38 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
2020-02-24 3:38 ` Noam Postavsky [this message]
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='CAM-tV-_ZpXAGtYFQ1wFauN9=ZD1XfO5U3O=c-TPhx9G-orbVWg@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=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.
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.