From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juanma Barranquero' <lekktu@gmail.com>,
'Lennart Borgman' <lennart.borgman@gmail.com>,
'Stefan Monnier' <monnier@iro.umontreal.ca>,
'Emacs developers' <emacs-devel@gnu.org>
Subject: RE: Deprecate _emacs on Windows
Date: Wed, 23 Mar 2011 12:20:53 +0900 [thread overview]
Message-ID: <87pqpi8qui.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <655D5DBB48F04F719130122440CDA29B@us.oracle.com>
Drew Adams writes:
> I objected to _warning_ users simply because you are deprecating
> `_emacs'.
In all the projects I know of, your understanding of "how deprecation
is done" notwithstanding, deprecation's semantic content is issuing a
warning. Formal deprecation is a policy statement that this feature
should *not* be used, *will* be removed, and any current uses should
be ported to the appropriate idiom, and yes, that should indeed get a
warning.
It should be possible to suppress those warnings (it is, in Python and
XEmacs), but the warning should be issued if the user chooses not to
suppress.
> That's not something to warn about. There is no danger.
OK, Drew, put
(if (< (random 100) 1) (error "Your .emacs is no longer usable."))
as the first line in your .emacs. When it triggers, come back and
tell us how you happy you are about losing use of your init file
without warning until it actually happens. Just how often do you
think long-time users read the section about what the name of the init
file is, anyway? Or NEWS?
The issue really *is* whether the feature should be removed, and
therefore deprecation and the accompanying warning are warranted, not
whether a deprecation deserves a warning. Personally, I think _emacs
is harmless, and deprecating it is indeed crying wolf, but that's not
my decision.
next prev parent reply other threads:[~2011-03-23 3:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 21:54 Deprecate _emacs on Windows Juanma Barranquero
2011-03-12 22:02 ` Lennart Borgman
2011-03-12 22:48 ` Drew Adams
2011-03-12 22:53 ` Lennart Borgman
2011-03-12 23:03 ` Drew Adams
2011-03-12 23:20 ` Lennart Borgman
2011-03-13 4:01 ` Stefan Monnier
2011-03-13 4:14 ` Juanma Barranquero
2011-03-22 20:38 ` Drew Adams
2011-03-22 20:50 ` Juanma Barranquero
2011-03-23 0:12 ` Drew Adams
2011-03-23 0:26 ` Juanma Barranquero
2011-03-23 0:58 ` Drew Adams
2011-03-23 1:34 ` Juanma Barranquero
2011-03-23 1:42 ` Juanma Barranquero
2011-03-24 23:33 ` Stephen J. Turnbull
2011-03-24 23:39 ` Juanma Barranquero
2011-03-23 2:42 ` Drew Adams
2011-03-23 3:00 ` Juanma Barranquero
2011-03-23 3:20 ` Stephen J. Turnbull [this message]
2011-03-23 3:34 ` Juanma Barranquero
2011-03-23 5:01 ` Óscar Fuentes
2011-03-23 12:07 ` Juanma Barranquero
2011-03-23 12:23 ` Fabian Ezequiel Gallina
2011-03-23 12:30 ` Juanma Barranquero
2011-03-23 13:36 ` Fabian Ezequiel Gallina
2011-03-23 13:42 ` Drew Adams
2011-03-23 14:30 ` Juanma Barranquero
2011-03-23 17:40 ` Stefan Monnier
2011-03-23 14:09 ` Drew Adams
2011-03-23 16:23 ` Stephen J. Turnbull
2011-03-13 22:49 ` Chong Yidong
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=87pqpi8qui.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).