From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Ergus <spacibba@aol.com>,
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 10:54:48 +0200 [thread overview]
Message-ID: <87v9e5herj.fsf@mail.linkov.net> (raw)
In-Reply-To: <92f3cbd7-29a0-461a-a023-562bc6020ea8@default> (Drew Adams's message of "Sun, 15 Nov 2020 21:38:26 -0800 (PST)")
> Cycling is actually a fairly inefficient, unconscious
> way to navigate among candidates. It's handy, but
> dumb cycling shouldn't be the only or the main way to
> get around.
I agree. I tried the completions-highlight-modifications branch, but
unfortunately restricting a set of navigation keys limits the freedom of
using any navigation key for browsing completion candidates that is
available today. What I mean is that currently it's possible in the
minibuffer to type <PageUp> (switch-to-completions), and then all keys
are available for selecting a completion: arrow keys, page scrolling
keys - even completion drop-down combo in browser's address bar allows
page scrolling.
next prev parent reply other threads:[~2020-11-16 8:54 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 [this message]
2020-11-16 10:27 ` Ergus
2020-11-16 20:23 ` Juri Linkov
2020-11-16 21:16 ` Drew Adams
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
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=87v9e5herj.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).