all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Aidan Kehoe <kehoea@parhasard.net>
Cc: emacs-pretest-bug@gnu.org, simon.marshall@misys.com,
	emacs-devel@gnu.org, bug-cc-mode@gnu.org,
	monnier@iro.umontreal.ca, Alan Mackenzie <acm@muc.de>
Subject: Re: [simon.marshall@misys.com: Font Lock on-the-fly misfontification in C++]
Date: Wed, 2 Aug 2006 11:38:48 +0200	[thread overview]
Message-ID: <17616.29352.887502.516153@parhasard.net> (raw)
In-Reply-To: <E1G7hfv-0003LK-H9@fencepost.gnu.org>


 Ar an t-aonú lá is triochad de mí Iúil, scríobh Richard Stallman: 

 > To speak of "GNU Emacs" and "XEmacs" gives the impression that XEmacs has
 > nothing to do with GNU. Since XEmacs is a forked version of Emacs, that
 > is a misleading impression. Please write "Emacs" and "XEmacs", or else
 > "GNU Emacs" and "GNU XEmacs".

Substantial parts of the code of XEmacs are not copyrighted by the FSF, the
legal entity stewarding the GNU project, and this is almost certain to
remain so. The XEmacs project members do not consider the advancement of the
GNU project as a significant part of our job. We use the term XEmacs, we
never use the term GNU XEmacs.

While there is an argument for the term GNU XEmacs, it is not stronger than
the argument for the term FSF Emacs; we have stopped using the latter out of
respect for the maintainers of GNU Emacs. If you want to be wilfully
disrespectful to the members of the XEmacs project, use GNU XEmacs to refer
to the editor; otherwise, the established usage, XEmacs on its own, will
raise fewer hackles and doesn’t require you to think extra hard every time
you mention the editor. 

-- 
Santa Maradona, priez pour moi!

  parent reply	other threads:[~2006-08-02  9:38 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1G3OAq-0004WV-P1@fencepost.gnu.org>
2006-07-23 14:26 ` [simon.marshall@misys.com: Font Lock on-the-fly misfontification in C++] Alan Mackenzie
2006-07-24  3:11   ` Stefan Monnier
2006-07-24 13:33     ` Alan Mackenzie
2006-07-24 14:36       ` Stefan Monnier
2006-07-24 19:29         ` Alan Mackenzie
2006-07-24 20:43           ` Stefan Monnier
2006-07-24 22:29             ` Alan Mackenzie
2006-07-24 22:30               ` Stefan Monnier
2006-07-24 14:35   ` Stefan Monnier
2006-07-31 22:04     ` Alan Mackenzie
2006-07-31 22:03       ` Stefan Monnier
2006-08-01  9:21         ` Alan Mackenzie
2006-08-01 14:55           ` Stefan Monnier
2006-08-01 19:48             ` Alan Mackenzie
2006-08-01 19:23               ` Stefan Monnier
2006-08-03  8:45                 ` Alan Mackenzie
2006-08-03 15:12                   ` Stefan Monnier
2006-07-31 23:59       ` Richard Stallman
2006-08-01  7:59         ` Alan Mackenzie
2006-08-01  8:32           ` David Kastrup
2006-08-01 20:09           ` Richard Stallman
2006-08-01  8:06         ` Romain Francoise
2006-08-01 20:09           ` Richard Stallman
2006-08-02  9:38         ` Aidan Kehoe [this message]
2006-08-02  9:57           ` David Kastrup
2006-08-02 10:28             ` Aidan Kehoe
2006-08-02 11:57               ` David Kastrup
2006-08-02 12:52                 ` Aidan Kehoe
2006-08-02 13:21                   ` David Kastrup
2006-08-02 13:31                     ` Aidan Kehoe
2006-08-02 14:02                       ` David Kastrup
2006-08-02 13:59                 ` Stefan Monnier
2006-08-02 14:12                   ` Aidan Kehoe
2006-08-02 14:14                   ` David Kastrup
2006-08-02 21:20             ` Richard Stallman
2006-08-03  9:17               ` Alan Mackenzie
2006-08-03  8:42                 ` David Kastrup
2006-08-03  8:54                   ` Aidan Kehoe
2006-08-03 19:15                 ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17616.29352.887502.516153@parhasard.net \
    --to=kehoea@parhasard.net \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=simon.marshall@misys.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.