Gnus development mailing list
 help / color / mirror / Atom feed
From: Paul Stevenson <spaul@mail.phy.ornl.gov>
Subject: Re: Ugh!  Ack!  Argh!  Nggh!
Date: 26 Jul 1999 13:45:23 -0400	[thread overview]
Message-ID: <m3r9lv1f0s.frustrates@q2ypc.phy.ornl.gov> (raw)
In-Reply-To: Hrvoje Niksic's message of "26 Jul 1999 19:14:29 +0200"

Hrvoje Niksic <hniksic@srce.hr> writes:

> Jack Vinson <vinson@unagi.cis.upenn.edu> writes:
> 
> > But his original point was that when Gnus asked him about creating a
> > group, it should _create the group_.  I just 'B c' on Kai's article
> > and answered with a new group name.  The following messages popped
> > into the minibuffer:
> > 
> > Creating mail directory w:/jmvins/private/Mail/jack_is_great/
> > Wrote w:/jmvins/private/Mail/jack_is_great/1
> > 
> > One would expect that group to be created, no?  If I look at my
> > *Group* buffer, it does not exist.
> 
> Try pressing `F' -- the group should spring into existence.

I just tried this (actually I `B m'ed some articles from one nnml group
to another which didn't yet exist). Gnus asked me if I wanted to create
the group so I said yes, and I saw the messages like Jack
indicated. 

Now I press `F' but it does not let me see the group. `j' followed by
the new group's name does, and shows that it was killed, so I subscribe
to it.

Now the new group /looks/ like any other, but I can't enter it (can't
select group). It's an nnml group, so I do nnml-generate-nov-databases
and that thinks for a while. Now the directory ~/Mail/mynewgroup has the
messages and an .overview file but still I can't select the group. 

What magic is needed ? (I know that if I restart gnus something occurs
which lets me read the group)  As Jack suggests, shouldn't creating a
new group default to subscribing to it, too?

Paul


  reply	other threads:[~1999-07-26 17:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-15 17:59 Gnus and NoCeM Ken McGlothlen
1999-07-15 19:05 ` Colin Rafferty
1999-07-15 19:32   ` Ken McGlothlen
1999-07-15 20:27     ` Colin Rafferty
1999-07-15 21:51       ` Ken McGlothlen
1999-07-15 22:58         ` David Hedbor
1999-07-16  0:15       ` Dan Christensen
1999-07-17  3:54         ` Justin Sheehy
1999-07-17  7:02           ` Ugh! Ack! Argh! Nggh! Ken McGlothlen
     [not found]             ` <wtnu2r3bslp.fsf@licia.dtek.chalmers.se>
1999-07-17 10:15               ` Hans de Graaff
1999-07-17 16:05                 ` Michael Cook
1999-07-17 10:17               ` Kjetil Ødegaard
1999-07-17 11:02               ` Kai Großjohann
1999-07-17 12:21                 ` Harry Putnam
1999-07-17 11:14             ` Kai Großjohann
1999-07-18  7:10               ` Ken McGlothlen
1999-07-19 10:50                 ` Kai Großjohann
1999-07-27 15:37                   ` Jack Vinson
1999-07-26 17:14                     ` Hrvoje Niksic
1999-07-26 17:45                       ` Paul Stevenson [this message]
1999-07-26 17:50                         ` Paul Stevenson
1999-07-26 19:13                         ` François Pinard
1999-07-28 12:15                         ` Robert Bihlmeyer
1999-07-28 14:38                           ` Paul Stevenson
1999-07-17 10:58           ` Gnus and NoCeM Kai Großjohann
1999-07-19 17:53       ` Sudish Joseph
1999-07-15 20:49     ` Justin Sheehy
1999-07-16  4:50     ` Andrew Hobson
1999-07-16  5:37       ` Ken McGlothlen
1999-07-16 14:02         ` Jack Twilley
1999-07-15 21:32 ` Kai Großjohann
1999-07-16 15:28 ` Wes Hardaker

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=m3r9lv1f0s.frustrates@q2ypc.phy.ornl.gov \
    --to=spaul@mail.phy.ornl.gov \
    /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).