unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 61337@debbugs.gnu.org
Subject: bug#61337: 29.0.60; Setting frame-title-format makes Emacs to steal focus
Date: Wed, 08 Feb 2023 12:48:01 +0800	[thread overview]
Message-ID: <87o7q469vi.fsf@yahoo.com> (raw)
In-Reply-To: <87v8kcvllw.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Wed, 08 Feb 2023 05:15:23 +0100")

Óscar Fuentes <ofv@wanadoo.es> writes:

> Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs@gnu.org> writes:
>
>> What if you do this?
>>
>> My suspicion is that the icon name is now being set to reflect that the
>> frame has been iconified, and KWin (wrongly) treats that as an attempt
>> to focus the frame.
>>
>> diff --git a/src/xterm.c b/src/xterm.c
>> index 1325d923be9..fcac6bc044f 100644
>> --- a/src/xterm.c
>> +++ b/src/xterm.c
>> @@ -25584,6 +25584,8 @@ x_text_icon (struct frame *f, const char *icon_name)
>>    if (FRAME_X_WINDOW (f) == 0)
>>      return true;
>>  
>> +  return;
>> +
>>    {
>>      XTextProperty text;
>>      text.value = (unsigned char *) icon_name;
>
> Same. GCC warned about missing return value, so then I tried `false' and
> finally `true'. No change.

Would you please run:

  xprop -spy

in a separate terminal emulator window, click on the Emacs frame, switch
to xterm, the other desktop, and back again, and then tell me what xprop
prints?

Thank you.





  reply	other threads:[~2023-02-08  4:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  5:07 bug#61337: 29.0.60; Setting frame-title-format makes Emacs to steal focus Oscar Fuentes
2023-02-07 14:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 15:29   ` Óscar Fuentes
2023-02-08  1:16     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08  2:45       ` Óscar Fuentes
2023-02-08  3:59         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08  4:15           ` Óscar Fuentes
2023-02-08  4:48             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-08 15:24               ` Óscar Fuentes
2023-02-09  2:20                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09  3:17                   ` Óscar Fuentes
2023-02-09  8:15                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09  8:43                       ` Eli Zaretskii
2023-02-09 10:23                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 11:22                           ` Eli Zaretskii
2023-02-09 14:16                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 15:32                               ` Óscar Fuentes
2023-02-09 15:53                                 ` Eli Zaretskii
2023-02-09 16:17                                   ` Óscar Fuentes
2023-02-09 16:50                                     ` Eli Zaretskii
2023-02-10  2:15                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  5:07                                         ` Óscar Fuentes
2023-02-10  7:15                                         ` Eli Zaretskii
2023-02-10  1:59                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  4:56                                   ` Óscar Fuentes
2023-02-13 16:02                                   ` Óscar Fuentes
2023-02-14  2:02                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87o7q469vi.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61337@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=ofv@wanadoo.es \
    /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).