unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: Variant spellings in GNU Emacs documentation
Date: Tue, 20 Jan 2004 22:31:00 GMT	[thread overview]
Message-ID: <barmar-A2688C.17310120012004@netnews.comcast.net> (raw)
In-Reply-To: mailman.978.1074588520.928.bug-gnu-emacs@gnu.org

In article <mailman.978.1074588520.928.bug-gnu-emacs@gnu.org>,
 "Eli Zaretskii" <eliz@elta.co.il> wrote:

> > From: Barry Margolin <barmar@alum.mit.edu>
> > Newsgroups: gnu.emacs.bug
> > Date: Tue, 20 Jan 2004 07:39:34 GMT
> > 
> > I don't really have much problem with people using these derogatory 
> > nicknames in Usenet postings and similar media; this is an informal 
> > environment, and it's common to throw opinions and biases around in 
> > conversation.  But putting them in published software documentation just 
> > makes us all seem unprofessional and juvenile, and hurts the whole free 
> > and open software movement.
> 
> Just FYI, these names were in the manual since about forever,
> certainly before I came on board of Emacs maintenance circa 1993.
> Heck, even the name of the Texinfo source file for the MS-DOS appendix
> to the manual is msdog.texi.
> 
> So I think whatever juvenile and unprofessional attitude follows from
> this, it's been out there for so long that nothing can now change our
> image in people's eyes, and any damage it could have possibly done to
> the free software movement is already done.

Back in the old days, GNU software was mostly distributed within the 
self-contained hacker community.  We all were in on the joke, and used 
the same jargon and nicknames amongst ourselves.  The documentation was 
written with that target audience in mind.

Like it or not, though, times have changed.  *BSD and Linux are becoming 
mainstream software, which means that we have to expect that the 
documentation will be used by people not so clued in to this mindset.  
If we don't want to alienate the potential converts, I don't think we 
should perpetuate these attitudes in media intended for them.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

  parent reply	other threads:[~2004-01-20 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 22:30 Variant spellings in GNU Emacs documentation Reuben Thomas
2004-01-18 19:15 ` Richard Stallman
2004-01-18 22:28   ` Reuben Thomas
2004-01-19 20:12     ` Richard Stallman
     [not found] ` <mailman.865.1074453744.928.bug-gnu-emacs@gnu.org>
2004-01-18 23:16   ` David Kastrup
2004-01-19  6:27     ` Eli Zaretskii
     [not found]     ` <mailman.883.1074493658.928.bug-gnu-emacs@gnu.org>
2004-01-19  6:51       ` David Kastrup
2004-01-19  7:35         ` Eli Zaretskii
2004-01-19 12:07       ` Alan Mackenzie
2004-01-20  4:42         ` Richard Stallman
     [not found]         ` <mailman.969.1074573915.928.bug-gnu-emacs@gnu.org>
2004-01-20  7:39           ` Barry Margolin
2004-01-20  8:44             ` Eli Zaretskii
     [not found]             ` <mailman.978.1074588520.928.bug-gnu-emacs@gnu.org>
2004-01-20  9:47               ` David Kastrup
2004-01-20 22:31               ` Barry Margolin [this message]
2004-01-20 14:07             ` Sam Steingold

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=barmar-A2688C.17310120012004@netnews.comcast.net \
    --to=barmar@alum.mit.edu \
    /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).