From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: imap.el and nnimap.el [was Re: Build failure bzr trunk revno 103260]
Date: Mon, 14 Feb 2011 11:45:24 -0800 [thread overview]
Message-ID: <87sjvq4cyz.fsf@gnus.org> (raw)
In-Reply-To: 87hbc6vf69.fsf@lifelogs.com
Ted Zlatanov <tzz@lifelogs.com> writes:
> Gnus itself needs imap.el only in one place (mail-source.el) so I
> propose we move imap.el to Emacs and out of Gnus when and if that
> dependency is removed. It's a general-purpose library anyway.
I wonder whether it might make some sense to re-separate out some of the
more basic IMAP stuff from nnimap.el again. nnimap.el slurped in all
the protocol-specific stuff from imap.el so that it could implement what
Gnus needed more efficiently, but there isn't really much reason why,
say, the login functions (and related) could be separated out again.
Then non-Gnus packages could just use this new stripped-down basic IMAP
library. I think, basically, what most useful is the login functions
and a simple `imap-command' function, and the rest would be application
specific.
I've had a peek at the relevant nnimap and mail-source functions, and it
seems like it should be doable in a pretty clean fashion.
However, if the new basic IMAP library is called imap.el, then this
would still break third-party applications.
Thoughts?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-02-14 19:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 23:11 Build failure bzr trunk revno 103260 Tim Cross
2011-02-14 0:38 ` Les Harris
2011-02-14 0:39 ` Ted Zlatanov
2011-02-14 1:22 ` Glenn Morris
2011-02-14 1:53 ` Glenn Morris
2011-02-14 2:08 ` Ted Zlatanov
2011-02-14 3:00 ` imap.el and nnimap.el [was Re: Build failure bzr trunk revno 103260] Glenn Morris
2011-02-14 14:55 ` Ted Zlatanov
2011-02-14 19:45 ` Lars Ingebrigtsen [this message]
2011-02-14 19:47 ` Lars Ingebrigtsen
2011-02-14 20:52 ` Ted Zlatanov
2011-02-14 21:13 ` Lars Ingebrigtsen
2011-02-14 21:28 ` Ted Zlatanov
2011-02-14 22:11 ` Lars Ingebrigtsen
2011-02-15 15:58 ` Chong Yidong
2011-02-16 21:30 ` Lars Ingebrigtsen
2011-02-14 20:17 ` imap.el and nnimap.el Glenn Morris
2011-02-14 20:48 ` Ted Zlatanov
2011-02-14 3:41 ` Build failure bzr trunk revno 103260 Tim Cross
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=87sjvq4cyz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=emacs-devel@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 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).