From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: nvp <noah.v.peart@gmail.com>, 38502@debbugs.gnu.org
Subject: bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames
Date: Mon, 9 Dec 2019 21:07:03 -0800 (PST) [thread overview]
Message-ID: <e3a95898-f9f6-499a-8bee-71c4e8701d05@default> (raw)
In-Reply-To: <87lfrlrt8z.fsf@mail.linkov.net>
> >>> Is S-TAB referring to <backtab>? That is unbound (default) in this
> >>> context for me.
> >>
> >> Indeed there is no counterpart to TAB for scrolling the completion
> >> window in the opposite direction. Maybe <backtab> and S-TAB should
> >> do this.
> >
> > FWIW:
> >
> > I'd suggest that both TAB and S-TAB (<backtab>) be left
> > alone, as they are natural for completion in some way
> > (e.g. cycling among candidates).
>
> This is exactly what I meant - TAB cycles completions forward,
> so S-TAB could cycle backward.
Based on the Subject line and your speaking of
"scrolling the completion window" I thought you
meant scrolling the completion window. ;-)
By "cycling among candidates" I meant cycling
among candidates.
In vanilla Emacs I guess that means only what
`completion-cycle-threshold' offers. (With
other completion approaches it can mean other
ways of cycling among candidates.)
Anyway, just one opinion against binding S-TAB.
I'm in favor of leaving it open, for users and
libraries to bind during completion.
(Yes, they can do that even if Emacs gives it a
default binding. But I'm not a fan of Emacs
taking up all the oxygen wrt key bindings, as
seems to be more and more the case.)
As I say, just one opinion.
next prev parent reply other threads:[~2019-12-10 5:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 19:03 bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames noah
2019-12-05 19:16 ` Eli Zaretskii
2019-12-05 21:59 ` nvp
2019-12-06 0:02 ` Juri Linkov
2019-12-06 1:42 ` nvp
2019-12-08 21:11 ` Juri Linkov
2019-12-08 23:09 ` Drew Adams
2019-12-09 23:39 ` Juri Linkov
2019-12-10 5:07 ` Drew Adams [this message]
2019-12-06 7:37 ` martin rudalics
2019-12-06 8:04 ` nvp
2019-12-06 8:36 ` martin rudalics
2019-12-07 23:33 ` Juri Linkov
2019-12-08 8:58 ` martin rudalics
2019-12-08 22:20 ` Juri Linkov
2019-12-08 23:22 ` nvp
2019-12-08 23:23 ` nvp
2019-12-06 7:48 ` Eli Zaretskii
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=e3a95898-f9f6-499a-8bee-71c4e8701d05@default \
--to=drew.adams@oracle.com \
--cc=38502@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=noah.v.peart@gmail.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).