From: Jon K Hellan <Jon.K.Hellan@item.ntnu.no>
Subject: Can't select group created by copying
Date: 07 Jul 1999 12:32:38 +0200 [thread overview]
Message-ID: <87r9mkvjg9.fsf@parus.itea.ntnu.no> (raw)
Here's a problem I found. I am not sure how to deal with it.
When I create a new group by copying a message into it, I can't
enter that group until gnus has been restarted.
This happens with the nnimap backend, but from my meagre understanding
of the code, it doesn't look like a backend issue.
I use B c - gnus-summary-copy-article, and enter the name of a group
that does not exist. When prompted, I confirm that I want to create
it.
gnus-read-move-group-name creates the group, and activates it. Of
course, it is empty, and this is what (gnus-active <group-name>) will
report from now on.
When I subscribe the group in the Group buffer, and try to select it, the
active info is never updated. So gnus believes that it is still empty,
and refuses to enter it. "Can't select group".
So - when should the active info have been updated?
Jon
next reply other threads:[~1999-07-07 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-07 10:32 Jon K Hellan [this message]
1999-07-07 13:51 ` Jon K Hellan
1999-07-07 19:15 ` Simon Josefsson
1999-07-07 20:44 ` Jon K Hellan
1999-07-08 11:45 ` Jon K Hellan
1999-07-08 11:52 ` Jon K Hellan
[not found] ` <wtnzp18a9wb.fsf@licia.dtek.chalmers.se>
1999-07-07 13:56 ` Jon K Hellan
1999-07-07 14:00 ` Kai.Grossjohann
[not found] ` <wtnr9mkph6s.fsf_-_@licia.dtek.chalmers.se>
1999-07-08 9:37 ` nnmh, delete next last article (Was: Re: Can't select group created by copying) Kai.Grossjohann
1999-07-08 19:26 ` Stainless Steel Rat
1999-07-09 7:54 ` Kai.Grossjohann
1999-07-09 18:56 ` Stainless Steel Rat
[not found] ` <wtng12ytcb0.fsf@licia.dtek.chalmers.se>
[not found] ` <wtnr9m6t6qk.fsf@licia.dtek.chalmers.se>
1999-08-27 19:57 ` Lars Magne Ingebrigtsen
1999-07-09 17:16 ` 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=87r9mkvjg9.fsf@parus.itea.ntnu.no \
--to=jon.k.hellan@item.ntnu.no \
/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).