Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Stumbled into bug in Make group process
Date: 21 Apr 2000 06:09:00 -0700	[thread overview]
Message-ID: <m2itxbppn7.fsf@reader.ptw.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "21 Apr 2000 13:48:14 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > Then `B c' to copy messages to a new gnus-owned nnfolder group.
> > 
> > That is: Answer the gnus prompt as to group name with:
> > 
> > nnfolder:NEWGROUP
> > 
> > Then press "F".. Gnus displays an inaccessable  *"nnml"* group
> > (nnml:NEWGROUP).
> 
> I'm unable to reproduce this.  Gnus creates an nnfolder group when I
> do this...

It does here too... but diplays a fictitious nnml group of the same
name, instead of displaying the nnfolder group.  The nnfolder group is
in fact created, but will only display by 'G m' NEWGROUP <RET> nnfolder <RET>.

I have (setq gnus-secondary-select-methods '((nnml "")))

Will that cause  the above reported behavior?  Should that be a list
that includes "nnfolder".... what is the syntax?

What other setting may affect this?

I have two more nnml servers that are only declared in Server Buffer
not in .gnus.

So in .gnus  I have  nnml ""

in Server buffer:

nnml ""
nnml "mail2"
nnml "n2m"



  reply	other threads:[~2000-04-21 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-21  0:01 Harry Putnam
2000-04-21 11:48 ` Lars Magne Ingebrigtsen
2000-04-21 13:09   ` Harry Putnam [this message]
2000-04-21 13:26     ` Lars Magne Ingebrigtsen
2000-04-22 12:44       ` Harry Putnam
2000-04-21 21:16     ` Kai Großjohann
2000-04-22  5:13       ` Harry Putnam
2000-04-22 12:40       ` Harry Putnam
2000-04-22 15:13         ` Kai Großjohann
2000-04-22 18:19           ` Lars Magne Ingebrigtsen

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=m2itxbppn7.fsf@reader.ptw.com \
    --to=reader@newsguy.com \
    /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).