all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>,
	"Stefan Kangas" <stefan@marxist.se>,
	"Richard Stallman" <rms@gnu.org>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Rename "window" to "pane" (after Emacs 27)
Date: Wed, 01 Apr 2020 11:13:39 -0400	[thread overview]
Message-ID: <jwvo8sbs13q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <c2324c08-368f-4ecc-bd3a-cfc73ccace8b@default> (Drew Adams's message of "Wed, 1 Apr 2020 07:56:31 -0700 (PDT)")

> And would we then rename "frame" to "window", which

We won't be able to do that before (almost) all legacy uses of "window"
are gone (and not just from Emacs's own code), which will take many many
years (to get an idea: lexical-scoping and cl-lib are 7 years old now
and adapting code to them is much less intrusive than renaming all
`window`s to `pane`s), so it's important to realize that if it ever
happens we'll probably be significantly older than we are now.

W.r.t using "panes", we could start by making a *forward compatibility*
library `pane.el` distributed via GNU ELPA containing aliases to
the current `window` functions and variables.  Over time it can be
refined/improved to also rewrite docstrings and maybe try to tackle more
delicate issues (e.g. "alias" the `pane` property of overlays to
the `window` property).

This can be done without convincing anyone that we should rename
"window" to "pane", but can help prepare for it.


        Stefan




  reply	other threads:[~2020-04-01 15:13 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvo8sbs13q.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=oitofelix@gnu.org \
    --cc=rms@gnu.org \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.