From: Shane Holder <holder@rsn.hp.com>
Cc: ding@gnus.org
Subject: Re: Ghost e-mail groups
Date: 26 Feb 1999 14:46:48 -0600 [thread overview]
Message-ID: <uhfs87v0n.fsf@rsn.hp.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "26 Feb 1999 18:29:53 +0100"
>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> Shane Holder <holder@rsn.hp.com> writes:
>> I'm not sure what you're asking here, are you asking about the
>> prompting after G-m? If so, I created the nnml.test group with a
>> backend of nnml and the nnfolder.test group with a backend of
>> nnfolder.
Kai> I think when your secondary-select-method says (nnfolder
Kai> "private"), then you should enter "private" at the G m prompt,
Kai> or maybe "nnfolder+private".
Hmm, not sure I understand why it should be nnfolder+private or
private.
If I to G m in the Group buffer it prompts me for name and then select
method.
Group name: foo
Select Method: nnml
creates a group "*: nnml:foo". If I then exit Gnus and restart gnus I
get another group, "*: nnfolder+private: foo", in addition to my
original group "nnml:foo", with no addition to my ~/Mail/active file
other than foo. This wasn't the behavior in Gnus 5.6.45. With the
same secondary select method in both versions.
If you're saying that based on my select method I should type in a
name other than what I want the name of the group to be, I'd have to
disagree. A name should just be a label and if Gnus needs something
in addition to what I want to call it, it should add it itself when
the group is newly created not after starting a second time.
Now, I'm certain that other people are creating groups so it's highly
possible that I just don't understand what I'm doing, but having just
come from 5.6.45 there's a feature that others are already used to
that new users of pgnus won't understand.
Shane
next prev parent reply other threads:[~1999-02-26 20:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-25 16:27 Shane Holder
1999-02-26 14:40 ` Lars Magne Ingebrigtsen
1999-02-26 16:45 ` Shane Holder
1999-02-26 17:26 ` Lars Magne Ingebrigtsen
1999-02-26 17:29 ` Kai.Grossjohann
1999-02-26 20:46 ` Shane Holder [this message]
1999-02-26 22:44 ` Lars Magne Ingebrigtsen
1999-02-26 23:28 ` Shane Holder
1999-02-27 0:53 ` Lars Magne Ingebrigtsen
1999-03-01 16:41 ` Shane Holder
1999-03-01 17:04 ` Kai.Grossjohann
1999-03-01 19:15 ` Shane Holder
1999-03-01 19:35 ` Simon Josefsson
[not found] ` <86ogmdq9tq.fsf@slowfox.frob.org>
[not found] ` <uzp5wsusp.fsf@rsn.hp.com>
1999-03-01 23:09 ` Kai.Grossjohann
1999-03-02 15:07 ` Lars Magne Ingebrigtsen
1999-03-02 16:09 ` Shane Holder
1999-03-02 16:19 ` Kai.Grossjohann
1999-03-02 16:52 ` Shane Holder
1999-03-02 16:52 ` Kai.Grossjohann
1999-03-02 17:06 ` Lars Magne Ingebrigtsen
1999-03-03 16:42 ` Shane Holder
1999-03-05 19:44 ` Lars Magne Ingebrigtsen
1999-03-05 20:57 ` Shane Holder
1999-03-06 19:14 ` Lars Magne Ingebrigtsen
1999-03-08 16:23 ` Shane Holder
1999-03-14 16:02 ` Lars Magne Ingebrigtsen
1999-03-15 15:22 ` Shane Holder
1999-03-28 15:03 ` Lars Magne Ingebrigtsen
1999-02-26 23:10 ` Kai.Grossjohann
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=uhfs87v0n.fsf@rsn.hp.com \
--to=holder@rsn.hp.com \
--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).