From: Carsten Dominik <carsten.dominik@gmail.com>
To: Org-Mode List <emacs-orgmode@gnu.org>
Subject: Support (or not) for Emacs 21, and XEmacs
Date: Wed, 14 Apr 2010 10:15:02 +0200 [thread overview]
Message-ID: <15649C3E-517D-433D-977F-06008C20A4F4@gmail.com> (raw)
Hi everyone,
I am, once again, reconsidering support for Emacs 21 and XEmacs
in Org-mode.
Supporting older versions of Emacsen does make the code in
Org-mode more complex, needs time to rewrite or copy features
that do exist in newer versions of Emacs. Also, it slows down
the process of updating the version of Org-mode distributed
with Emacs, because the compatibility code makes it often hard to
comply with Emacs rules and practices.
What I would like to do is the following.
We are now working toward release 7.0 of Org-mode, which will
hopefully see full integration of org-babel. I am considering
to make Org-mode version 6.35 the last version of Org-mode
supporting XEmacs and Emacs 21. That would mean that I would
still fix critical bugs in 6.35 and keep that package on the
website indefinitely. So people stuck with Emacs 21 and XEmacs do
have an excellent version of Org-mode available. Git users will
be able indefinitely to select this version of Org-mode to support
and Emacs 21 or XEmacs installation.
For version 7.0 I would then not only stop actively supporting
these older Emacsen, but I would actually remove some of the
twisted code that has accumulated over the years in order to
support older versions. Important examples are all the
stuff in org-compat, but also key bindings and other stuff. There
are about 100 cases of (featurep 'xemacs) in the sources, and many
other places where I have to check for the availablility of a
specific feature or function.
If you object to such a development, please step into this
discussion.
- Carsten
next reply other threads:[~2010-04-14 8:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:15 Carsten Dominik [this message]
2010-04-16 10:26 ` Support (or not) for Emacs 21, and XEmacs Carsten Dominik
2010-04-16 10:27 ` Carsten Dominik
2010-04-16 12:19 ` Matt Lundin
2010-04-16 16:41 ` Carsten Dominik
2010-04-16 13:03 ` Sebastian Rose
2010-04-16 13:13 ` Bernt Hansen
2010-04-16 14:39 ` Carsten Dominik
2010-04-16 14:42 ` Bernt Hansen
2010-04-16 14:42 ` Carsten Dominik
2010-04-16 19:15 ` Bernt Hansen
2010-04-16 22:02 ` Carsten Dominik
2010-04-16 13:32 ` Rémi Vanicat
2010-04-16 13:56 ` Sebastian Rose
2010-04-16 13:07 ` Jan Böcker
2010-04-16 13:47 ` Günter Kolousek
2010-04-17 15:39 ` Michael Sperber
2010-04-17 20:31 ` Carsten Dominik
2010-04-18 8:22 ` Michael Sperber
2010-04-18 14:03 ` Carsten Dominik
2010-04-19 11:00 ` Michael Sperber
2010-04-19 11:19 ` Michael Sperber
2010-04-19 15:51 ` Carsten Dominik
2010-04-19 15:54 ` Michael Sperber
2010-04-19 15:55 ` Carsten Dominik
2010-04-19 15:59 ` Carsten Dominik
2010-05-07 7:51 ` Carsten Dominik
2010-05-07 8:30 ` Michael Sperber
2010-05-07 9:21 ` Carsten Dominik
2010-04-23 15:50 ` Michael Sperber
2010-04-23 19:03 ` Carsten Dominik
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=15649C3E-517D-433D-977F-06008C20A4F4@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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 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.