all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Marking old window variables obsolete
Date: Thu, 09 Aug 2012 20:37:56 +0200	[thread overview]
Message-ID: <87mx23j4hn.fsf@wanadoo.es> (raw)
In-Reply-To: 2C6E1B3A8D6C411980AFBD9472E76E03@us.oracle.com

"Drew Adams" <drew.adams@oracle.com> writes:

> 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.

Really? Even if we supposse that everybody reads the NEWS file and are
willing to adapt their perfectly working configuration on accordance,
your approach would limit the set of acceptable new features to those
which are indisputably more useful than the functionality they
replace/modify for the taste of (almost?) all the Emacs user population.

What's reasonable, IMHO, is to add clear instructions to the docstrings
of those variables and functions explaining how to migrate to the new
machinery. If those instructions turn to be too complex, it is an
indication that the new system is not so good. A good practice is to do
those kind of documentation tasks at the design phase of the new
machinary as a preemptive usability check.




  reply	other threads:[~2012-08-09 18:37 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 [this message]
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=87mx23j4hn.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --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.