Gnus development mailing list
 help / color / mirror / Atom feed
From: Shane Holder <holder@rsn.hp.com>
Cc: ding@gnus.org
Subject: Re: Ghost e-mail groups
Date: 01 Mar 1999 13:15:35 -0600	[thread overview]
Message-ID: <u90dht414.fsf@rsn.hp.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "01 Mar 1999 18:04:44 +0100"

>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

  Kai> From the Group buffer, type ^ to go to the Server buffer.  There,
  Kai> create a new server.  Then type C to close the server.  Then, type e
  Kai> to edit it.  You can put several parameters there, here's the archive
  Kai> server as an example:

  Kai> ,-----
  Kai> | (nnfolder "archive"
  Kai> |           (nnfolder-directory "~/Mail/archive")
  Kai> |           (nnfolder-active-file "~/Mail/archive/active")
  Kai> |           (nnfolder-get-new-mail nil)
  Kai> |           (nnfolder-inhibit-expiry t))
  Kai> `-----

  Kai> Just change these as appropriate.  Then hit C-c C-c.  You can then
  Kai> move and copy articles to that server.


So is this new to pgnus, I know I didn't have to do that under 5.6.45,
or is it because it's still pre-release?  It seems like a real
difficult way to get a group that doesn't really do anything.  A user
that is new to Gnus isn't going to figure this out, and while I took a
hiatus from Gnus I used gnus for several years and don't recall having
to do anything this intensive to get a new group.  I'm really not
trying to be difficult on this, but it does seem more difficult than
it should.

Shane



  reply	other threads:[~1999-03-01 19:15 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
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 [this message]
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=u90dht414.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).