unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: sds@gnu.org, emacs-devel@gnu.org
Subject: RE: Rename "window" to "pane" (after Emacs 27)
Date: Fri, 3 Apr 2020 11:34:34 -0700 (PDT)	[thread overview]
Message-ID: <1900ccca-6f14-4a69-944a-f4264195bb25@default> (raw)
In-Reply-To: <m1eet430x6.fsf@gnu.org>

> > And would we then rename "frame" to "window", which
> > would engender further confusion, especially wrt
> > older versions and all of the existing Emacs
> > collateral outside Emacs proper?
> 
> Exactly!

Oh, and BTW, in the jargon of web browsers and HTML
there is even a notion of "frame" which is, in a way,
akin to an Emacs window: HTML element <frame>.
IOW, in a way, the two terms are swapped, to the
extent that anyone even uses "frame" outside Emacs.
(Element <frame> isn't used much anymore.)

[No, please don't bother to respond saying that the
analogies/correspondences aren't perfect.  The point
is that _confusion_ is probable if we start trying to
switch - and not just for the interim period when only
"window" is renamed.]

https://en.wikipedia.org/wiki/Frame_(World_Wide_Web)

> So it will take us 2-3 releases to rename "window" to "pane"
> and then another 2-3 releases to rename "frame" to "window".
> Thus, 10 years from now we will be in compliance with the
> common terminology introduced in 1990-ies.

I think Stefan even said 20 years.  But yeah.

> By then it is quite possible that the whole "window manager"
> paradigm will be obsolete as more and more computing is done
> on mobile devices with full-screen-only windows, where the
> current Emacs terminology makes more sense.

Exactly.  Trying to sync with non-Emacs terminology
from 1994 and the creation of browsers is misguided
in multiple ways.

This is truly a YAGNI, IMO.  I've seen _no_ evidence
that novice Emacs users are taken aback by the Emacs
terminology of "window" and "frame".  It takes about
10 minutes to learn and assimilate the notions.

To me, this is a false, Sky-is-falling!! problem
promoted by some who seriously wonder/worry about an
apparent scarcity of Emacs newbies.  That alarmism
resurfaces here every few years...

And I'm not even convinced of said scarcity.  At
least from my point of view, Emacs is not, and should
not be, in a popularity contest with other editors.

Scarcity of Emacs developers is a different question,
I think.  And the window/frame terminology is in no
sense a hurdle in that regard (again, IMO).

> So... how much effort are we willing to expend on this cosmetic change?
> Don't we have something better to do with our time?



  reply	other threads:[~2020-04-03 18:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 23:07 Rename "window" to "pane" (after Emacs 27) Stefan Kangas
2019-10-29  0:28 ` Filipp Gunbin
2019-10-29  1:55   ` Stefan Kangas
2019-10-30 17:29 ` Eli Zaretskii
2019-10-31  2:07 ` Richard Stallman
2020-03-31 18:50   ` Bruno Félix Rezende Ribeiro
2020-04-01  2:07     ` Richard Stallman
2020-04-01 12:03       ` Stefan Kangas
2020-04-01 14:56         ` Drew Adams
2020-04-01 15:13           ` Stefan Monnier
2020-04-01 17:04             ` Stefan Kangas
2020-04-01 17:30               ` Drew Adams
2020-04-02  2:34                 ` Richard Stallman
2020-04-02  4:51                   ` Jean-Christophe Helary
2020-04-03  2:52                     ` Richard Stallman
2020-04-01 15:25           ` Juanma Barranquero
2020-04-03 17:59           ` Sam Steingold
2020-04-03 18:34             ` Drew Adams [this message]
2020-04-03 18:53               ` Dmitry Gutov
2020-04-03 18:56                 ` Drew Adams
2020-04-03 18:54             ` Dmitry Gutov
2020-04-08 15:34               ` Sam Steingold
2020-04-08 17:29                 ` Dmitry Gutov
2020-04-02  2:31         ` Richard Stallman
2020-04-02  2:31         ` Richard Stallman

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=1900ccca-6f14-4a69-944a-f4264195bb25@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=sds@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).