From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nnimap ports and protocols
Date: Fri, 01 Oct 2010 20:29:11 +0200 [thread overview]
Message-ID: <m34od54vig.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87d3rtyi8t.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> That seems like a reinvention of the customize facility. We can do a
> non-interactive customization of `gnus-connection-preferences' for
> instance and save the result. I think that's better.
That's be a whopping long alist that wouldn't be very understandable to
the customize interface. I think...
> Also the connection preferences need to be keyed by server name/server
> address regex with t as the default.
No, it would just store what it decided to do for exactly that server.
> If Customize is inadequate, I would put this in .newsrc.eld, not in a
> special new file. And I would allow `gnus-connection-preferences' to be
> a function called with the server name.
It could be stored in the .newsrc.eld, but we'd then have to supply a
mode to edit it, because the user will want to clear stuff out.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-01 18:29 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
2010-10-01 16:25 ` Lars Magne Ingebrigtsen
2010-10-01 16:45 ` Ted Zlatanov
2010-10-01 18:29 ` Lars Magne Ingebrigtsen [this message]
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=m34od54vig.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).