unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: <tomas@tuxteam.de>
Cc: emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Fri, 05 May 2023 08:33:14 +0300	[thread overview]
Message-ID: <83jzxnjqat.fsf@gnu.org> (raw)
In-Reply-To: <ZFSJvapZ2/8ZUI9T@tuxteam.de> (tomas@tuxteam.de)

> Date: Fri, 5 May 2023 06:44:45 +0200
> From: <tomas@tuxteam.de>
> 
> > > ``minimize'' is not modern terminology.  It is simply terminology used
> > > by proprietary window systems.
> > 
> > KDE and AwesomeWM (just to mention the window managers I have installed
> > on this machine) are not proprietary. AFAIK Gnome also uses "minimize"
> > on its user-oriented documentation, so does Xfce and LXQt.
> 
> Po Lu is still right. The question is whether to accept Microsoft's
> intellectual hegemony here (as the GNU/Linux desktop ennvironments
> have done, too lightly for my personal taste) or not.
> 
> Tough question. I clearly side with Po Lu's standpoint here, but can
> understand that there are others.

There's no "standpoint" here.  Our documentation must be easily
interpreted by today's users, and so boycotting terminology we don't
like is silly and futile.  We will be shooting ourselves in the foot.

Once again: the documentation already says that these two are
equivalent, so both terms can be used.  Which one to use in each case
depends on the context; for example, when talking about variables or
functions that include "icon" in their names, using "iconify" is
clearly better (but "minimize" could be mentioned in parentheses as
the alternative, where appropriate).



  reply	other threads:[~2023-05-05  5:33 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
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 [this message]
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=83jzxnjqat.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tomas@tuxteam.de \
    /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).