From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=C3=93scar?= Fuentes Newsgroups: gmane.emacs.bugs Subject: bug#61496: 30.0.50; Default value of icon-title-format Date: Tue, 14 Feb 2023 14:35:56 +0100 Message-ID: <87mt5gqshv.fsf@telefonica.net> References: <87zg9hqflv.fsf@telefonica.net> <83fsb8e8yr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8606"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 61496@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 14 15:09:53 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pRw0G-00023L-Jf for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Feb 2023 15:09:52 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pRvUV-0003Uc-Ot; Tue, 14 Feb 2023 08:37:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pRvUU-0003UP-LQ for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 08:37:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pRvUU-00070w-C5 for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 08:37:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pRvUT-0000wf-UH for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 08:37:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=C3=93scar?= Fuentes Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Feb 2023 13:37:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61496 X-GNU-PR-Package: emacs Original-Received: via spool by 61496-submit@debbugs.gnu.org id=B61496.16763817723564 (code B ref 61496); Tue, 14 Feb 2023 13:37:01 +0000 Original-Received: (at 61496) by debbugs.gnu.org; 14 Feb 2023 13:36:12 +0000 Original-Received: from localhost ([127.0.0.1]:52904 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pRvTf-0000vP-QG for submit@debbugs.gnu.org; Tue, 14 Feb 2023 08:36:12 -0500 Original-Received: from relayout02.e.movistar.es ([86.109.101.202]:63631 helo=relayout02-redir.e.movistar.es) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pRvTZ-0000up-RC for 61496@debbugs.gnu.org; Tue, 14 Feb 2023 08:36:09 -0500 Original-Received: from sky (73.red-81-39-121.dynamicip.rima-tde.net [81.39.121.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: 981711563@telefonica.net) by relayout02.e.movistar.es (Postfix) with ESMTPSA id 4PGMfj5VLdzdb5t; Tue, 14 Feb 2023 14:35:56 +0100 (CET) In-Reply-To: <83fsb8e8yr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 14:18:36 +0200") X-TnetOut-Country: IP: 81.39.121.73 | Country: ES X-TnetOut-Information: AntiSPAM and AntiVIRUS on relayout02 X-TnetOut-MsgID: 4PGMfj5VLdzdb5t.AA737 X-TnetOut-SpamCheck: no es spam, clean X-TnetOut-From: ofv@wanadoo.es X-TnetOut-Watermark: 1676986558.85457@nSmo1UiHZEHUSyhQoujhBA X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:255581 Archived-At: Eli Zaretskii writes: > I agree with adding a feature that will allow to keep > icon-title-format and frame-title-format identical. However: > > . I don't want to make that the default: it's too late for such > changes on the emacs-29 branch. The whole point of this change is to not break user's setup when they upgrade to 29. If the user must fix his config, he may as well set icon-title-format and be done with it. OTOH, there is no possible breakage by changing the default. > . I suggest that the "special" value which means "use > frame-title-format" will be t, not nil, so that users who want it > set it explicitly, not by some omission. The purpose of changing the default is based partly on the idea that, very likely, the user will want to keep icon-title-format in sync with frame-title-format. So not having to do anything to achieve that is a feature, not a bug. > (Code-wise, this is not > important, since the code treats both nil and t the same: it > produces nothing. So using t or nil is backward-compatible, in > the sense that older Emacsen will not crash.) > > I understand that you think the more radical change you propose is for > the better, and "no one can possibly suffer of be against it", but I > think you are not very objective, being a victim of the problem, Yes, wasting several hours made me aware of the impact this change may have. This made my judgement quite *objetive* about it :-) > and > it is quite possible that someone out there does want/expect the > default value to be a string. I have no idea how this can be. OTOH, the problems caused by the current state are obvious and real. > Thus, I think we should leave the > change of the default value for some future release. ... which, as I explained, will require another round of fixes on user's config to avoid the same problem when 30 is released. > So: okay for changing xdisp.c, just using EQ (Qt, ...), not NILP, but > please don't change the default value of icon-title-format. > > Also, this change needs a suitable NEWS entry and appropriate changes > for the doc string and the ELisp manual. If this is your final decision, it's better to discard the whole proposal, as it gives little benefit. Then, mentioning in NEWS that icon-title-format is back is even more important because of the problems mentioned.