unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: "43672@debbugs.gnu.org" <43672@debbugs.gnu.org>
Subject: bug#43672: 28.0.50; select-frame-set-input-focus does not set focus first time called
Date: Thu, 21 Apr 2022 16:02:31 +0200	[thread overview]
Message-ID: <87wnfi4jrc.fsf@gnus.org> (raw)
In-Reply-To: <VI1PR06MB452610A27974623BD467AA5196010@VI1PR06MB4526.eurprd06.prod.outlook.com> (Arthur Miller's message of "Sun, 18 Oct 2020 16:10:44 +0200")

Arthur Miller <arthur.miller@live.com> writes:

>> If setting the parent in 'make-frame' works, then we can warn about
>> reparenting later possibly causing problems with focus transfer.  But
>> if
> Personally I can live with this, it is not problem for me; I reported
> mostly because I thought it was rather an odd behaviour. I understand
> it's a picky thing to debug.
>> But if
>> the problematic behavior occurs when you want to pop up an (already
>> existing but invisible) child menu frame on a different parent and give
>> the menu focus, I have no idea what to do.  So does the latter work for
>> you?
> I haven't come to that part yet :-). I just started to write a small
> eperiment, got into that one and reported, and haven't had time to go
> back to my experiment.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

This was a year ago -- skimming this bug report, it's unclear whether
there's anything to be done on the Emacs side here.  Is further progress
possible in this bug report?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-04-21 14:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 13:34 bug#43672: 28.0.50; select-frame-set-input-focus does not set focus first time called Arthur Miller
2020-09-28 13:57 ` Lars Ingebrigtsen
2020-09-28 14:11   ` Arthur Miller
2020-09-28 14:14     ` Lars Ingebrigtsen
2020-09-28 14:40       ` Arthur Miller
2020-09-29 13:46         ` Lars Ingebrigtsen
2020-09-29 14:34           ` martin rudalics
2020-09-29 14:44             ` Lars Ingebrigtsen
2020-09-29 20:43             ` Arthur Miller
2020-09-30  8:15               ` martin rudalics
2020-09-30  9:31                 ` Arthur Miller
2020-09-30 17:33                   ` martin rudalics
2020-09-30 17:36                     ` arthur miller
2020-10-01  8:39                       ` martin rudalics
2020-10-17 21:51                         ` Arthur Miller
2020-10-18  7:56                           ` martin rudalics
2020-10-18 14:10                             ` Arthur Miller
2020-10-20  7:20                               ` martin rudalics
2022-04-21 14:02                               ` Lars Ingebrigtsen [this message]
2020-09-28 17:59   ` martin rudalics
2020-09-28 17:59 ` martin rudalics

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=87wnfi4jrc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=43672@debbugs.gnu.org \
    --cc=arthur.miller@live.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).