unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 b44a7ff85dc: Allow 'icon-title-format' to have the value t
Date: Tue, 21 Feb 2023 21:07:02 +0200	[thread overview]
Message-ID: <83r0uisuqx.fsf@gnu.org> (raw)
In-Reply-To: <87356yq2c8.fsf@telefonica.net> (message from Óscar Fuentes on Tue, 21 Feb 2023 19:51:19 +0100)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Tue, 21 Feb 2023 19:51:19 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > If that's what users want, how did they do it before this change?
> 
> They didn't need to do anything, because icon-frame-title was
> ineffective and Emacs used frame-title-format when minimized too.

They don't need to do anything now, either, because the default value
of icon-frame-title is a string whose text is identical to that of
frame-title-format.

> > If the desktop doesn't behave like KDE, users could simply set both
> > formats to two identical strings.  The only reason to force Emacs to
> > use the _same_ string (which can only be done internally) is that
> > those desktops misbehave.
> 
> The reason to force Emacs to use the same string is to behave as most
> users expect, and to avoid hard-to-detect breakage on desktop automation
> setups that depend on the title of the window.
> 
> That was explained in #61496. No need to rehash the discussion here.
> 
> > So I don't see why we should remove the explanation.
> >
> >> OTOH, maybe we could explain that icon-frame-title it is effective
> >> in cases where the user does not explicitly iconify the frame, as
> >> when he moves to another virtual desktop.
> >
> > Sorry, I don't think I understand what you mean here.
> 
> Again, it was explained in #61496.

Look, you started this discussion.  Now it sounds like you don't want
to continue it.  Neither do I, as a matter of fact.  I see no need to
change anything in the documentation of these features.



  reply	other threads:[~2023-02-21 19:07 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 [this message]
2023-02-21 19:48               ` Óscar Fuentes
2023-02-22 14:35                 ` Po Lu
2023-02-22 15:22                   ` Óscar Fuentes

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=83r0uisuqx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).