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 14:53:06 -0700 [thread overview]
Message-ID: <1418ED67AA6C4EEC9F294278215E9D15@us.oracle.com> (raw)
In-Reply-To: <83lihneugd.fsf@gnu.org>
> > > > My request is first that we do not deprecate these user
> > > > options _now_.
> > >
> > > How else can we encourage users to migrate to the new machinery?
> >
> > Sheesh. If that's the only way users can be encouraged to
> > adopt the new machinery, that doesn't say much about how appealing
> > it is, does it?
> >
> > Users generally have little problem adopting new features
> > that they find (or even suspect might be) useful.
>
> You must be kidding, if you rely in people discovering every new
> feature among hundreds, let alone study each one of them.
No, I am not kidding.
And you are jumping all over the map. So now it's about users _discovering_ new
features? No.
With that logic, we should deprecate all over the place, just to make sure users
discover new features. "You must be kidding."
next prev parent reply other threads:[~2012-08-09 21:53 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
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 [this message]
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
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=1418ED67AA6C4EEC9F294278215E9D15@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 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).