Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: moved messages don't go away neither
Date: Wed, 05 Apr 2006 18:28:46 +0200	[thread overview]
Message-ID: <871wwcdm0x.fsf@mat.ucm.es> (raw)
In-Reply-To: <867j64nkte.fsf@student.uni-magdeburg.de>

>>>>> "Wolfram" == Wolfram Fenske
>>>>> <Wolfram.Fenske@Student.Uni-Magdeburg.DE> writes:


   Wolfram> Uwe Brauer <oub@mat.ucm.es> writes:

   Wolfram> Did you recompile "nnimap.el" or move the old "nnimap.elc"
   Wolfram> out of the way?  IIRC, Emacs tries to use the compiled
   Wolfram> version of a file, even if it's older.

Of course  I did.

   Wolfram> Also, how exactly are you're articles still there?  I ask, because
   Wolfram> there are two problems:

   Wolfram>   1. Articles that appears in an nnimap group but aren't
   Wolfram>   really there. When you try to read such an article, Gnus
   Wolfram>   beeps at you and tells you the article is no longer
   Wolfram>   present (something like that).  IIRC, you can't delete
   Wolfram>   (B DEL) it, either.  This is what I referred to as
   Wolfram>   "ghost mail" in my previous post, and this is what I
   Wolfram>   believe the original poster was talking about.  I may be
   Wolfram>   wrong, though.
No this is not my case. I can read the article.

   Wolfram>   2. Moving articles in the nnimap backend didn't work
   Wolfram>   because the article in the source folder was not
   Wolfram>   expired.  But in contrast to problem no. 1, the article
   Wolfram>   in the source folder could still be read. My patch
   Wolfram>   should have fixed this bug.

But the article has been copied? If so then it is my case. I use the
gnus-summary-move-article function, say in a imap folder INBOX, then
the articles *gets* copied to the new imap folder, say IMPORTANT, and
the article is then *marked* as deleted. However when I reenter the
group INBOX, the article is still there.

Uwe 










  reply	other threads:[~2006-04-05 16:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 15:40 Deleted messages don't go away David Abrahams
2006-03-27 23:57 ` gdt
2006-03-28  3:33   ` Dave Goldberg
2006-03-28  9:21     ` Reiner Steib
2006-03-28 16:34     ` Steven E. Harris
2006-03-31  3:39       ` Dave Goldberg
2006-04-04 13:04     ` moved messages don't go away neither (was: Deleted messages don't go away) Uwe Brauer
2006-04-04 13:38       ` moved messages don't go away neither Simon Josefsson
2006-04-04 14:09         ` Uwe Brauer
2006-04-04 22:09       ` Dave Goldberg
2006-04-05  1:17         ` Wolfram Fenske
2006-04-05 11:29           ` Uwe Brauer
2006-04-05 14:44             ` Wolfram Fenske
2006-04-05 16:28               ` Uwe Brauer [this message]
2006-04-05 17:50                 ` Wolfram Fenske
2006-04-05 18:35                   ` Uwe Brauer
2006-04-05 18:41                   ` Uwe Brauer
2006-04-05 19:14                     ` Wolfram Fenske
2006-03-28 13:30   ` Deleted messages don't go away Wolfram Fenske
2006-03-29 16:03   ` [nnimap] " David Abrahams
2006-03-29 16:23     ` gdt
2006-03-29 16:55       ` David Abrahams

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=871wwcdm0x.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    /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).