Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@work.lexort.com>
To: Nicolas KOWALSKI <niko@petole.dyndns.org>
Cc: ding@gnus.org
Subject: Re: move article, agent does not expire ?
Date: Tue, 02 Oct 2007 07:55:12 -0400	[thread overview]
Message-ID: <smuk5q5enof.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <878x6mgdug.fsf@petole.dyndns.org> (Nicolas KOWALSKI's message of "Tue, 02 Oct 2007 09:44:39 +0200")

  But when I move an article from a group to another, this expiry does not
  happen, and so old data is kept into the agent. If I later come back
  into that "source" group, I see the old article (marked with G), and I
  can not remove it anymore. So, I currently have to copy the article in
  the destination group, then delete it, to keep the agent up to date.
  Even using "gnus-agent-regenerate" does not always clean up the
  situation.

I am having a problem that I think is the same one.  I use imap for
mail.  I have a function to make imap sharing with tbird etc. easier:

  d runs the command gdt-gnus-move-to-trash
    which is an interactive Lisp function in `/usr/home/gdt/.dot-gdt/.emacs'.
  It is bound to d.
  (gdt-gnus-move-to-trash)

(defun gdt-gnus-move-to-trash ()
  (interactive)
  (gnus-summary-move-article nil gdt-trash-newsgroup))


and have been noticing G articles in the summary on reentry.  I fix this
by "rm -rf News/agent".  This behavior started about 2 months ago (by
very fuzzy memory).



  reply	other threads:[~2007-10-02 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02  7:44 Nicolas KOWALSKI
2007-10-02 11:55 ` Greg Troxel [this message]
2007-10-02 13:58   ` Nicolas KOWALSKI
2007-10-02 22:45 ` Malcolm Purvis
2007-10-03 18:48   ` Elias Oltmanns
2007-10-03 18:54     ` Greg Troxel
2007-10-06  8:17     ` Malcolm Purvis

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=smuk5q5enof.fsf@linuxpal.mit.edu \
    --to=gdt@work.lexort.com \
    --cc=ding@gnus.org \
    --cc=niko@petole.dyndns.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).