unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, <rms@gnu.org>
Cc: 12621@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#12621: Emacs 24.1 crashing on Windows 7
Date: Sat, 15 Dec 2012 12:41:19 -0800	[thread overview]
Message-ID: <909C0D44C3864106A12B04D2F3410D44@us.oracle.com> (raw)
In-Reply-To: <83y5gzqe0r.fsf@gnu.org>

> > I don't think a piece of proprietary software, with known 
> > spyware, DRM and back doors, deserves respect.
> 
> Well, actually, it does, for several technical achievements that I can
> only dream of when I work on modern GNU/Linux systems.  But I won't
> say a word more about that, because this is off-topic here.

Off-topic technically, perhaps, but not off-topic wrt the OP's feelings and
intention indicated in the bug report.

Aside from the question of whether MS deserves respect or whether MS Windows
deserves some respect as software, there is the neglected point that the OP made
in characterizing the anti-"win" campaign as "puerile".

I think that raises a reasonable question, and one that perhaps is not
completely independent of asking how effective such a campaign is or can be.

I would agree with the OP that it smacks of childishness, even if that is not
the intent.  It also seems a bit old-hat/been-there-done-that at this point.

It reminds me of those who still like to call users "lusers" or "losers".  Kind
of an infantile joke, and an old one.  A joke you might have laughed at the
first time you heard it back in 1968, but one you no longer find very funny.
Quite the opposite - users deserve respect, even, or especially, when they are
ignorant.

Of course, poking fun at things that are evil or regressive can sometimes be
effective and progressive, even sometimes when the poking fun is infantile.

But it's a good question for GNU to (re)consider perhaps at this point: what's
the point/effect of the anti-"win" campaign now?






  reply	other threads:[~2012-12-15 20:41 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  3:32 bug#12621: Win32 (Ver:24.2); Crashes when files from shared folders are accessed Arvind Devarajan
2012-10-11  8:38 ` bug#12621: Acknowledgement (Win32 (Ver:24.2); Crashes when files from shared folders are accessed) Arvind Devarajan
2012-10-11 17:11   ` bug#12621: Win32 (Ver:24.2); Crashes when files from shared folders are accessed Eli Zaretskii
2012-10-16 13:39 ` Arvind Devarajan
2012-10-16 17:32   ` Eli Zaretskii
2012-10-22 10:19 ` Arvind Devarajan
2012-10-22 17:14   ` Eli Zaretskii
2012-10-23 12:16 ` Arvind Devarajan
2012-10-23 16:24   ` Eli Zaretskii
2012-12-13 10:22 ` bug#12621: Emacs 24.1 crashing on Win7 Arunas Ruksnaitis
2012-12-13 18:04   ` Eli Zaretskii
2012-12-13 18:30     ` Arunas Ruksnaitis
2012-12-13 19:05       ` Eli Zaretskii
2012-12-13 19:13         ` Eli Zaretskii
2012-12-13 21:09           ` Arūnas Rukšnaitis
2012-12-14  9:16             ` Eli Zaretskii
2012-12-14 14:07               ` Eli Zaretskii
2013-02-19 18:53               ` Glenn Morris
2013-02-19 21:00                 ` Eli Zaretskii
2012-12-13 18:41     ` Arunas Ruksnaitis
2012-12-13 19:08       ` Eli Zaretskii
2012-12-14 15:22       ` bug#12621: Emacs 24.1 crashing on Lose7 Richard Stallman
2012-12-14 18:31         ` Arunas Ruksnaitis
2012-12-15  0:36         ` bug#12621: Emacs 24.1 crashing on Windows 7 Andy Moreton
2012-12-15  8:16           ` Eli Zaretskii
2012-12-15 19:46             ` Richard Stallman
2012-12-15 20:03               ` Eli Zaretskii
2012-12-15 20:41                 ` Drew Adams [this message]
2012-12-16 21:23                 ` Richard Stallman
2012-12-15 20:45               ` Daniel Colascione
2012-12-16 21:23                 ` Richard Stallman
2012-12-17  2:03                   ` Dmitry Gutov
2012-12-17  2:19                     ` Daniel Colascione
2012-12-17  2:30                       ` Dmitry Gutov
2012-12-17 23:46                       ` Richard Stallman
2012-12-16 22:05           ` Stefan Monnier
2012-12-16 22:26             ` Drew Adams
2012-12-16 22:36               ` Drew Adams
2012-12-16 23:04               ` Juanma Barranquero
2012-12-17  0:04               ` Stephen Berman
2012-12-17  0:17                 ` Bastien
2012-12-17  1:38                   ` Drew Adams
2012-12-17  1:42                     ` Drew Adams
2012-12-17 23:46                     ` Richard Stallman
2012-12-18  9:35                       ` Bastien
2012-12-18 18:30                         ` Richard Stallman
2012-12-18 18:48                           ` Bastien
2012-12-17  0:43                 ` Juanma Barranquero
     [not found]                 ` <mailman.15500.1355705095.855.bug-gnu-emacs@gnu.org>
2012-12-17  1:01                   ` Burton Samograd
2012-12-17  2:11                 ` Daniel Colascione
2012-12-17 23:46                 ` Richard Stallman
2012-12-17  1:55             ` Dmitry Gutov

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=909C0D44C3864106A12B04D2F3410D44@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12621@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=eliz@gnu.org \
    --cc=rms@gnu.org \
    /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).