Gnus development mailing list
 help / color / mirror / Atom feed
From: Benjamin Rutt <brutt+news@bloomington.in.us>
Subject: Re: *Server* buffer problems when adding server parameters
Date: Fri, 24 Aug 2001 13:36:31 -0500	[thread overview]
Message-ID: <m3ae0pfgpc.fsf@brutt.maplenet.net> (raw)
In-Reply-To: <m3ofp52ye2.fsf@brutt.maplenet.net>

Benjamin Rutt <brutt+news@bloomington.in.us> writes:

> I'll G e it from *Group* and set it to just "archive" and try again.

Yes, that did the trick.  Why the select method got all fubar in the
first place remains a mystery.

Thanks for the help, Lars and Kai, and sorry for my misunderstanding
of what the select method should look like.  To defend myself, I think
the following line in gnus info threw me, when I was trying to learn
what he meant by "Have a peek at the select method of these groups":

,----[ from (Info-goto-node "(gnus)Select Methods") ]
| a select method is a list where the first element says what backend to
| use (e.g. `nntp', `nnspool', `nnml') and the second element is the
| "server name".  There may be additional elements in the select method,
| where the value may have special meaning for the backend in question.
`----

So, I figured that when lars asked me to check on the select method
for the groups, he was telling me to sure the second element of the
list making up the select method is the string "archive", which it
was.  I couldn't grok the idea that a select method was not a list,
since it said clearly that it is a list in the documentation above.
So, don't we have a doc bug in the above info node?  I'm sorry that I
don't know enough about a select method yet to know how to correct it,
though.  I'm thinking it could be revised to say something like "a
select method is either the server name as a string or a list where
the first element..."

If the above is a bug, then surely the following is a bug also,

,----[ from (Info-goto-node "(gnus)Terminology") ]
| "select method"
|      A structure that specifies the backend, the server and the virtual
|      server settings.
`----

unless by "structure" it is obvious to the reader that it can either
be a string or a list.

-- 
Benjamin


  reply	other threads:[~2001-08-24 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 19:55 Benjamin Rutt
2001-08-23 16:50 ` Lars Magne Ingebrigtsen
2001-08-24  4:03   ` Benjamin Rutt
2001-08-24  9:43     ` Kai Großjohann
2001-08-24 16:09       ` Benjamin Rutt
2001-08-24 13:56     ` Lars Magne Ingebrigtsen
2001-08-24 16:07       ` Benjamin Rutt
2001-08-24 16:41         ` Lars Magne Ingebrigtsen
2001-08-24 16:52           ` Benjamin Rutt
2001-08-24 18:36             ` Benjamin Rutt [this message]
2001-08-24 22:32               ` Kai Großjohann
2001-08-24 22:51                 ` Lars Magne Ingebrigtsen
2001-08-24 22:27           ` Kai Großjohann
2001-08-24 22:50             ` Lars Magne Ingebrigtsen
2001-08-24 22:53               ` Paul Jarc
2001-08-24 23:00                 ` Lars Magne Ingebrigtsen
2001-08-24 23:12                   ` Paul Jarc
2001-08-24 23:20                     ` Lars Magne Ingebrigtsen
2001-08-24 23:31                       ` Paul Jarc
2001-08-24 23:46                         ` Lars Magne Ingebrigtsen
2001-08-24 23:53                           ` Paul Jarc
2001-08-25  0:11                             ` Lars Magne Ingebrigtsen
2001-08-25  5:21                               ` Paul Jarc
2001-08-26 16:28               ` Kai Großjohann

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=m3ae0pfgpc.fsf@brutt.maplenet.net \
    --to=brutt+news@bloomington.in.us \
    /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).