From: Dan Christensen <jdc+news@uwo.ca>
Cc: ding@gnus.org
Subject: Re: self contained nnfolder
Date: Sun, 02 Sep 2001 23:35:29 -0400 [thread overview]
Message-ID: <873d65kku6.fsf@uwo.ca> (raw)
In-Reply-To: <vaf1ylp7d45.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Dan Christensen <jdc+news@uwo.ca> writes:
>
>> 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.
>> (And I did include the parentheses around it.) So I've set
>> gnus-secondary-select-methods to ((nnfolder "")). Will this
>> cause me some problems?
>
> Hm. You have (setq gnus-secondary-select-methods '("nnfolder:"))?
> And that doesn't work?
Nope. Here's the backtrace. (I tried to load gnus.el to get a
better backtrace, but got an error about gnuserv-start when doing
so.)
Debugger entered--Lisp error: (wrong-type-argument listp "nnfolder:")
gnus-server-to-method("nnfolder:")
#[(m) "\b;H\0Ä\b\x19\x1a ;\x14\0Å !F\0 \v\x1e\0\vF\0 @;/\0\n/\0Æ\n \"F\0 C\0\nC\0Ç !ÈC\0 F\0É !*\b" [m method group gnus-select-method nil gnus-server-to-method gnus-server-extend-method cadr "" gnus-server-add-address] 3]("nnfolder:")
mapcar(#[(m) "\b;H\0Ä\b\x19\x1a ;\x14\0Å !F\0 \v\x1e\0\vF\0 @;/\0\n/\0Æ\n \"F\0 C\0\nC\0Ç !ÈC\0 F\0É !*\b" [m method group gnus-select-method nil gnus-server-to-method gnus-server-extend-method cadr "" gnus-server-add-address] 3] ("nnfolder:" "archive"))
gnus-read-active-file(nil t)
gnus-setup-news(nil nil 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(nil t nil)
gnus(nil t)
jdc-gnus-no-server()
jdc-gnus()
call-interactively(jdc-gnus)
>>> Edit your .newsrc.eld (while Gnus is
>>> not running) to remove whichever entry from gnus-server-alist you
>>> don't want to use.
>>
>> I don't want to use "archive", but when I removed it from
>> gnus-server-alist I got an error message when Gnus started, even
>> though the string `archive' didn't appear anywhere in my .newsrc.eld
>> or my .gnus. When I remove the "" entry, everything was fine.
>> Is this a bug in gnus? It seems to have `archive' hardcoded
>> somewhere.
>
> I think normally people aren't supposed to set gnus-server-alist
> manually.
Yes, but mine seems wrong, and I'm just trying to get it back to
a sane state.
> I think Gnus looks is there is an archive server when it
> starts up. If an archive server is missing, it creates one. Now,
> maybe you set gnus-server-alist after Gnus created the archive server?
> Then Gnus got very confused that the archive server was missing even
> after it created it.
Gnus shouldn't have any record that it existed before, since there
is no mention of the word archive in any of my gnus related files.
>>> Edit your .gnus to make
>>> gnus-message-archive-method nil;
>>
>> I've got it set to (nnfolder "").
>
> Hm. No, that doesn't sound right. Or is (nnfolder "") without
> further parameters your normal mail select method?
Yes, it's my normal select method. (I do have lots of nnfolder
and nnmail variables set globally, but (I think) I only have one
mail server, so hopefully that's not a problem.)
Dan
next prev parent reply other threads:[~2001-09-03 3:35 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 [this message]
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
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=873d65kku6.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).