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: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, 61337@debbugs.gnu.org
Subject: bug#61337: 29.0.60; Setting frame-title-format makes Emacs to steal focus
Date: Thu, 09 Feb 2023 18:23:00 +0800	[thread overview]
Message-ID: <87mt5n3zp7.fsf@yahoo.com> (raw)
In-Reply-To: <83ilgbmdo9.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Feb 2023 10:43:50 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Which part? the change in xfns.c is fine (it just makes the code
> slower, so perhaps test EQ first and Fstring_equal if EQ doesn't
> return non-zero)

Just the change in xfns.c.  It fixes a bug in the original code (which
was trying to test whether or not both strings were equal, but didn't
handle the case where the strings were equal, but not EQ.)

>, but if someone sets icon-title-format in a way that
> produces a different string from what frame-title-format does, it will
> not work.  And forcing these two formats to produce the same strings
> is definitely NOT okay, not for emacs-29, not ever.

That isn't the change here.

> However, to tell the truth, I don't really understand the phenomenon
> being complained about in this case.  The original report says: "the
> z-order is not altered", whereas the conclusion of the analysis is
> "KWin seems to treat this as Emacs asking to be focused".  Would you
> please describe the problem in easier-to-understand terms and use the
> user-facing behavior instead of technical terms like z-order, so that
> I could at least make up my mind whether this issue is serious, and
> perhaps think about alternative solutions?  E.g., I don't yet
> understand why returning early in x_set_title should help here, and
> how.

The problem is that KWin apparently focuses a window if its title
changes while it is in a different workspace.  That's misbehavior on
KWin's part, and likely a bug.

Since moving to a different desktop is a form of iconification under X,
Emacs switches to displaying the icon title.

The change to xfns.c prevents Emacs from changing the title if the icon
title is identical to the frame title, which should make it possible to
work around the problem by setting icon-title-format to the same text as
frame-title-format; the rest is something that can only be fixed by its
developers.

The problem does not exist in Emacs 28, because icon-title-format did
not work there at all.

Thanks.





  reply	other threads:[~2023-02-09 10:23 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
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 [this message]
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=87mt5n3zp7.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61337@debbugs.gnu.org \
    --cc=eliz@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).