Gnus development mailing list
 help / color / mirror / Atom feed
From: Vin Shelton <acs@alumni.princeton.edu>
Subject: Re: Error when restarting gnus
Date: Tue, 16 Jul 2002 22:52:29 -0400	[thread overview]
Message-ID: <m2d6tnjcb6.fsf@zion.rcn.com> (raw)
In-Reply-To: <m2eleatuol.fsf@zion.rcn.com> (Vin Shelton's message of "Thu, 11 Jul 2002 06:39:38 -0400")

Sorry to follow-up my own post, but I've gotten no responses.
Since I changed:
(setq
...
      gnus-secondary-select-methods
      '((nnml "")
	(nnfolder))

to:
...

         (nnfolder ""))

I have not seen the error again.  I hope that this really is the
correct fix, and that this report can prove useful to anyone else who
has the same problem in the future.

Vin Shelton <acs@xemacs.org> writes:
> I recently added nnfolder to my list of backends.  If I let gnus sit
> idle for an hour or so, then quit gnus and restart it, here is the
> backtrace I get:
>
>
> Signaling: (wrong-type-argument stringp nil)
>   insert-file-contents-internal(nil nil nil nil nil nil nil)
>   insert-file-contents(nil)
>   byte-code("..." [file coding-system-for-read auto-mode-alist file-name-coding-system nnmail-pathname-coding-system nnmail-file-coding-system mm-auto-mode-alist insert-file-contents t] 3)
>   nnmail-find-file(nil)
>   nnfolder-request-list(nil)
>   gnus-request-list((nnfolder))
>   gnus-read-active-file-1((nnfolder) nil)
>   gnus-read-active-file(nil nil)
>   gnus-setup-news(nil nil nil)
>   byte-code("..." [gnus-slave gnus-current-startup-file gnus-startup-file did-connect level dont-connect 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-dribble-file gnus-use-grouplens] 4)
>   gnus-1(nil nil nil)
>   gnus(nil)
>   call-interactively(gnus)
>   command-execute(gnus t)
>   execute-extended-command(nil)
>   call-interactively(execute-extended-command)
>
>
> I'm running a gnus built from CVS on July 9, under XEmacs 21.4.
> Here's the part of my .gnus.el file that deals with nnfolder:
>
> (setq nnfolder-directory "~/Mail/archive")
> (setq gnus-parameters
>       '(("nnfolder:xemacs-patches\\..*"
> 	 ; Setting gnus-visible-headers has no effect.
> 	 ; Ideally, we would just add Message-id to gnus-visible-headers,
> 	 ; so I can use 'msgid' to save the message.
> 	 ; I'll make all headers visible instead (yuck!).
> ;	 (gnus-visible-headers "^From:\\|^Newsgroups:\\|^Subject:\\|^Date:\\|^Summary:\\|^Keywords:\\|^To:\\|^[BGF]?Cc:\\|^Posted-To:\\|^Resent-From:\\|^X-Sent:\\|^Message-[Ii][Dd]:")
> 	 (gnus-show-all-headers t)
> 	 (gnus-large-newsgroup 2000)
> 	 (display . all))))
> (setq gnus-move-split-methods
>       '(((equal gnus-newsgroup-name "gnu.emacs.sources") "nnml:emacs")
> 	((equal gnus-newsgroup-name "rec.humor.funny") "nnml:humor"))
>       nnmail-spool-file acs::mailspool
>       nnmail-keep-last-article nil	; t if using exmh
> ;      nnmail-delete-incoming nil	; save a copy of incoming mail
>       gnus-secondary-select-methods
>       '((nnml "")
> 	(nnfolder))
>       nnmh-get-new-mail nil
>       nnmh-be-safe t
>       nnml-get-new-mail t
>       gnus-treat-display-smileys nil	; don't smilify by default
>       gnus-large-newsgroup 1000)
>
> What am I doing wrong?
>
> Thanks in advance,
>    Vin

  - Vin



  reply	other threads:[~2002-07-17  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11 10:39 Vin Shelton
2002-07-17  2:52 ` Vin Shelton [this message]
2002-07-17 16:27   ` Paul Jarc

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=m2d6tnjcb6.fsf@zion.rcn.com \
    --to=acs@alumni.princeton.edu \
    /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).