Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Quick survey of gnus-server-alist
Date: Mon, 16 Oct 2017 08:45:07 -0700	[thread overview]
Message-ID: <87o9p7xfjw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87vajfjhdp.fsf@nwalsh.com>

Thanks to you all! That was enough information to solve the mystery:
gnus-server-alist holds servers automatically created by Gnus, *plus*
the servers that you've created using "a" in the *Server* buffer. Not
the servers you've defined in your gnus.el.

Which makes sense: gnus-server-alist is kept in newsrc.eld, and takes
care of saving servers that you've created through the Gnus interface.
It doesn't touch servers you've defined yourself using
select-method/secondary-select-methods in gnus.el.

This is important as I look at turning servers into actual class
objects.

More docstrings and better errors are in order!

Thanks again to everyone,
Eric





  reply	other threads:[~2017-10-16 15:45 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 [this message]
2017-10-17 17:00 ` Jorge A. Alfaro-Murillo
2017-10-17 17:54 ` Steinar Bang
2017-10-17 19:34 ` Tim Landscheidt
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=87o9p7xfjw.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).