From: Tim Landscheidt <tim@tim-landscheidt.de>
To: ding@gnus.org
Subject: Re: Quick survey of gnus-server-alist
Date: Tue, 17 Oct 2017 19:34:19 +0000 [thread overview]
Message-ID: <87bml5sh50.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <87d15o3y36.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> I'm trying to figure out how all the variables that hold Gnus' servers
> actually work. `gnus-server-alist' looks like it's meant to be a fairly
> authoritative list, but in my case it has never held anything but the
> archive server.
> If anyone wants to take twenty seconds and satisfy my curiosity -- does
> that variable hold anything else for you? Anything but the archive
> server?
> It looks like `gnus-server-method-cache' ends up actually holding the
> information that would also have gone in `gnus-server-alist'.
> Anyway, I hope some of you will humor me!
| ELISP> gnus-server-alist
| (("archive" nnfolder "archive"
| (nnfolder-directory "~/Mail/archive")
| (nnfolder-active-file "~/Mail/archive/active")
| (nnfolder-get-new-mail nil)
| (nnfolder-inhibit-expiry t))
| ("nntp.perl.org" nntp "nntp.perl.org")
| ("news.fernuni-hagen.de" nntp "news.fernuni-hagen.de")
| ("news.individual.de" nntp "news.individual.de")
| ("news.gnus.org" nntp "news.gnus.org")
| ("news.gmane.org" nntp "news.gmane.org"))
| ELISP> gnus-server-method-cache
| (("nnml:private" nnml "private")
| ("news.gnus.org" nntp "news.gnus.org")
| ("nntp.perl.org" nntp "nntp.perl.org")
| ("native" nnml "private")
| ("news.individual.de" nntp "news.individual.de")
| ("news.gmane.org" nntp "news.gmane.org")
| ("archive" nnfolder "archive"
| (nnfolder-directory "~/Mail/archive")
| (nnfolder-active-file "~/Mail/archive/active")
| (nnfolder-get-new-mail nil)
| (nnfolder-inhibit-expiry t)))
| ELISP>
Tim
next prev parent reply other threads:[~2017-10-17 19:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 21:22 Eric Abrahamsen
2017-10-16 5:57 ` Eric S Fraga
2017-10-16 15:39 ` Eric Abrahamsen
2017-10-17 6:32 ` Eric S Fraga
2017-10-17 14:51 ` Eric Abrahamsen
2017-10-16 7:06 ` Robert Pluim
2017-10-16 7:34 ` Julien Danjou
2017-10-16 12:49 ` Dan Christensen
2017-10-16 13:12 ` Dave Marquardt
2017-10-17 16:32 ` Eric Abrahamsen
2017-10-18 12:54 ` Dave Marquardt
2017-10-16 14:10 ` Peter Davis
2017-10-16 14:17 ` Adam Sjøgren
2017-10-16 14:29 ` Norman Walsh
2017-10-16 15:45 ` Eric Abrahamsen
2017-10-17 17:00 ` Jorge A. Alfaro-Murillo
2017-10-17 17:54 ` Steinar Bang
2017-10-17 19:34 ` Tim Landscheidt [this message]
2017-10-17 20:32 ` Eric Abrahamsen
2017-10-18 13:20 ` Sivaram Neelakantan
2017-10-18 16:27 ` Eric Abrahamsen
2017-10-19 12:08 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-10-20 19:02 ` Michael Sperber
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=87bml5sh50.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--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).