From: Helmut Eller <eller.helmut@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 22539@debbugs.gnu.org
Subject: bug#22539: 25.1.50; C-x o should switch to *Completions*
Date: Wed, 03 Feb 2016 09:24:04 +0100 [thread overview]
Message-ID: <m2powep5gb.fsf@gmail.com> (raw)
In-Reply-To: <56B1B450.5030702@gmx.at> (martin rudalics's message of "Wed, 03 Feb 2016 09:03:28 +0100")
On Wed, Feb 03 2016, martin rudalics wrote:
>> 1) start Emacs with: emacs -Q -f find-file
>> 2) press TAB two times so that the *Completions* buffer
>> becomes visible
>> 3) press C-x o
>>
>> the window with the *scratch* buffer is selected.
>>
>> It would be more convenient if C-x o in step 3 would switch to the
>> *Completions* buffer.
>
> The basic idea behind C-x o is that it cycles through all live windows
> before returning to the initially selected one. We could, in your
> special case, have ‘other-window’ select ‘other-window-for-scrolling’.
> But if we do so, we have to face the dilemma that the next C-x o gets us
> immediately back to the minibuffer window. This means that all other
> windows would get excluded from repeated invocations of C-x o.
>
> So I'm afraid that I cannot offer a practicable solution for this :-(
No big deal. I only noticed this because I had more than two windows
before doing a completion and in that case one has to type C-x o a lot
to to get to the *Completions* window.
A somewhat related question: Is there a command that cycles through the
windows in opposite direction as C-x o does? I noticed that
<C-iso-lefttab> is not bound by default so I could use that.
Helmut
next prev parent reply other threads:[~2016-02-03 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 21:37 bug#22539: 25.1.50; C-x o should switch to *Completions* Helmut Eller
2016-02-03 8:03 ` martin rudalics
2016-02-03 8:24 ` Helmut Eller [this message]
2016-02-03 9:08 ` martin rudalics
2016-02-03 9:14 ` Helmut Eller
2016-02-03 9:32 ` Andreas Schwab
2016-02-03 10:04 ` Helmut Eller
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=m2powep5gb.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=22539@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.