From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"Charles A. Roelli" <charles@aurox.ch>,
"26513@debbugs.gnu.org" <26513@debbugs.gnu.org>
Subject: bug#26513: [External] : bug#26513: 25.2; pop-up-frames and *Completions* buffer
Date: Sun, 20 Feb 2022 21:16:10 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488530117CF35FB9466D575F3399@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <0bd1707e-9f47-2c49-5af0-836119ac4438@gmx.at>
> > Wrt frame focus problems stemming from some
> > window mgrs focusing a new frame etc.: I wonder
> > whether it might help (in the case of dedicated
> > frames) to pre-create the relevant frames such
> > as *Completions*, and instead of deleting them
> > and re-creating them, make them invisible and
> > show them again.
>
> It might be worth pursuing such an approach. Provided we can convince a
> sufficiently large number of WMs to not auto-focus a frame when making
> it visible.
;-)
(I didn't realize that they do that.)
next prev parent reply other threads:[~2022-02-20 21:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 9:17 bug#26513: 25.2; pop-up-frames and *Completions* buffer Charles A. Roelli
2017-04-15 14:50 ` martin rudalics
2017-04-15 19:14 ` Charles A. Roelli
2017-04-15 19:40 ` martin rudalics
2017-04-15 20:28 ` Charles A. Roelli
2017-04-16 7:16 ` martin rudalics
2017-04-17 7:44 ` Charles A. Roelli
2017-04-15 16:49 ` Drew Adams
2017-04-15 20:05 ` Charles A. Roelli
2017-04-16 15:54 ` Drew Adams
2017-04-18 17:27 ` martin rudalics
2017-04-18 20:34 ` Charles A. Roelli
2017-04-19 7:26 ` martin rudalics
2022-02-15 10:37 ` Lars Ingebrigtsen
2022-02-17 10:01 ` martin rudalics
2022-02-17 13:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 16:02 ` martin rudalics
2022-02-17 19:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-19 9:40 ` martin rudalics
2022-02-19 12:23 ` Eli Zaretskii
2022-02-20 0:25 ` bug#26513: [External] : " Drew Adams
2022-02-20 0:28 ` Drew Adams
2022-02-20 9:17 ` martin rudalics
2022-02-20 21:16 ` Drew Adams [this message]
2022-02-21 16:25 ` Drew Adams
2022-02-17 16:40 ` Drew Adams
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=SJ0PR10MB5488530117CF35FB9466D575F3399@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=26513@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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 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).