Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Phantom message 14
Date: Sun, 27 Jun 2010 13:54:19 +0800	[thread overview]
Message-ID: <87pqzdt3zo.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pqzfv929.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I'm trying to compact my Sent messages group, (nnml mail numbers
> currently run from 7112 to 10300) and every time I do gnus tells me
> that it can't delete message 14. There is no message 14. It starts the
> compacting process, writes a blank message to 1, then says there's no
> message 14.
>
> So far as I know, the active file in this backend and the .newsrc.eld
> file are the only two places where gnus could be getting information
> about existing messages. I've killed emacs, made sure the relevant line
> in the active file reads:
>
> Sent 10300 7112 y
>
> and that .newsrc.eld doesn't have a 14 in it, then restarted emacs and
> gnus. Again, the complaint about message 14. After I've done this, gnus
> rewrites the active file to read:
>
> Sent 10300 14 y
>
> I just don't know why. Where else could this 14 be coming from?
> References from other messages? Hidden configuration files? Can anyone
> give me a logical place to start looking, before I turn to voodoo?
>
> Thank you,
> Eric

Still don't know where the 14 was coming from, but after looking in the
source code for a bit I went into the Sent group, popped (14 . "14") off
the nnml-file-article-alist variable, returned to the *Group* buffer, and
successfully compacted the group without, so far as I can tell, any lost
or mis-filed messages.




      reply	other threads:[~2010-06-27  5:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25  7:57 Eric Abrahamsen
2010-06-27  5:54 ` Eric Abrahamsen [this message]

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=87pqzdt3zo.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).