From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: wilnerthomas@tutanota.com, 57423@debbugs.gnu.org
Subject: bug#57423: Completions Buffer requiring window switching or mouse activity
Date: Fri, 26 Aug 2022 07:15:29 +0000 [thread overview]
Message-ID: <65MRhyP1F--AfjJc_H2fIFFQn7A1YZYRNp3jsv9e_e8KY5fVl4a2DVwSrN4kj4Y6zpwCltO1csSo381ZE03SSPLxRBbz6ng4-l_195scrgw=@proton.me> (raw)
In-Reply-To: <831qt332uj.fsf@gnu.org>
------- Original Message -------
On Friday, August 26th, 2022 at 7:01 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 26 Aug 2022 06:21:37 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: wilnerthomas@tutanota.com, 57423@debbugs.gnu.org
> >
> > > . in Emacs 29, you can type M-<UP> and M-<DOWN> arrow keys to select
> > >
> > > the candidates
> >
> > So I get to see one by one in the minibuffer itself before hitting RET?
>
>
> Yes.
>
> > > > An effective way that improves the frequent minibuffer activity (e.g. icomplete lets user
> > > > select a completion without having to smitch windows), emacs can automatically switch
> > > > to the completions buffer so one can get to a possible selection using the arrow keys.
> > >
> > > In Emacs 29, there's a new variable 'completion-auto-select', which
> > > does precisely that.
> >
> > Sounds sufficient.
>
>
> So can this bug be closed as resolved?
Yes
next prev parent reply other threads:[~2022-08-26 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 1:18 bug#57423: Completions Buffer requiring window switching or mouse activity wilnerthomas--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 6:09 ` Eli Zaretskii
2022-08-26 6:21 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 7:01 ` Eli Zaretskii
2022-08-26 7:15 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-26 10:31 ` 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='65MRhyP1F--AfjJc_H2fIFFQn7A1YZYRNp3jsv9e_e8KY5fVl4a2DVwSrN4kj4Y6zpwCltO1csSo381ZE03SSPLxRBbz6ng4-l_195scrgw=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=57423@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=uzibalqa@proton.me \
--cc=wilnerthomas@tutanota.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).