From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap ports and protocols
Date: Fri, 01 Oct 2010 10:46:57 -0500 [thread overview]
Message-ID: <87lj6hyky6.fsf@lifelogs.com> (raw)
In-Reply-To: <m3eica9bbk.fsf@quimbies.gnus.org>
On Fri, 01 Oct 2010 17:34:07 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Frank Schmitt <ich@frank-schmitt.net> writes:
>> I'd use the customize framework. This gives the added benefit of a ready
>> GUI for manually tweaking the saved info.
LMI> This data wouldn't be variables as such. It'd be, like "connecting to
LMI> imap server foo is done on port bar using method zot". Does that work
LMI> in the customize framework? I'm not sure how I would express that...
LMI> Or to take a different example -- using tls.el to connect to a server.
LMI> Then it would be nice if we'd tried gnutls-cli once, and saw it fail,
LMI> and that openssl worked, that we could save that in some way.
My example on extending nnimap-stream could handle this (posted earlier
this morning in this thread).
Another approach is to add a customizeable alist to control this
preference.
Yet another is to save a "nnimap-stream" token in the netrc file.
Ted
next prev parent reply other threads:[~2010-10-01 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:55 Lars Magne Ingebrigtsen
2010-10-01 1:00 ` Daniel Pittman
2010-10-01 13:43 ` Ted Zlatanov
2010-10-01 14:52 ` Ted Zlatanov
2010-10-01 15:19 ` Lars Magne Ingebrigtsen
2010-10-01 15:29 ` Frank Schmitt
2010-10-01 15:34 ` Lars Magne Ingebrigtsen
2010-10-01 15:46 ` Ted Zlatanov [this message]
2010-10-01 16:25 ` Lars Magne Ingebrigtsen
2010-10-01 16:45 ` Ted Zlatanov
2010-10-01 18:29 ` Lars Magne Ingebrigtsen
2010-10-01 18:41 ` Ted Zlatanov
2010-10-01 18:47 ` Lars Magne Ingebrigtsen
2010-10-01 19:05 ` Ted Zlatanov
2010-10-01 19:17 ` Lars Magne Ingebrigtsen
2010-10-01 19:44 ` Ted Zlatanov
2010-10-01 18:18 ` Sivaram Neelakantan
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=87lj6hyky6.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).