From: Alan Mackenzie <acm@muc.de>
To: npostavs@users.sourceforge.net
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 25461@debbugs.gnu.org
Subject: bug#25461: [Patch #2]: Missing doc strings for "," and ",@".
Date: Tue, 24 Jan 2017 19:39:18 +0000 [thread overview]
Message-ID: <20170124193917.GA7358@acm> (raw)
In-Reply-To: <871svtumvz.fsf@users.sourceforge.net>
Hello, Noam.
On Mon, Jan 23, 2017 at 23:01:36 -0500, npostavs@users.sourceforge.net wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > I've hacked all this together. What used to be called a "reader macro"
> > is now a "reader construct".
> I think "read syntax" is better just because the manual already uses
> that term.
I think this is a very fine point. "Read syntax" tends to distract
attention from the semantics, I think.
> > +;; Give `,' and `,@' documentation strings which can be examined by C-h f.
> > +(put '\, 'function-documentation
> > + "See `\\=`' (also `pcase') for the details of `,'.")
> > +(put '\, 'reader-construct t)
> > +
> > +(put '\,@ 'function-documentation
> > + "See `\\=`' or `,' for the details of `,@'.")
> Linking from ",@" to "," seems a bit unhelpful, since "," hardly says
> anything and just links to "`".
Thanks, I actually spotted that and removed it before committing a patch
yesterday.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-01-24 19:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 21:22 bug#25461: Missing doc strings for "," and ",@" Alan Mackenzie
2017-01-17 19:34 ` Glenn Morris
2017-01-17 19:56 ` Alan Mackenzie
2017-01-17 20:36 ` Andreas Schwab
2017-01-17 20:41 ` Alan Mackenzie
2017-01-17 20:53 ` Andreas Schwab
2017-01-18 1:44 ` Michael Heerdegen
2017-01-18 19:28 ` Alan Mackenzie
[not found] ` <handler.25461.B.148460180922707.ack@debbugs.gnu.org>
2017-01-18 19:43 ` bug#25461: [Patch]: " Alan Mackenzie
2017-01-19 0:16 ` npostavs
2017-01-19 17:37 ` Alan Mackenzie
2017-01-19 18:10 ` Noam Postavsky
2017-01-19 18:36 ` Alan Mackenzie
2017-01-20 0:24 ` Michael Heerdegen
2017-01-19 2:23 ` Michael Heerdegen
2017-01-19 17:58 ` Alan Mackenzie
2017-01-20 0:12 ` Michael Heerdegen
2017-01-20 16:58 ` Alan Mackenzie
2017-01-21 2:26 ` Michael Heerdegen
2017-01-21 15:56 ` Alan Mackenzie
2017-01-21 20:46 ` bug#25461: [Patch #2]: " Alan Mackenzie
2017-01-24 1:58 ` Michael Heerdegen
2017-01-24 19:43 ` Alan Mackenzie
2017-01-24 4:01 ` npostavs
2017-01-24 19:39 ` Alan Mackenzie [this message]
2017-01-24 20:00 ` Noam Postavsky
2017-01-23 19:09 ` bug#25461: [Patch]: " Alan Mackenzie
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=20170124193917.GA7358@acm \
--to=acm@muc.de \
--cc=25461@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
/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).