all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
	"jaime.escalante@gmx.com" <jaime.escalante@gmx.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	"48764@debbugs.gnu.org" <48764@debbugs.gnu.org>
Subject: bug#48764: [External] : bug#48764: mini-buffer completion
Date: Tue, 1 Jun 2021 21:31:09 +0000	[thread overview]
Message-ID: <SA2PR10MB44741591B784C894B7376BD9F33E9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87tumhia8g.fsf@tcd.ie>

> > Is there any information about basic navigation keys
> > for mini-buffer input in the manual?
> 
> Does the node (info "(emacs) Minibuffer History")[1] in the Emacs manual
> count?

FWIW, I wouldn't refer (or want Emacs to refer) to
keys that you use to cycle among history or default
elements (`M-(p|n)', `M-(r|s)') or cycle among
completion candidates (`<down>', `<up') as
"navigation keys" (basic or non-basic).

They are cycling keys.  Yes, they help you access
something, to choose it for some purpose.  So they
"get you to" something, in a way, but they're not
motion keys - they don't move point or the mouse
pointer etc.

Keys such as `M-f' navigate in the minibuffer.
Keys that cycle among choices don't.  It's clear
enough, I think, to refer to such keys as "cycling
keys".  It confuses things to refer to them as
navigation keys.

Yes, I realize that we also sometimes speak about
"navigating" when referring to using menus or
searching, etc., whether or not the end result is
moving the cursor.

But when talking about the minibuffer, where there
really are motion keys, I think it's clearer to
call such keys "cycling", not "navigation".

Just one opinion.





  parent reply	other threads:[~2021-06-01 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 20:16 bug#48764: mini-buffer completion jaime.escalante
2021-06-01 15:39 ` Lars Ingebrigtsen
2021-06-01 15:54   ` jaime.escalante
2021-06-01 20:46     ` Basil L. Contovounesios
2021-06-01 21:00       ` jaime.escalante
2021-06-01 22:50         ` Basil L. Contovounesios
2021-06-01 23:00           ` jaime.escalante
2021-06-01 21:04       ` jaime.escalante
2021-06-01 22:50         ` Basil L. Contovounesios
2021-06-01 23:04           ` jaime.escalante
2021-06-01 21:31       ` Drew Adams [this message]
2021-06-01 16:00   ` bug#48764: [External] : " Drew Adams
2021-06-01 16:06     ` jaime.escalante

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=SA2PR10MB44741591B784C894B7376BD9F33E9@SA2PR10MB4474.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=48764@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=jaime.escalante@gmx.com \
    --cc=larsi@gnus.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.
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.