From: Adrian Aichner <adrian@xemacs.org>
Subject: Re: Is it planned to remove xemacs compatibility code?
Date: Tue, 26 Oct 2004 23:17:29 +0200 [thread overview]
Message-ID: <4qkhyyae.fsf@smtprelay.t-online.de> (raw)
In-Reply-To: x5k6tdw5yl.fsf@lola.goethe.zz
David Kastrup <dak@gnu.org> writes:
> Jay Belanger <belanger@truman.edu> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>>> Around Emacs code, I find many Xemacs compatibility code as
>>>> (cond ((featurep 'xemacs) blah ...)
>>>> (if (featurep 'xemacs) blah ...)
>>>
>>> Those files are typically also distributed separately from Emacs
>>> for older Emacsen or for XEmacs, so it is better to keep this code
>>> so as to minimize the difference between the version bundled with
>>> Emacs and the other version: any difference tends to lead to
>>> problems keeping the files in sync.
>>
>> What about the files that aren't distributed separately?
>
> As long as we don't get big amounts of unmaintable cruft and as long
> as there is some reasonable chance that the code will help the XEmacs
> developers catch up with it, I'd leave it in. If one thinks that the
> stuff is falling into bit rot anyway, it may be an idea to ask on the
> xemacs-devel@xemacs.org whether somebody there volunteers to actively
Hi David, make that xemacs-design@xemacs.org and we'll take note :-)
That's a good suggestion!
Best regards,
Adrian
> keep it working inside of the Emacs CVS (requires copyright
> assignment). If not, it is probably saner to just pull it instead of
> giving the XEmacs crowd something that only pretends to work with
> XEmacs.
>
>> Also, the manuals of some bundled packages have installation
>> instructions; should these be kept?
>
> As long as we are maintaining the manuals separately, I don't see any
> point in including either installation instructions for Emacs or
> XEmacs, if the respective version of the package is already installed
> with Emacs. If there is no manual available outside of the Emacs CVS,
> this is probably a situation that is a bit unfortunate. Again, I'd
> then ask on the XEmacs list whether somebody wants to maintain the
> respective section (which can probably be removed by conditional
> compilation) here, and pull it only if nobody can be found willing to
> maintain those parts. Keeping possibly outdated and incorrect
> documentation around will help nobody.
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/
next prev parent reply other threads:[~2004-10-26 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 16:26 Is it planned to remove xemacs compatibility code? CHENG Gao
2004-10-26 18:24 ` Stefan Monnier
2004-10-26 19:14 ` Jay Belanger
2004-10-26 21:00 ` David Kastrup
2004-10-26 21:17 ` Adrian Aichner [this message]
2004-10-27 6:29 ` Cheng Gao
2004-10-27 17:35 ` Richard Stallman
2004-10-26 21:13 ` Stefan Monnier
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=4qkhyyae.fsf@smtprelay.t-online.de \
--to=adrian@xemacs.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).