From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Juanma Barranquero' <lekktu@gmail.com>,
'Emacs developers' <emacs-devel@gnu.org>
Subject: RE: Deprecate _emacs on Windows
Date: Tue, 22 Mar 2011 13:38:32 -0700 [thread overview]
Message-ID: <AAABC503D99C415A966940C9CE36E7AA@us.oracle.com> (raw)
In-Reply-To: <jwvei6boejg.fsf-monnier+emacs@gnu.org>
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.
No doubt due to a pampered American generation or two having been brought up
with extreme protection, from crash helmets for 3-year-old tricyclists to...
what's next? Disclaimers that alphabet soup might accidentally spell out
offensive words?
This phenomenon is a by-product of a unique civil law system gone
litigation-crazy. And the influence extends beyond Amerika, unfortunately.
People everywhere come to think it's only natural to **SCREAM ALARMIST
WARNINGS** at users about the slightest potential boo-boo.
It's one thing for some company to issue such silly warnings to avoid possible
lawsuits; it's another thing for everyone and her brother to act likewise for no
real reason other than habit.
Emacs need not fear a lawsuit in this case - and its users deserve better than
being beat over the head with such silliness. When pseudo-warnings abound about
anything and everything, any real warnings lose their significance.
next prev parent reply other threads:[~2011-03-22 20:38 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 [this message]
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
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=AAABC503D99C415A966940C9CE36E7AA@us.oracle.com \
--to=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).