From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Cc: yamaoka@jpl.org, sxemacs-devel@sxemacs.org, emacs-devel@gnu.org
Subject: Re: Moving Gnus development to Emacs
Date: Sat, 02 Jan 2016 04:28:44 +0100 [thread overview]
Message-ID: <m3si2gaccz.fsf@gnus.org> (raw)
In-Reply-To: <microsoft-free.877fjw0zwp.fsf@steveyoungs.com> (Steve Youngs's message of "Thu, 31 Dec 2015 00:33:26 +1000")
Steve Youngs <steve@sxemacs.org> writes:
> > That would mean removing basically all compat code.
>
> OK, from where I sit, this would totally suck. :-( And anyone not
> wanting to use dev Emacs would just have to put it all back in.
>
> Any chance I could talk you out of it? Is there a compromise? Would it
> be possible/acceptable to leave in the existing compat code but not
> update it or use it for any new features from this point on? (I realise
> this wouldn't be possible every time)
Having different programming styles in the same functions is just
awkward. One talks about `gnus-union' and the other talks about
`cl-union' (or whatever). Somebody who tries to fix a bug will have to
examine `gnus-union' to see whether it does something weird, and then
discover that it's just the normal `cl-union'.
It's doable, of course, but it's not very readable.
> I don't mind having to bring my own glue to get the lastest and greatest
> shiny new feature working, but I don't want to glue stuff that has been
> working fine for me for the last 15 to 20 years.
Well, Gnus will still be working for you, but new features will have to
be ported gingerly, I'm afraid...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-01-02 3:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 11:43 Moving Gnus development to Emacs? Lars Magne Ingebrigtsen
[not found] ` <mailman.1827.1451475821.29210.sxemacs-devel-sxemacs.org@lists.sxemacs.org>
2015-12-30 14:33 ` Moving Gnus development to Emacs Steve Youngs
2015-12-30 15:15 ` Ivan Shmakov
2016-01-01 19:21 ` Steinar Bang
2016-01-02 3:28 ` Lars Magne Ingebrigtsen [this message]
2015-12-30 16:33 ` Moving Gnus development to Emacs? raman
2015-12-30 19:05 ` Jay Belanger
2015-12-30 19:25 ` Nikolaus Rath
2015-12-31 17:40 ` Lars Magne Ingebrigtsen
2015-12-31 18:35 ` Benjamin Slade
2015-12-30 18:44 ` John Wiegley
2015-12-31 0:46 ` Katsumi Yamaoka
2015-12-31 13:50 ` Eli Zaretskii
2015-12-31 9:18 ` Julien Danjou
2015-12-31 9:40 ` David Engster
2015-12-31 11:43 ` Michael Albinus
2015-12-31 12:29 ` CHENG Gao
2015-12-31 14:35 ` Xue Fuqiao
2015-12-31 14:52 ` CHENG Gao
2016-01-01 0:10 ` Xue Fuqiao
2016-01-01 7:02 ` CHENG Gao
2015-12-31 17:10 ` Lars Magne Ingebrigtsen
2015-12-31 17:15 ` Adam Sjøgren
2016-01-02 17:39 ` Lars Magne Ingebrigtsen
2016-01-02 20:31 ` Steinar Bang
2016-01-03 18:24 ` Bill Wohler
2016-01-04 0:48 ` Lars Magne Ingebrigtsen
2016-01-04 1:05 ` John Wiegley
2016-01-04 3:47 ` Steve Youngs
2016-01-06 7:18 ` Lars Magne Ingebrigtsen
2016-01-06 7:38 ` CHENG Gao
2016-01-06 8:50 ` Andreas Schwab
2016-01-25 15:07 ` Ted Zlatanov
2016-01-28 12:45 ` Greg Troxel
2015-12-31 10:15 ` Eric Abrahamsen
2015-12-31 17:43 ` Lars Magne Ingebrigtsen
2016-01-01 21:43 ` Göktuğ Kayaalp
2015-12-31 17:04 ` Uwe Brauer
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=m3si2gaccz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=sxemacs-devel@sxemacs.org \
--cc=yamaoka@jpl.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).