From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: [drew.adams@oracle.com: RE: Customize doc strings and tagstrings do not respect \\<...> and \\[...]]
Date: Mon, 27 Mar 2006 19:09:18 +0200 [thread overview]
Message-ID: <rjodzrizlt.fsf@sheridan.dina.kvl.dk> (raw)
In-Reply-To: DNEMKBNJBGPAOPIJOOICAEIDDDAA.drew.adams@oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
> Right. The manuals are silent on this, AFAICT. Call it a new feature request
> if you like.
>
> `(choice
> (const :tag ,(substitute-command-keys
> "`\\<minibuffer-local-map>\\[next-history-element]'.")
> tata)))
>
> Sure, that's OK too. But why not have it done implicitly?
Would you like 'message' to do an implicit substitute-command-keys as
well?
It is not a rhetorical question.
It doesn't seem intuitive to me that the value of :tag should be
considered a documentation string.
next prev parent reply other threads:[~2006-03-27 17:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 8:59 [drew.adams@oracle.com: RE: Customize doc strings and tag strings do not respect \\<...> and \\[...]] Richard Stallman
2006-03-04 14:57 ` Chong Yidong
2006-03-04 17:55 ` [drew.adams@oracle.com: RE: Customize doc strings and tagstrings " Drew Adams
2006-03-04 21:36 ` Andreas Schwab
2006-03-04 22:14 ` Drew Adams
2006-03-05 10:17 ` Andreas Schwab
2006-03-05 15:30 ` Drew Adams
2006-03-05 15:44 ` Andreas Schwab
2006-03-06 0:49 ` Richard Stallman
2006-03-06 13:13 ` Andreas Schwab
2006-03-06 22:48 ` Richard Stallman
2006-03-05 11:05 ` Andreas Schwab
2006-03-06 0:49 ` Richard Stallman
2007-02-15 11:44 ` Juanma Barranquero
2007-02-16 7:45 ` Richard Stallman
2007-02-16 9:49 ` Juanma Barranquero
2007-02-17 1:03 ` Richard Stallman
2007-02-17 1:23 ` Juanma Barranquero
2006-03-08 20:49 ` Kevin Rodgers
2006-03-08 21:28 ` Drew Adams
2006-03-27 17:09 ` Per Abrahamsen [this message]
2006-03-27 23:51 ` [drew.adams@oracle.com: RE: Customize doc strings andtagstrings " Drew Adams
2006-03-29 8:12 ` Richard Stallman
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=rjodzrizlt.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).