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: Tue, 22 Mar 2011 21:50:48 +0100 [thread overview]
Message-ID: <AANLkTi=GYfn9=oSThGyhdJo2XzFCLcEs_Vb+Xqgd=VYv@mail.gmail.com> (raw)
In-Reply-To: <AAABC503D99C415A966940C9CE36E7AA@us.oracle.com>
On Tue, Mar 22, 2011 at 21:38, Drew Adams <drew.adams@oracle.com> wrote:
> Come on. This is getting silly. Now there is a _warning_ when you start Emacs
> with an init file named `_emacs'. A ***WARNING***? You have got to be kidding.
> Ridiculous.
I think you made your opinion on this issue quite clear before, even
in the same thread where I discussed adding the warning, so it's a
bit... silly? ridiculous? for you to suddenly show such indignation.
That said, if you cool off a bit, perhaps you could wait until the
delayed warning issue is decided, and then we can change the warning
so it still exists, but users can deactivate it from their .emacs...
Sorry, I mean from their _emacs.
> This phenomenon is a by-product of a unique civil law system gone
> litigation-crazy. And the influence extends beyond Amerika, unfortunately.
Well, Spain is nowhere near the States in this regard (and I proposed
and added the warning) so I think your analysis is... silly?
ridiculous? out of the line?
> Emacs need not fear a lawsuit in this case - and its users deserve better than
> being beat over the head with such silliness.
The users you are trying to protect can avoid that warning with
C:> ren _emacs .emacs
Hard, isn't?
Juanma
next prev parent reply other threads:[~2011-03-22 20:50 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 [this message]
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
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='AANLkTi=GYfn9=oSThGyhdJo2XzFCLcEs_Vb+Xqgd=VYv@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).