Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc+news@uwo.ca>
Cc: ding@gnus.org
Subject: Re: self contained nnfolder
Date: Mon, 03 Sep 2001 11:01:54 -0400	[thread overview]
Message-ID: <871ylomi71.fsf@uwo.ca> (raw)
In-Reply-To: <vafvgj060ia.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> prj@po.cwru.edu (Paul Jarc) writes:
>
>> Dan Christensen <jdc+news@uwo.ca> wrote:
>> > prj@po.cwru.edu (Paul Jarc) writes:
>>>> gnus-secondary-select-methods should
>>>> also be nil, or, if you want your foreign nnfolder server to also be
>>>> secondary, use '("nnfolder:").  
>>> 
>>> This didn't work.  I got an error that "nnfolder:" wasn't a list.
>>
>> Hm.  Well, do you really need it to be both foreign and secondary?
>> If it's foreign only, then Gnus won't check it for new groups, I
>> think.  If it's secondary only, then you have to change it by editing
>> your .gnus, not in the *Server* buffer.
>
> I think that the following is permissible:
>
> (1) Create a server foo via the server buffer.
> (2) (add-to-list 'gnus-secondary-select-methods "foo")

I tried the following settings for g-secondary-select-methods:

      '((nnfolder "")) 
      '("nnfolder:")
      '("")
      nil

The first one works for me in all the cases I tested.  The second
never works.  The third and forth gave me errors when "nnfolder:" was
used in my .newsrc as the server for each group in gnus-newsrc-alist,
but is ok when "" is used as the server for each group.  Here's an
example of the backtrace I get when I start gnus with
gnus-secondary-select-methods set to nil and one of my groups
(nnfolder:house) has "nnfolder:" as its method:

Debugger entered--Lisp error: (error "Trying to require a method that doesn't exist")
  signal(error ("Trying to require a method that doesn't exist"))
  error("Trying to require a method that doesn't exist")
  gnus-server-opened((nil ""))
  gnus-activate-group("nnfolder:house" scan)
  gnus-get-unread-articles(2)
  gnus-setup-news(nil 2 t)
  byte-code("\b„\x0e\0	„\x0e\0Æ ˆ‚O\0ÇÈ!ˆÉ\n!\x13\f„\x1e\0\rƒ!\0Ê ˆ\x0e\x19ƒ.\0Ë ˆÌÍÎ\"ˆÏÐ\x0e\x1a\b#ˆÇÑ!ˆÒ ˆÓ\x0e\x1a!ˆÔ ˆÕÖ!ˆ× ˆÇØ!ˆÐ‡" [dont-connect did-connect gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook gnus-use-grouplens level] 4)
  gnus-1(2 t nil)
  gnus(2 t nil)
  gnus-no-server-1(nil nil)
  gnus-no-server(nil)
* call-interactively(gnus-no-server)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

If I change nnfolder:house's method to "" this error goes away.
This seems pretty strange to me.

So now I've made all my groups use "" and have
gnus-secondary-select-methods set to '("").

-- 
Dan Christensen
jdc+news@uwo.ca


  reply	other threads:[~2001-09-03 15:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-25 16:53 Simon Josefsson
2001-08-26 16:30 ` Raymond Scholz
2001-08-26 21:20   ` Simon Josefsson
2001-08-26 22:24     ` Nevin Kapur
2001-08-27  1:22       ` Steve Youngs
2001-08-27 16:19       ` Simon Josefsson
2001-08-27 16:36         ` Nevin Kapur
2001-09-01 22:22 ` Dan Christensen
2001-09-01 23:03   ` Dan Christensen
2001-09-01 23:31     ` Kai Großjohann
2001-09-02  6:34     ` Paul Jarc
2001-09-01 23:26   ` Kai Großjohann
2001-09-02  4:41     ` Dan Christensen
2001-09-02  6:11       ` Paul Jarc
2001-09-02 10:36         ` Kai Großjohann
2001-09-02 15:51         ` Dan Christensen
2001-09-02 16:48           ` Kai Großjohann
2001-09-02 23:58             ` Paul Jarc
2001-09-03  3:35             ` Dan Christensen
2001-09-03 10:16               ` Kai Großjohann
2001-09-03 15:07                 ` Dan Christensen
2001-09-03 16:31                   ` Kai Großjohann
2001-09-04  1:22                     ` Dan Christensen
2001-09-03 23:51                 ` Paul Jarc
2001-09-04  1:38                   ` Dan Christensen
2001-09-04  6:58                     ` Paul Jarc
2001-09-04 14:45                       ` Dan Christensen
2001-09-02 23:54           ` Paul Jarc
2001-09-03  3:49             ` Dan Christensen
2001-09-03 15:12               ` Dan Christensen
2001-09-03 23:36               ` Paul Jarc
2001-09-03 10:18             ` Kai Großjohann
2001-09-03 15:01               ` Dan Christensen [this message]
2001-09-03 15:22                 ` Dan Christensen
2001-09-03 16:34                   ` Kai Großjohann
2001-09-03 17:00                     ` Amos Gouaux
2001-09-03 21:31                       ` Kai Großjohann
2001-09-03 23:17                         ` Paul Jarc
2001-09-04  0:43                         ` Amos Gouaux
2001-09-04 13:41                           ` Kai Großjohann
2001-09-04 14:10                             ` Amos Gouaux
2001-09-03 23:23                   ` Paul Jarc
2001-09-04  1:14                     ` Dan Christensen
2001-09-04  1:33                     ` Dan Christensen
2001-09-04 13:42                     ` Kai Großjohann
2001-09-02  9:53   ` Simon Josefsson

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=871ylomi71.fsf@uwo.ca \
    --to=jdc+news@uwo.ca \
    --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).