Re: nnimap ports and protocols

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> My example on extending nnimap-stream could handle this (posted earlier
> this morning in this thread).

Yes, that would work, but I find that variables that have complex
syntaxes (and we have enough of them) are something users fiddle with
and complain when they break, so if that could be avoided, it would be a
plus. 

> Yet another is to save a "nnimap-stream" token in the netrc file.

This is my current idea I had like five minutes ago, so it should be
great.  :-)  To take nnimap-stream as the example:

1) we'd change the default to nil, signalling that we want Gnus to
figure it out on its own.  If it has a value, then the user has
obviously chosen it, which makes the rest of the stuff irrelevant.

2) if it's nil, then we're in DWIM mode.  We then call
(nnimap-guess-connection-method server).  It'd try the stuff we talked
about earlier, and return its result.

3) this is saved in a new Gnus/Emacs file, called...  er...
~/emacs.d/emacs-memoize, which would have a format like

(nnimap connection-method ("imaps" ssl))

one per line, so that the user can edit it by hand, if necessary.  The
meaning here would be DOMAIN (so that many different packages can use
the same mechanism), TOKEN (that has some meaning in that domain), and
the VALUE.

4) nnimap would call this with the macro
(gnus-memoize 'nnimap 'connection-method
  (nnimap-guess-connection-method server))

So it's like a normal memoizer, only it saves stuff to a file, too.

Does this sound halfway sane?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen