Gnus development mailing list
 help / color / mirror / Atom feed
From: Hannu Koivisto <azure@iki.fi>
Subject: Re: Removing gaps by moving articles from group x to group x doesn't work
Date: 30 Jan 2001 16:14:44 +0200	[thread overview]
Message-ID: <87hf2h3z57.fsf@lynx.ionific.com> (raw)
In-Reply-To: <s8elxlp6wr.fsf@lanber.cam.eu.citrix.com>

Toby Speight <streapadair@gmx.net> writes:

| Are you sure you've moved *all* the articles?  Including dormant,
| read, etc?  Enter the group with - RET (that's a minus, followed by
| return), then M P a (`gnus-uu-mark-all') and B m.

Yes, I did this.

| If that doesn't work, create a scratch group, move all the articles
| to it, then leave and re-enter the original group.  Re-entry will

I did this.  Now the _scratch group_ says it has 598 articles.
Also, the original group has no articles (I even checked the
directory), but now it says it has something like 8516 articles.
If I do 'G E', I see

("lists.cmucl.imp" 3
 ((1 . 9249)))

If I go and edit 1 . 9249 to 1 . 1, which I saw one empty group
had, and hit 'C-c C-c' and 'g', the group suddenly says in the
group buffer it has 8xxx articles.  If I do 'G E' again, I see 

("lists.cmucl.imp" 3
 ((1 . 9249)))

again, so my editing was "erased" somehow.  I'm not going to move
the articles from the scratch group back to the original group
until I figure what's going on here --- after all, shouldn't the
scratch group be ok too so that moving those articles to the
original group doesn't buy me anything in this sense?

-- 
Hannu



  reply	other threads:[~2001-01-30 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28 18:50 Hannu Koivisto
2001-01-30 12:21 ` Toby Speight
2001-01-30 14:14   ` Hannu Koivisto [this message]
2001-01-30 16:20     ` ShengHuo ZHU
2001-01-30 17:13       ` Hannu Koivisto
2001-01-30 18:10         ` Toby Speight
2001-01-31 11:16           ` Hannu Koivisto
2001-01-31 15:05             ` Harry Putnam
2001-01-30 20:59         ` Nevin Kapur
2001-02-07 17:47     ` Kai Großjohann

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=87hf2h3z57.fsf@lynx.ionific.com \
    --to=azure@iki.fi \
    /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).