From: Leonidas Tsampros <ltsampros@upnet.gr>
To: ding@gnus.org
Subject: Re: Moving emails around groups woes/problems
Date: Tue, 09 Nov 2010 16:36:15 +0200 [thread overview]
Message-ID: <87tyjqwom8.fsf@bifteki.lan> (raw)
In-Reply-To: <m3lj53eeqz.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Leonidas Tsampros <ltsampros@upnet.gr> writes:
>
>> Anyway, do you consider this behaviour as erroneous or not?
>
> It's not erroneous. Gnus simply doesn't keep track of whether an
> article exists or not.
I understand that message counts are not *that important* however it is
an annoyance to me. So, do you believe that having some kind of support
for this would make sense for specific backends like nnml? (which
support article moving)
One work around I have tried so far is Compacting the group, however,
currently I'm a little bit afraid of using it since
a) it can be slow on large groups
b) it can have bad effects especially if something goes wrong
c) it does not work on nnimap :)
next prev parent reply other threads:[~2010-11-09 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 9:36 Leonidas Tsampros
2010-11-08 20:34 ` Lars Magne Ingebrigtsen
2010-11-09 14:36 ` Leonidas Tsampros [this message]
2010-11-09 17:54 ` 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=87tyjqwom8.fsf@bifteki.lan \
--to=ltsampros@upnet.gr \
--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).