From: "Drew Adams" <drew.adams@oracle.com>
To: "'Óscar Fuentes'" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: RE: Marking old window variables obsolete
Date: Thu, 9 Aug 2012 14:51:31 -0700 [thread overview]
Message-ID: <2C4C11FDCD1A478B9353BACB064B6B46@us.oracle.com> (raw)
In-Reply-To: <87mx23j4hn.fsf@wanadoo.es>
> 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.
Sorry, but that simply does not follow, at all. None of it.
I am _not_ proposing _any_ limitation on what new features are acceptable. And
in particular I have not objected to the "new machinery" for controlling buffer
display, and I have even said explicitly that I am _glad_ for it to exist.
I simply object to deprecating those longstanding user options now.
And I prefer that we in fact keep them as a simple, alternative way to customize
the behavior.
> 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.
That is also something that I (and Eli also) proposed. You and I are in the
same choir on that.
Such doc certainly should be part of any future deprecation, if ever that should
occur.
And it would be helpful even if we do not deprecate the options. The
correspondence between the different ways of doing things is something that is
good to know, in any case.
> If those instructions turn to be too complex, it is an
> indication that the new system is not so good.
That's also something I suggested. If we cannot even explain that
correspondence in simple terms, it's hard to imagine that we would be convinced
that the variables should be deprecated, especially so soon.
> A good practice is to do those kind of documentation tasks at the
> design phase of the new machinary as a preemptive usability check.
Again, we are in agreement. And that is why I brought it up back then.
http://lists.gnu.org/archive/html/emacs-devel/2011-06/msg00677.html
http://lists.gnu.org/archive/html/emacs-devel/2009-05/msg00048.html
http://lists.gnu.org/archive/html/emacs-devel/2011-06/msg00834.html
next prev parent reply other threads:[~2012-08-09 21:51 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 [this message]
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=2C4C11FDCD1A478B9353BACB064B6B46@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.