Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: Spurious "no such group" question following `B c'
Date: 05 Jun 2000 17:14:59 +0200	[thread overview]
Message-ID: <dpaeh0rwgc.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Shenghuo ZHU's message of "05 Jun 2000 11:09:08 -0400"

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> > ("nnml+save:news-stuff" 5
> >  ((1 . 447))
> >  ((save 101 107 110 164 275 399)
> >   (reply 37 63 65 90 101 130 147 161 165 180 210 221 328 342 368 384 399 418 425))
> >  "save")
> > 
> > What should I change it to?
> 
> Put on your asbestos longjohns and change "save" to (nnml "save").

Didn't help.  The message persisted, and -- even worse -- the group
was inaccessible.  I changed (nnml "save") back to "save", restarted
Gnus, and the group is accessible again.  The old problem persists.



  reply	other threads:[~2000-06-05 15:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-03 15:35 Hrvoje Niksic
2000-06-03 15:57 ` Simon Josefsson
2000-06-05  7:56   ` Didier Verna
2000-06-05 21:03     ` Simon Josefsson
2000-06-06 13:03     ` guessing To's Simon Josefsson
2000-06-06 16:23       ` Didier Verna
2000-06-05  8:20   ` Spurious "no such group" question following `B c' Hrvoje Niksic
2000-06-05 11:13     ` Kai Großjohann
2000-06-05 12:13       ` Hrvoje Niksic
2000-06-05 22:51         ` François Pinard
2000-06-05 14:38     ` Shenghuo ZHU
2000-06-05 14:41       ` Hrvoje Niksic
2000-06-05 15:09         ` Shenghuo ZHU
2000-06-05 15:14           ` Hrvoje Niksic [this message]
2000-06-05 15:25             ` Shenghuo ZHU
2000-06-05 15:29               ` Hrvoje Niksic
2000-06-05 15:40                 ` Shenghuo ZHU
2000-06-05 22:24             ` 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=dpaeh0rwgc.fsf@mraz.iskon.hr \
    --to=hniksic@iskon.hr \
    /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).