From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: jwiegley@gmail.com, emacs-devel@gnu.org
Subject: Re: pcase docs
Date: Fri, 22 Jan 2016 23:30:54 +0200 [thread overview]
Message-ID: <83wpr15mk1.fsf@gnu.org> (raw)
In-Reply-To: <87r3h95qs3.fsf@web.de> (message from Michael Heerdegen on Fri, 22 Jan 2016 20:58:06 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Fri, 22 Jan 2016 20:58:06 +0100
> Cc: emacs-devel@gnu.org
>
> And pcase-defmacro is intended for developers of (internal) packages
> like seq etc, so it must not have to be described broadly.
Since we don't have a separate "Emacs Lisp for Developers of Internal
Packages" manual, I don't see why we should omit these or describe
them in less detail. Otherwise, where would those developers learn
about the likes of pcase-defmacro?
next prev parent reply other threads:[~2016-01-22 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 19:47 pcase docs Eli Zaretskii
2016-01-22 18:07 ` John Wiegley
2016-01-22 19:46 ` Michael Heerdegen
2016-01-22 19:58 ` Michael Heerdegen
2016-01-22 21:30 ` Eli Zaretskii [this message]
2016-01-23 10:16 ` Michael Heerdegen
2016-01-23 11:43 ` Eli Zaretskii
2016-01-23 12:05 ` Michael Heerdegen
2016-01-23 13:35 ` Eli Zaretskii
2016-01-23 14:22 ` Michael Heerdegen
2016-01-23 14:50 ` Eli Zaretskii
2016-01-23 15:18 ` Michael Heerdegen
2016-01-24 8:50 ` Nicolas Petton
2016-01-23 15:51 ` Michael Heerdegen
2016-01-23 12:28 ` Alan Mackenzie
2016-01-23 13:13 ` Eli Zaretskii
2016-01-23 20:48 ` Drew Adams
2016-01-24 5:07 ` Stefan Monnier
2016-01-22 21:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wpr15mk1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=michael_heerdegen@web.de \
/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.