all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Moving through options with completing read
Date: Sat, 13 Aug 2022 00:00:46 +0000	[thread overview]
Message-ID: <64tH8jdw75YBB1umbGrfWELv2W_bu-5tp4ZOu6NevBy6lvGFlEztTYby06Qmt6fuwMUkWbuzLiQnrATh2pOLeeXuSEtximlGzNsmKvIqkcE=@proton.me> (raw)
In-Reply-To: <87pmh5nhsx.fsf@web.de>


------- Original Message -------
On Friday, August 12th, 2022 at 11:49 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:


> uzibalqa uzibalqa@proton.me writes:
>
> > No. I am saying that some argue that TAB cycles through the options,
> > but if one goes to try it, it does not work like that.
>
>
> Does not work like what? Or not at all?
>
> > But I can do it using the arrow keys. But the manual does not explain
> > that the arrow keys can be used to iterate through the options
> > provided by completing-read.
>
>
> Arrow keys cycle through the history, see
> (info "(emacs) Minibuffer History")
>
> The future history depends on the context. It will not always just be
> the list of completion candidates.
>
> Michael.

Have not been focusing on minibuffer history, but minibuffer option cycling for completing-read, which is not based on history.



      reply	other threads:[~2022-08-13  0:00 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='64tH8jdw75YBB1umbGrfWELv2W_bu-5tp4ZOu6NevBy6lvGFlEztTYby06Qmt6fuwMUkWbuzLiQnrATh2pOLeeXuSEtximlGzNsmKvIqkcE=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.