From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Wed, 01 Feb 2012 13:07:15 -0500 [thread overview]
Message-ID: <87y5smxwa4.fsf@lifelogs.com> (raw)
In-Reply-To: <871uqey9t4.fsf@gnus.org>
On Wed, 01 Feb 2012 14:15:03 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> I think Ma Gnus should drop Emacs 22 compatibility, and it should also
LI> drop non-Mule XEmacs compatibility.
LI> More controversially :-), I think 真 Gnus should also stop defining
LI> compatibility functions like `gnus-mark-active-p', and instead just
LI> start maintaining a `gnus-compat.el' library that would define functions
LI> like `mark-active-p' for Emacsen that don't define them.
LI> This will make the source code more readable, I think.
I am 100% in favor of both. But gnus-compat.el could be an ELPA package
so other packages and users can have the same functionality. Which
reminds me, are you interested in packaging Ma Gnus as an ELPA package?
That would let us pull its source code out of Emacs, except for the
pieces that Emacs wants, and would make installation easier.
Ted
next prev parent reply other threads:[~2012-02-01 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 13:15 Lars Ingebrigtsen
2012-02-01 13:37 ` Steinar Bang
2012-02-01 18:07 ` Ted Zlatanov [this message]
2012-02-01 19:40 ` Lars Ingebrigtsen
2012-02-02 7:40 ` Reiner Steib
2012-02-02 8:51 ` Michael Albinus
2012-02-02 8:59 ` David Engster
2012-02-02 9:47 ` Lars Ingebrigtsen
2012-02-02 10:43 ` Michael Albinus
2012-02-02 10:51 ` Lars Ingebrigtsen
2012-02-02 12:26 ` Michael Albinus
2012-02-02 12:32 ` Lars Ingebrigtsen
2012-02-02 13:02 ` Michael Albinus
2012-02-02 13:28 ` Lars Ingebrigtsen
2012-02-02 13:39 ` Michael Albinus
2012-02-02 13:03 ` Ted Zlatanov
2012-02-02 13:29 ` Lars Ingebrigtsen
2012-02-02 13:57 ` Ted Zlatanov
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=87y5smxwa4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).