From: David Kastrup <dak@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Strange change in bytecmop.el
Date: Mon, 25 Jul 2005 19:21:21 +0200 [thread overview]
Message-ID: <85ll3uvm26.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1Dx5QS-0004ce-Ty@fencepost.gnu.org> (Richard M. Stallman's message of "Mon, 25 Jul 2005 12:03:32 -0400")
"Richard M. Stallman" <rms@gnu.org> writes:
> Sure. As long as we have code intended to run with XEmacs, calling it
> anything but code intended to run with XEmacs would be obfuscate.
>
> The option we're actually talking about is not obfuscated.
>
> (if (featurep 'emacs)
> ...
> ...)
Frankly, I can't make head nor tails out of it. If this is supposed
to differentiate just XEmacs (and it will rule out any older version
of Emacs, too, as collateral), then I find it offensive that the
_default_ code path is for XEmacs, and we have to make an _exception_
for Emacs. This is so backwards that I consider it repulsive.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-07-25 17:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 21:49 Strange change in bytecmop.el Stefan Monnier
2005-07-21 23:12 ` Juanma Barranquero
2005-07-22 19:43 ` Stefan Monnier
2005-07-22 22:52 ` Richard M. Stallman
2005-07-23 18:45 ` Stefan Monnier
2005-07-24 14:41 ` Richard M. Stallman
2005-07-24 16:44 ` David Kastrup
2005-07-25 1:43 ` Richard M. Stallman
2005-07-25 1:59 ` David Kastrup
2005-07-25 11:39 ` Robert J. Chassell
2005-07-25 12:51 ` David Kastrup
2005-07-25 16:03 ` Richard M. Stallman
2005-07-25 17:21 ` David Kastrup [this message]
2005-07-26 8:12 ` Juanma Barranquero
2005-07-26 8:44 ` David Kastrup
2005-07-26 10:09 ` Juanma Barranquero
2005-07-26 12:38 ` David Kastrup
2005-07-26 12:58 ` Juanma Barranquero
2005-07-28 22:04 ` Kim F. Storm
2005-07-24 14:41 ` Richard M. 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=85ll3uvm26.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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.