From: Eli Zaretskii <eliz@gnu.org>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>
Cc: phst@google.com, p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: module documentation draft
Date: Fri, 29 Sep 2017 21:08:10 +0300 [thread overview]
Message-ID: <83wp4h5qet.fsf@gnu.org> (raw)
In-Reply-To: <CA+5B0FPq5KhA_zxMFO-iknLTU9vJ37PQrJhE3Nhk9u=rJ6G-5g@mail.gmail.com> (message from Aurélien Aptel on Fri, 29 Sep 2017 18:49:59 +0200)
> From: Aurélien Aptel <aurelien.aptel@gmail.com>
> Date: Fri, 29 Sep 2017 18:49:59 +0200
> Cc: Philipp Stephani <p.stephani2@gmail.com>, Philipp Stephani <phst@google.com>,
> Emacs development discussions <emacs-devel@gnu.org>
>
> On Fri, Sep 29, 2017 at 6:45 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I already read this, when this was first announced in April.
> > Unfortunately, the style and the methodology of the description
> > differs significantly from what we use in the ELisp manual. So this
> > text will have to be reworked, and I didn't yet find time to do it.
>
> Eli, I believe you're talking about a different document. Philipp's
> documentation is much closer to a specification than a tutorial.
>
> https://phst.github.io/emacs-modules
No, I'm talking about this very document.
I won't argue with the "tutorial" part, but the point is the style
and the methodology of introducing the features there is very
different from what I expect of a chapter in the ELisp manual. Just
read some chapter or section which describes a single large feature,
and you will see the difference.
I don't mean to denigrate Philipp's work in any way, I'm just saying
that importing it into the ELisp manual needs some non-trivial work,
that's all.
next prev parent reply other threads:[~2017-09-29 18:08 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
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 [this message]
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=83wp4h5qet.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aurelien.aptel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--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).