From: Heime <heimeborgia@protonmail.com>
To: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Using completing-read efficiently
Date: Sat, 19 Aug 2023 02:54:45 +0000 [thread overview]
Message-ID: <coZabUWA16emn5gGR87NAlJJjxMw-vHFG73stlJVxrtu7pgcwl79woTLwhGiPArZaqhGALCFnLFhVEyR9IUOrzQd3gPGqKGU-NPEXhuhe24=@protonmail.com> (raw)
Have been using completing-read in the following way.
I customarily cycle through the COLLECTION items by repeating <down>.
Having been pointed out to me that cycling is not an efficient
way to get to something, I would like to try new ways.
One suggestion has been to sort completion candidates to tame dumb cycling.
Being able to filter them is another.
Would I need to change the code for sorting and filtering ? It would be good
to have some instructions on how to use such things in practice.
Another aspect has been completion against the history. I know absolutely
nothing about history, though.
(interactive
(list
(let ( (cseq '("EXTEN" "DISAB" "TABTR")) )
(completing-read " Changeling: " cseq nil t "TABTR"))))
next reply other threads:[~2023-08-19 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:54 Heime [this message]
2023-08-19 20:38 ` [External] : Using completing-read efficiently Drew Adams
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='coZabUWA16emn5gGR87NAlJJjxMw-vHFG73stlJVxrtu7pgcwl79woTLwhGiPArZaqhGALCFnLFhVEyR9IUOrzQd3gPGqKGU-NPEXhuhe24=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.
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).