From: Jean Louis <bugs@gnu.support>
To: uzibalqa <uzibalqa@proton.me>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Moving through options with completing read
Date: Fri, 12 Aug 2022 09:02:46 +0300 [thread overview]
Message-ID: <YvXtBm98XP5rWnKx@protected.localdomain> (raw)
In-Reply-To: <PF2asb5VDbTC7JTIXLdZwQO92SYLj1g06bYGHpbYRGa9XY6OLe-JdVMucplvLnBtpojHdtvJ-EehsSfB4CgKwf86-KfkkV1E_8InTbaegCc=@proton.me>
* uzibalqa via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-08-12 00:56]:
> I am using `completing-read'. The way to go through options in using
> the arrow keys, right?
1. If I am already very acquainted with what I am expected to write
during `completing-read' function and there was some previous entry
which is remembered in history, then I would usually just search
for the previous entry by using M-p or M-n
2. If there was no previous history, and I am very acquainted with it,
I would then start typing an entry and press TAB to expand it.
3. If I am not acquainted with what I am expected to enter then I
press TAB to see possible completion. This is often the case even
with my own programs.
To make the function `completing-read' more visual or interactive
depending of personal preferences, one can turn on `helm-mode` or
`ivy-mode' or similar. However, after extensively using those special
completion modes I have found out that I work more efficient with the
Emacs standard completion.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-08-12 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 21:55 Moving through options with completing read uzibalqa via Users list for the GNU Emacs text editor
2022-08-12 6:02 ` Jean Louis [this message]
2022-08-12 6:18 ` uzibalqa
2022-08-12 21:47 ` Michael Heerdegen
2022-08-12 21:54 ` uzibalqa
2022-08-12 23:49 ` Michael Heerdegen
2022-08-13 0:00 ` uzibalqa
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=YvXtBm98XP5rWnKx@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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).