From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 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 01:26:03 +0100 [thread overview]
Message-ID: <AANLkTincjezi9PLVNNxi7CFrQ+zO3cUFqAc_MPg104hM@mail.gmail.com> (raw)
In-Reply-To: <0B6A6EC5FD8F46D697F914FB2F6D4304@us.oracle.com>
> Why should it still exist?
Why not? You're making a big, big deal of a small warning that just
tells the user to rename a file.
And, why are you not pissed off by "emacs --unibyte", for example?
> Why should they have to?
Why should they not? By your reasoning, we should deprecate things,
but *never* remove them, because, why should we force users to change
anything? Well, if they are really that interested in keeping _emacs,
they can stay with Emacs 23.
> Why issue a _warning_ for this? As long as a user's `_emacs' is found and used
> (traditional behavior) there is nothing to warn about.
We're warning them that in a not-so-distant future they will find
their _emacs no longer working.
> And if a user's `_emacs'
> is no longer sought and found (i.e. ignored, in the future) then the warning
> obviously does no good.
I fail to understand your reasoning here, sorry.
> Since when does the mere act of deprecation call for a _warning_? A warning is
> in order only if a particular deprecation means there is some danger to warn
> about.
You have already lectured us on your interpretation for the word
"warning". I still disagree.
> Yes, I know you did, which is why I added that this has moved well beyond
> Amerika. As I said, a couple of generations and globalization have spread it,
> yes, even as far as Catalunya and the Canary Islands. You might like to believe
> you are not so influenced by American culture, but think again.
Please! Are you really unable to talk about these matters without
being patronizing?
Juanma
next prev parent reply other threads:[~2011-03-23 0:26 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 [this message]
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
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=AANLkTincjezi9PLVNNxi7CFrQ+zO3cUFqAc_MPg104hM@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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).