From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Wed, 01 Feb 2012 20:40:26 +0100 [thread overview]
Message-ID: <87vcnq736d.fsf@gnus.org> (raw)
In-Reply-To: <87y5smxwa4.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 01 Feb 2012 13:07:15 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> 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've now started this, with `delete-directory' as the first victim. It
redefines it to have the `recursive' parameter, if it doesn't already.
I know this is really bad engineering. I know this is pretty much a
maintainability nightmare. If all packages redefined Emacs core
functions willy-nilly, Emacs would become totally unusable.
But enough is enough. Bring your Emacsen up to par, or be redefined.
> 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.
There's already an fsf-compat package that people use. If somebody
wants to take stuff out of gnus-compat and put it there, that's fine.
> Which reminds me, are you interested in packaging Ma Gnus as an ELPA
> package?
Not really. Ma Gnus is going to be seriously unstable if I'm able to
type fast enough. :-)
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-02-01 19:40 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
2012-02-01 19:40 ` Lars Ingebrigtsen [this message]
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=87vcnq736d.fsf@gnus.org \
--to=larsi@gnus.org \
--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).