From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: emacs-29 b44a7ff85dc: Allow 'icon-title-format' to have the value t
Date: Wed, 22 Feb 2023 16:22:59 +0100 [thread overview]
Message-ID: <87ttzdohbg.fsf@telefonica.net> (raw)
In-Reply-To: EC3664E6-4F4A-45F9-8743-4DDFE65ED01E@yahoo.com
Po Lu <Luangruo@yahoo.com> writes:
> Why not write:
>
> "This is useful on certain versions of KDE, where [description of the bug]"
>
> in NEWS instead? It would be much less misleading.
But the point is that the special value for icon-title-format is not all
that helpful at avoiding that bug. Certainly not more than
(setq icon-title-format (setq frame-title-format "blah))
... and even then the problem may happen anyway.
Plus, the KDE bug requires an specific configuration of KWin, so it is
not a frequent case at all.
At first I thought that Emacs was buggy, so I created an Emacs bug
report. Then we discovered that KDE is buggy and closed the issue, but
in the meantime I noticed that Emacs changing the frame title when it is
minimized can be problematic, and thus created another bug report
suggesting to set the default of icon-title-format to stay in sync with
frame-title-format. Somehow Eli mixed those two issues and introduced a
change to icon-title-format thinking on the original bug report.
prev parent reply other threads:[~2023-02-22 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167661970773.22310.13511166994278322415@vcs2.savannah.gnu.org>
[not found] ` <20230217074148.2E130C1391A@vcs2.savannah.gnu.org>
2023-02-20 20:57 ` emacs-29 b44a7ff85dc: Allow 'icon-title-format' to have the value t Óscar Fuentes
2023-02-21 12:13 ` Eli Zaretskii
2023-02-21 15:02 ` Óscar Fuentes
2023-02-21 15:26 ` Eli Zaretskii
2023-02-21 18:51 ` Óscar Fuentes
2023-02-21 19:07 ` Eli Zaretskii
2023-02-21 19:48 ` Óscar Fuentes
2023-02-22 14:35 ` Po Lu
2023-02-22 15:22 ` Óscar Fuentes [this message]
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=87ttzdohbg.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
/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).