all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: cyd@gnu.org, emacs-devel@gnu.org
Subject: RE: Marking old window variables obsolete
Date: Thu, 9 Aug 2012 09:10:47 -0700	[thread overview]
Message-ID: <D22D97A1A84746B38D7D60526A691081@us.oracle.com> (raw)
In-Reply-To: <83r4rgdpgt.fsf@gnu.org>

> > FWIW and for the record, I disagree with _all_ of that proposal.
> > Please do not do this.  There should be _no_ hurry to do anything
> > of the sort.  Why can't you wait a few releases - or more - for
> > all of the above?
> 
> Deprecation does not mean removal.  I'm sure you know that.

Of course.  No one suggested otherwise.

My request is first that we do not deprecate these user options _now_.

And second, preferably, that we do not deprecate them at all (i.e., even later),
but we instead keep them as an alternative, simpler way to do some (most?) of
what the new "machinery" does in a less user-friendly way (in my relatively
uninformed opinion).

And I also encourage better documenting the new machinery itself.  And
especially describing, for each such longstanding and useful user option, how to
get the same effect with the new, alternative machinery.  




  reply	other threads:[~2012-08-09 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09  9:43 Marking old window variables obsolete Chong Yidong
2012-08-09 14:12 ` Drew Adams
2012-08-09 16:01   ` Eli Zaretskii
2012-08-09 16:10     ` Drew Adams [this message]
2012-08-09 16:53       ` Eli Zaretskii
2012-08-09 18:16         ` Drew Adams
2012-08-09 18:37           ` Óscar Fuentes
2012-08-09 21:51             ` Drew Adams
2012-08-09 19:28           ` Eli Zaretskii
2012-08-09 21:53             ` Drew Adams
2012-08-10  6:18               ` Eli Zaretskii
2012-08-09 14:53 ` Stefan Monnier
2012-08-09 15:57   ` 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

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

  git send-email \
    --in-reply-to=D22D97A1A84746B38D7D60526A691081@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=cyd@gnu.org \
    --cc=eliz@gnu.org \
    --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 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.