unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
Subject: Re: gnu vs. xemacs
Date: Fri, 29 Dec 2006 10:53:03 +1100	[thread overview]
Message-ID: <877iwbshls.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.2457.1167332268.2155.help-gnu-emacs@gnu.org

Matthew Flaschen <matthew.flaschen@gatech.edu> writes:

> Tim X wrote:
>> You don't think your being a bit pedantic do you? After all, Linux is
>> what GNU/Linux is commonly called. You also have lots of other
>> references out there which don't include the "GNU" part, such as The
>> Linux Journal, the Linux Gazette, Linux Weekly news,
>> linuxquestions.org, linuxkernel.org, etc etc.
>
>> At least if your going to take the time to post a response, maybe add
>> something for the OP in addition to correcting his colloquial use of
>> Linux rather than the technically correct one.
>
> I don't think he's being pedantic, and the fact that the error is common
> does not mean it's insignificant.  It's not only technically correct,
> it's ethically correct.
>
> As for the OP, I can't help since I've never used XEmacs.
>

Perhaps your right - I guess what got to me was the fact the
respondent was able to take the time to correct a common error which
nearly everyone is guilty of, but failed to actually address the OPs
question in any way. I mean, is he going to correct every post that
refers to just Linux rather than GNU/Linux?

Although I understand why we should encourage people to not drop the
GNU part, I suspect that basic human tendency to shorten descriptions
will see Linux being used far more often than GNU/Linux. We have
far greater ethical problems relating to how people use GNU software
and misunderstanding regarding free software and open source than
whether people use the "formal" title or not. IMO if we want users to
adopt a specific terminology, we need to provide positive
reinforcement to do so in addition to criticising them when they fail
to. Actually assisting someone together with correcting their
understandable error in terms would assist in this. Just criticism
without any assistance is more likely to have the opposite affect. 

Tim


-- 
tcross (at) rapttech dot com dot au

  parent reply	other threads:[~2006-12-28 23:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27 11:46 gnu vs. xemacs H.
2006-12-27 12:57 ` Lennart Borgman (gmail)
2006-12-27 13:10 ` Peter Dyballa
2006-12-27 13:59 ` Sven Bretfeld
2006-12-28 10:27   ` Ramprasad
     [not found]   ` <mailman.2429.1167301573.2155.help-gnu-emacs@gnu.org>
2006-12-28 11:27     ` Tim X
2006-12-28 18:57       ` Matthew Flaschen
     [not found]       ` <mailman.2457.1167332268.2155.help-gnu-emacs@gnu.org>
2006-12-28 23:53         ` Tim X [this message]
2006-12-29  1:12           ` Leo
2006-12-29 12:46             ` "MIT/GNU/Linux" (was: gnu vs. xemacs) B. Smith-Mannschott
2006-12-29 13:59               ` Micha Feigin
2006-12-29 14:17                 ` Gian Uberto Lauri
2006-12-29 17:27                 ` "MIT/GNU/Linux" Alexey Pustyntsev
2006-12-29 18:35                   ` "MIT/GNU/Linux" Kim F. Storm
     [not found]               ` <mailman.2488.1167400944.2155.help-gnu-emacs@gnu.org>
2006-12-29 15:29                 ` "MIT/GNU/Linux" Giorgos Keramidas
2006-12-30  0:28                   ` "MIT/GNU/Linux" Tim X
2006-12-30  6:05                     ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                     ` <mailman.2537.1167458715.2155.help-gnu-emacs@gnu.org>
2006-12-30 12:09                       ` "MIT/GNU/Linux" Tim X
2006-12-30 17:13                         ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                         ` <mailman.2550.1167498938.2155.help-gnu-emacs@gnu.org>
2006-12-31  2:36                           ` "MIT/GNU/Linux" Tim X
2006-12-31 15:42                             ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01  2:45                               ` "MIT/GNU/Linux" Tim X
2006-12-31 15:34                     ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01  2:21                       ` "MIT/GNU/Linux" Tim X
2006-12-29 23:12                 ` "MIT/GNU/Linux" Jay Belanger
2006-12-30 15:13                   ` "MIT/GNU/Linux" Micha Feigin
     [not found]                   ` <mailman.2547.1167491771.2155.help-gnu-emacs@gnu.org>
2006-12-30 17:19                     ` "MIT/GNU/Linux" Robert Thorpe
2006-12-30 17:49                 ` "MIT/GNU/Linux" (was: gnu vs. xemacs) Robert Thorpe
2006-12-30 19:20                   ` Matthew Flaschen
     [not found]             ` <mailman.2487.1167396377.2155.help-gnu-emacs@gnu.org>
2007-01-03  6:42               ` "MIT/GNU/Linux" Stefan Monnier
2007-01-03  8:17                 ` "MIT/GNU/Linux" Drew Adams
2007-01-03 10:03                 ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                 ` <mailman.2685.1167818637.2155.help-gnu-emacs@gnu.org>
2007-01-03 20:33                   ` "MIT/GNU/Linux" Stefan Monnier
2007-01-04  9:14                     ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]           ` <mailman.2475.1167354778.2155.help-gnu-emacs@gnu.org>
2006-12-29 18:23             ` gnu vs. xemacs Hadron Quark
2006-12-29 18:32               ` Ralf Angeli
2006-12-27 19:52 ` David Kastrup
2006-12-28 14:36 ` insert name
2006-12-28 20:25   ` David Kastrup

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=877iwbshls.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    /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.
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).