From: Philipp Stephani <p.stephani2@gmail.com>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>,
"Philipp Stephani" <phst@google.com>,
"Emacs development discussions" <emacs-devel@gnu.org>
Subject: Re: module documentation draft
Date: Thu, 28 Sep 2017 20:25:11 +0000 [thread overview]
Message-ID: <CAArVCkQCQmsF1voQq5MnOv9rnr=k63hMOgZzmrKnb9U68LBhZw@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkSsg0_1g=dZAtVmeoHRAD5whXHKCWoeBvYB5=F6+4h70w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Philipp Stephani <p.stephani2@gmail.com> schrieb am So., 23. Juli 2017 um
20:57 Uhr:
> Aurélien Aptel <aurelien.aptel@gmail.com> schrieb am Mo., 24. Apr. 2017
> um 19:05 Uhr:
>
>> Hi,
>>
>> ~6 months ago I started writing some doc for modules. Some things have
>> changed since then it seems (Philipp last message about
>> make_global_ref seems to mention something I thought was removed..
>> hrm..)
>>
>> But it could be a good starting point. Look for XXX.
>>
>
> Thanks! I've also finally managed to get my draft online:
> https://phst.github.io/emacs-modules
> It's more specification-like and hopefully covers most of the behavior of
> the module API.
>
It would be great if we could have comprehensive documentation in the ELisp
manual in Emacs 26. So it would be great if others (especially the
maintainers) could review these two documents. Please focus on the content
during the first pass, not on stylistic or editorial issues.
[-- Attachment #2: Type: text/html, Size: 1646 bytes --]
next prev parent reply other threads:[~2017-09-28 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 17:04 module documentation draft Aurélien Aptel
2017-07-23 18:57 ` Philipp Stephani
2017-07-25 12:50 ` Aurélien Aptel
2017-09-28 20:25 ` Philipp Stephani [this message]
2017-09-28 21:51 ` Aurélien Aptel
2017-09-29 16:45 ` Eli Zaretskii
2017-09-29 16:49 ` Aurélien Aptel
2017-09-29 18:08 ` Eli Zaretskii
2017-09-29 20:39 ` Philipp Stephani
2017-09-29 21:03 ` Eli Zaretskii
2017-12-26 21:06 ` Philipp Stephani
2018-10-11 18:01 ` Eli Zaretskii
2018-10-14 15:47 ` Basil L. Contovounesios
2018-10-14 16:14 ` Eli Zaretskii
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='CAArVCkQCQmsF1voQq5MnOv9rnr=k63hMOgZzmrKnb9U68LBhZw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=aurelien.aptel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=phst@google.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).