From: Michael Heerdegen <michael_heerdegen@web.de>
To: 12884@debbugs.gnu.org
Subject: bug#12884: 24.2.50; defun*: argument lists in documentation look terrible
Date: Wed, 14 Nov 2012 22:51:09 +0100 [thread overview]
Message-ID: <87wqxnkg4y.fsf@web.de> (raw)
In-Reply-To: <jwvip980xz2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 Nov 2012 14:49:08 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > | (my-toggle-item #:MODE-OR-VAR &key ((:selected #:ENABLED-SPEC) (\`
> > | (am-bound-and-true-p (quote (\, mode-or-var))))) ((:help
> > | #:HELP-STRING) (am-make-symbol-docstring mode-or-var)))
>
> Let me just say that I will resist the urge to tell you what I think
> about this style of argument list ;-)
Please don't resist. What's wrong with it?
> > This looks terrible with all this #: and quote \, stuff.
>
> Binding print-quoted makes sense to improve the quote/backquote syntax.
> But I don't understand why we have those #: in there. I understand it's
> there to say the symbols are not interned, but I don't understand why
> they're not interned.
See `cl--make-usage-args'. It upcases the names of the arguments and
makes them a symbol again. The one who wrote that wanted that no new
symbols are interned, and so used `make-symbol'. Dunno if there's a
reason to do so.
- Michael.
next prev parent reply other threads:[~2012-11-14 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 16:47 bug#12884: 24.2.50; defun*: argument lists in documentation look terrible Michael Heerdegen
2012-11-14 19:49 ` Stefan Monnier
2012-11-14 21:51 ` Michael Heerdegen [this message]
2012-11-15 1:28 ` Stefan Monnier
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=87wqxnkg4y.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=12884@debbugs.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).