From: "Drew Adams" <drew.adams@oracle.com>
To: Nordlöw <per.nordlow@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Hints about the choices in completing-read-multiple (in crm.el)
Date: Fri, 18 Jan 2008 07:21:43 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAENHEEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <324e57d6-308c-4dac-a4ab-2bfbb0f52a38@1g2000hsl.googlegroups.com>
> I am currently building functions for searching, replacing and C/C++
> refactorings. In these I have found the *efficiency* in using
> completing-read-mutliple() of sets of gcc-functions/types/attributes,
> file-types/groups really usable. I would however like to extend its
> logic a bit so that the user can get a small explanation/documentation
> about a specific choice in a pre-specificied multiple-value-doc-set.
> Any tips?
Could you be more specific? Perhaps give an example of what you would like.
prev parent reply other threads:[~2008-01-18 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 14:04 Hints about the choices in completing-read-multiple (in crm.el) Nordlöw
2008-01-18 15:21 ` Drew Adams [this message]
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=DNEMKBNJBGPAOPIJOOICAENHEEAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=per.nordlow@gmail.com \
/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.
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).