unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: pcase docs
Date: Thu, 14 Jan 2016 21:47:57 +0200	[thread overview]
Message-ID: <83a8o8gcya.fsf@gnu.org> (raw)

Would people who expressed  the desire and intent of contributing
better documentation for pcase please consider doing that in the next
few days?  The initial documentation effort for v21.5 is almost
complete, and we will have our first pretest shortly, so it would be
good to have this item covered when the pretest comes out.

If you are not comfortable with Texinfo, don't bother about the
markup: adding that is a simple job, and I can easily do it.  It's
coming up with good content that takes most of the documentation
effort.

While at that, please also recommend which part(s) of this NEWS entry
needs to be reflected in the ELisp manual:

  ** pcase
  *** New UPatterns `quote', `app', `cl-struct', `eieio', `seq', and `map'.
  *** New UPatterns can be defined with `pcase-defmacro'.

Thanks.



             reply	other threads:[~2016-01-14 19:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 19:47 Eli Zaretskii [this message]
2016-01-22 18:07 ` pcase docs John Wiegley
2016-01-22 19:46   ` Michael Heerdegen
2016-01-22 19:58     ` Michael Heerdegen
2016-01-22 21:30       ` Eli Zaretskii
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

  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=83a8o8gcya.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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 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).