From: Eli Zaretskii <eliz@gnu.org>
To: Bryce Carson <bovine@cyberscientist.ca>,
Mauro Aranda <maurooaranda@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Community improvements to the Emacs Widget Library manual?
Date: Sun, 09 Jul 2023 08:26:04 +0300 [thread overview]
Message-ID: <83sf9xbqqb.fsf@gnu.org> (raw)
In-Reply-To: <1e042c59-9baf-ee4f-4726-26aba36847d4@cyberscientist.ca> (message from Bryce Carson on Sat, 8 Jul 2023 14:18:21 -0600)
> Date: Sat, 8 Jul 2023 14:18:21 -0600
> From: Bryce Carson <bovine@cyberscientist.ca>
>
> Would anyone like to collaborate to improve The Emacs Widget Library manual? Are there any active
> Emacs Lisp hackers that actually understand this library at a deep level?
I think Mauro (CC'ed) is our widget expert.
> The Emacs Widget Library manual could use a re-write, preferably following the Diataxis
> documentation framework if possible. Does anyone want to collaborate over the long-term, creating a
> study group and editing the manual to a high standard to benefit the community and ourselves?
I don't think I understand the plan in this aspect. If important
information is missing from the manual, it can and should be added.
If you want to add tutorial-style sections, that could also be a good
idea, provided that the subject is so complex that reading the main
description is too hard without first reading a tutorial introduction.
If this is what you mean here, it is, of course, very welcome. But
the general idea of the existing manual, which is to describe both the
user-facing UI and the Lisp-level reference, is correct, IMO.
next prev parent reply other threads:[~2023-07-09 5:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 20:18 Community improvements to the Emacs Widget Library manual? Bryce Carson
2023-07-09 5:26 ` Eli Zaretskii [this message]
2023-07-09 12:02 ` Mauro Aranda
2023-07-09 12:16 ` Eli Zaretskii
2023-07-11 0:52 ` Bryce
2023-07-12 12:30 ` Eli Zaretskii
2023-07-12 16:42 ` Corwin Brust
2023-07-13 23:05 ` Bryce Carson
2023-07-13 23:27 ` [External] : " Drew Adams
2023-07-13 23:57 ` Bryce Carson
2023-07-10 3:38 ` Michael Heerdegen
2023-07-11 23:17 ` Bryce
2023-07-12 5:18 ` Michael Heerdegen
2023-07-12 7:21 ` Bryce
2023-07-13 2:59 ` Michael Heerdegen
2023-07-11 11:04 ` Kjartan Oli Agustsson
2023-07-14 2:02 ` Richard Stallman
2023-07-14 5:28 ` Bryce Carson
-- strict thread matches above, loose matches on Subject: below --
2023-07-09 12:17 Mauro Aranda
2023-07-12 4:07 ` Bryce
2023-07-12 11:34 ` Mauro Aranda
2023-07-13 3:30 ` Michael Heerdegen
2023-07-23 23:06 ` Bryce
2023-07-24 11:37 ` Eli Zaretskii
2023-07-12 11:43 Mauro Aranda
2023-07-12 20:17 ` Bryce
2023-07-14 6:32 ` Bryce Carson
2023-07-14 6:52 ` Bryce Carson
2023-07-14 6:56 ` Bryce Carson
2023-07-14 6:59 ` Bryce Carson
2023-07-14 7:07 ` Bryce Carson
2023-07-14 14:41 ` Mauro Aranda
2023-07-14 18:50 ` bovine
2023-07-15 0:08 ` Mauro Aranda
2023-07-14 10:48 ` Mauro Aranda
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=83sf9xbqqb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bovine@cyberscientist.ca \
--cc=emacs-devel@gnu.org \
--cc=maurooaranda@gmail.com \
/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.