all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Ergus <spacibba@aol.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: feature/completions-highlight-modifications e3c5b99 3/6: Add completions-highlight-mode initial implementation.
Date: Mon, 16 Nov 2020 13:16:37 -0800 (PST)	[thread overview]
Message-ID: <18fb5d5b-d62b-4961-899c-ae011c982a66@default> (raw)
In-Reply-To: <877dql59v0.fsf@mail.linkov.net>

> Sorry, I was not clear enough: I meant that the new feature doesn't
> allow in the minibuffer using the same navigation keys that are
> already available in the *Completions* buffer, e.g. <PgDown> and <PgUp>
> typed in the *Completions* buffer scroll it up and down.
> 
> For example, while in the minibuffer type 'TAB' that displays a very
> long list of completions, then type 'C-M-v', and see how it scrolls the
> *Completions* buffer.  Better yet try typing <M-PgDown> and <M-PgUp>
> in the minibuffer, and see how it scrolls the *Completions* buffer
> up and down.  I meant that a new feature could allow such page
> scrolling without the 'M-' modifier, by just using <PgDown> and <PgUp>
> in the minibuffer (and C-v/M-v as well) to scroll the *Completions* buffer.

(By <PgDown> and <PgUp> I assume you really mean
the logical keys <next> and <prior>.)

I hope that you don't choose keys such as <next>
and <prior> for this.  Or <home> and <end>.

Such pairs are useful for other things.  Icicles
uses those two pairs of keys for cycling different
kinds of matches, for instance.

> (and C-v/M-v as well)

And I especially hope we don't assign _multiple_
pairs for this scrolling.  Icicles uses `C-v' and
`M-v' for it.  Aren't those two keys sufficient?
Why multiply things, here, reducing key binding
possibilities for other purposes?
___

Yes, I know that Emacs binds both pairs, C-v/M-v
and next/prior, in general.  But that was done
long ago, when keys were not so precious.  I'd
prefer that `next' and `prior' were left free of
any default key bindings.

I feel the same about C-e/C-b and end/home, FWIW.

I know that many applications outside Emacs use
end/home and next/prior for movement.  But I don't
think it's great that Emacs does that by default.

I do feel differently about C-n/C-p and down/up.
But I think that users outside Emacs are _much_
more likely to expect the arrow keys to move
down/up than they are to have strong expectations
about end/home and next/prior.



  reply	other threads:[~2020-11-16 21:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201115023629.19537.77471@vcs0.savannah.gnu.org>
     [not found] ` <20201115023631.C78AB20A27@vcs0.savannah.gnu.org>
2020-11-15 18:41   ` feature/completions-highlight-modifications e3c5b99 3/6: Add completions-highlight-mode initial implementation Stefan Monnier
2020-11-15 22:49     ` Ergus
2020-11-15 23:32       ` Stefan Monnier
2020-11-16  3:37         ` Ergus
2020-11-16  3:56           ` Stefan Monnier
2020-11-16  5:40             ` Drew Adams
2020-11-16  7:39             ` Ergus
2020-11-16  5:38           ` Drew Adams
2020-11-16  8:54             ` Juri Linkov
2020-11-16 10:27               ` Ergus
2020-11-16 20:23                 ` Juri Linkov
2020-11-16 21:16                   ` Drew Adams [this message]
2020-11-17  0:46                   ` Ergus
2020-11-17 20:02                     ` Juri Linkov
2020-11-17 20:52                       ` Drew Adams
2020-11-18 19:43                 ` Juri Linkov
2020-11-18 22:45                   ` Drew Adams
2020-11-19  3:25                   ` Ergus
2020-11-19  7:45                     ` Juri Linkov
2020-11-19 10:50                       ` Ergus
2020-11-20  9:32                         ` Juri Linkov
     [not found]                           ` <20201120145248.wmbv2zgbvs7bg25i@Ergus>
2020-11-21 19:30                             ` Juri Linkov
2020-11-22 13:28                               ` Ergus
2020-11-22 20:03                                 ` Juri Linkov
2020-11-22 23:09                               ` Ergus
2020-11-23  9:14                                 ` Juri Linkov
2020-11-23 11:46                                   ` Ergus
2020-11-23 14:13                                     ` Jean Louis
2020-11-23 19:12                                       ` Eli Zaretskii
2020-11-23 19:44                                         ` Jean Louis
2020-11-23 20:54                                     ` Dmitry Gutov
2020-11-23 23:27                                       ` Ergus via Emacs development discussions.
2020-12-10  1:16                                         ` Dmitry Gutov
2020-12-10  8:23                                           ` Juri Linkov
2020-11-25  8:49                                     ` Juri Linkov
2020-11-20 14:24                         ` Stefan Monnier
     [not found]                           ` <20201120144940.p55brblxpuowslag@Ergus>
2020-11-20 15:15                             ` Stefan Monnier
2020-11-16 16:03               ` Drew Adams
2020-11-16 20:28                 ` Juri Linkov
2020-11-16 21:31                   ` Drew Adams
2020-11-18 19:30                   ` Juri Linkov

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=18fb5d5b-d62b-4961-899c-ae011c982a66@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=spacibba@aol.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.
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.