From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: tbading@web.de, emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Fri, 05 May 2023 16:31:14 +0300 [thread overview]
Message-ID: <83ednuj465.fsf@gnu.org> (raw)
In-Reply-To: <874jorklli.fsf@yahoo.com> (message from Po Lu on Fri, 05 May 2023 20:29:29 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: tbading@web.de, emacs-devel@gnu.org
> Date: Fri, 05 May 2023 20:29:29 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Anyway, I don't object to explaining what we call ``minimized'', as long
> >> as it is confined to some short introductory text in the manual. But we
> >> should never use the term ``minimized'' ourselves.
> >
> > That's not the current policy, and I see no reason to enforce such
> > restrictions. So please stop pushing others to adopt your personal
> > preferences.
>
> There are at least two reasons:
>
> 1. the term ``minimize'' does not make sense, at least on the common
> free desktops.
>
> 2. Emacs minimizes windows, while it iconifies frames. Type M-x
> minimize-window RET, then see what happens.
I hear you, but I still don't see that as good enough reasons to stop
using "minimize frames" as well. I explained my reasons already, and
IMO they are more important than the ones you present.
next prev parent reply other threads:[~2023-05-05 13:31 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
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 [this message]
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=83ednuj465.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tbading@web.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).