From: Helmut Eller <eller.helmut@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 22539@debbugs.gnu.org
Subject: bug#22539: 25.1.50; C-x o should switch to *Completions*
Date: Wed, 03 Feb 2016 11:04:52 +0100 [thread overview]
Message-ID: <m2h9hqp0sb.fsf@gmail.com> (raw)
In-Reply-To: <mvmoaby6swj.fsf@hawking.suse.de> (Andreas Schwab's message of "Wed, 03 Feb 2016 10:32:28 +0100")
On Wed, Feb 03 2016, Andreas Schwab wrote:
>> It would be more convenient if C-x o in step 3 would switch to the
>> *Completions* buffer.
>
> That's what M-v (switch-to-completions) does.
Another one I didn't know. Thanks.
Helmut
prev parent reply other threads:[~2016-02-03 10:04 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
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 [this message]
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=m2h9hqp0sb.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=22539@debbugs.gnu.org \
--cc=schwab@suse.de \
/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).