From: Simon Josefsson <jas@extundo.com>
Cc: emacs-devel@gnu.org
Subject: Re: pop3.el itegration with netrc.el
Date: Thu, 14 Oct 2004 20:56:41 +0200 [thread overview]
Message-ID: <ilulle9xh5i.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nis9dgn88.fsf@lifelogs.com>
"Ted Zlatanov" <tzz@lifelogs.com> writes:
>> Btw, is it difficult to modularize gnus-encrypt.el into, say,
>> encrypt.el, that doesn't use a lot of Gnus functions? I recall some
>> discussions about that, though.
>
> This may be a good time to make that break. The current
> gnus-encrypt.el can be turned into encrypt.el with very few changes
> except for the dependency on password.el, which is in Gnus.
We can install password.el in Emacs.
> The root problem is that netrc.el is a part of Gnus I can't break out
> (I think)
Why not? Doing so seem like a good idea, to me. netrc.el doesn't
call any Gnus functions, except for gnus-encrypt, as far as I can
tell. And if we (you) move gnus-encrypt.el to encrypt.el, all will be
fine, I think.
> so the Gnus version of pop3.el will have a dependency we don't want.
pop3.el would depend on netrc.el, which would depend on encrypt.el,
which would depend on password.el. All small files, and no Gnus
dependencies.
next prev parent reply other threads:[~2004-10-14 18:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 15:44 Ted Zlatanov
2004-10-14 18:21 ` Simon Josefsson
2004-10-14 18:37 ` Ted Zlatanov
2004-10-14 18:56 ` Simon Josefsson [this message]
2004-10-14 18:49 ` Reiner Steib
2004-10-14 19:01 ` Simon Josefsson
2004-10-14 19:52 ` Reiner Steib
2004-10-14 22:39 ` Simon Josefsson
2004-10-15 17:08 ` Ted Zlatanov
2004-10-15 17:43 ` Simon Josefsson
2004-10-15 19:07 ` Ted Zlatanov
2004-10-15 19:16 ` Reiner Steib
2004-10-17 23:13 ` Miles Bader
2004-10-18 18:30 ` Ted Zlatanov
2004-10-21 18:35 ` Ted Zlatanov
2004-10-15 18:07 ` Reiner Steib
2004-10-15 19:14 ` encrypt.el (was: pop3.el itegration with netrc.el) Ted Zlatanov
[not found] ` <iluwtxrvkfb.fsf@latte.josefsson.org>
[not found] ` <E1CIozF-00034v-V7@fencepost.gnu.org>
[not found] ` <4n4qkrvrwu.fsf@lifelogs.com>
[not found] ` <E1CJx6h-0000Ns-QW@fencepost.gnu.org>
[not found] ` <4nsm87vrgk.fsf@lifelogs.com>
[not found] ` <4nr7m9j1ah.fsf@lifelogs.com>
2004-12-01 22:12 ` encrypt.el Reiner Steib
2004-12-02 16:36 ` encrypt.el Ted Zlatanov
2004-12-02 20:56 ` encrypt.el Reiner Steib
2004-12-07 17:50 ` encrypt.el Ted Zlatanov
2004-10-15 17:48 ` pop3.el itegration with netrc.el Reiner Steib
2004-10-15 17:58 ` Simon Josefsson
2004-10-15 18:55 ` Reiner Steib
2004-10-17 23:22 ` Miles Bader
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=ilulle9xh5i.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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.
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).