unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Thu, 04 May 2023 16:51:29 +0200	[thread overview]
Message-ID: <877ctocfpq.fsf@telefonica.net> (raw)
In-Reply-To: s8h8re4emo1.fsf@yahoo.com

Po Lu <luangruo@yahoo.com> writes:

> Tobias Bading <tbading@web.de> writes:
>
>> On 04.05.23 02:12, Po Lu wrote:
>>>>     The title of iconified or minimized frames is determined by
>>>                    ^^^^^^^^^^^^^^^^^^^^^^
>>>
>>> X does not use the term ``minimized''.  We prefer just
>>> ``iconified''.
>>
>> I’m afraid “we” includes me — because I’m old. So old in fact that I
>> (barely) remember mwm being able to turn top-level windows into icons
>> and back. Those were the days… ;-)
>>
>> But I don’t actually remember the last window manager I used that used
>> this
>> feature. Might actually have been mwm. The last decade or so GNOME 2
>> and
>> then MATE minimized my windows into the Window List panel applet. So I
>> can
>> see the window’s title changing when it is minimized or restored,
>> which is a
>> rather uncommon “feature” in this desktop environment.
>>
>> PS: there’s also “shaded” these days… :-p
>
> These are all reported under the Iconic state, and as such that is the
> terminology we use in Emacs.
>
> So let's please not use the term "minimize".  Thanks.

What's wrong with saying "iconified or minimized"?

IIRC a few years ago there was on this list some acknowledgment of the
problems posed by using obsolete terminology in Emacs and some actions
were discussed to converge to modern wording up to some extent.

Rejecting "___ or minimized" on the docs only works nowadays if the goal
is obfuscating things.




  parent reply	other threads:[~2023-05-04 14:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 18:40 icon-title-format vs. frame-title-format (Bug#61496) Tobias Bading
2023-05-03 18:56 ` Eli Zaretskii
2023-05-03 19:10   ` Tobias Bading
2023-05-04  0:12 ` Po Lu
2023-05-04  4:03   ` Tobias Bading
2023-05-04  4:38     ` Po Lu
2023-05-04  4:46       ` Tobias Bading
2023-05-04  4:59         ` Tobias Bading
2023-05-04 14:51       ` Óscar Fuentes [this message]
2023-05-04 16:08         ` Eli Zaretskii
2023-05-04 16:37           ` Óscar Fuentes
2023-05-04 17:36             ` Eli Zaretskii
2023-05-05  0:15         ` Po Lu
2023-05-05  1:02           ` Óscar Fuentes
2023-05-05  4:44             ` tomas
2023-05-05  5:33               ` Eli Zaretskii
2023-05-05  7:28                 ` tomas
2023-05-05 10:39                   ` Eli Zaretskii
2023-05-05  5:24             ` Po Lu
2023-05-05  5:29           ` Eli Zaretskii
2023-05-05 10:40 ` Tobias Bading
2023-05-05 11:00   ` Eli Zaretskii
2023-05-05 11:00   ` Po Lu
2023-05-05 11:17     ` Eli Zaretskii
2023-05-05 12:29       ` Po Lu
2023-05-05 13:31         ` Eli Zaretskii
2023-05-05 23:52           ` Po Lu
2023-05-06  6:27             ` Eli Zaretskii

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=877ctocfpq.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).