Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Kevin Greiner <kevin.greiner@compsol.cc>
Cc: <ding@gnus.org>
Subject: Re: Agent and gnus-group-clear-data
Date: Sat, 24 Mar 2007 21:51:39 +0100	[thread overview]
Message-ID: <v9wt1674bo.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9oe3wem7b.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun\, 04 Dec 2005 19\:44\:40 +0100")

[ I came across this old thread ...]

On Sun, Dec 04 2005, Reiner Steib wrote:

> On Sun, Dec 04 2005, Kevin Greiner wrote:

[shouldn't `gnus-group-clear-data' also clear the agent data?]
>> No.  I can see where people might want to clear marks (i.e. gnus-
>> group-clear-data) without purging the content that they have 
>> downloaded.  
>
> Okay, I see.
>
>> In this particular case, the old article numbers have been
>> invalidated so Rahed needed to do both.
>>
>> There's a section in the manual on 'Changing Servers' that 
>> mentions gnus-group-clear-data.  It needs to be updated to also 
>> reference gnus-agent-flush-cache (to purge the old articles).  
>
> Maybe `gnus-agent-flush-cache' should be interactive then?  Could you
> add a doc string, too?
>
>> Do you think we should add another section named 'Renumbering
>> Articles' to discuss the sort of problem that Rahed encountered?
>
> I'd suggest to add it to (info "(gnus)Changing Servers") first.  If it
> becomes too long, we can still split it.

Could someone work on this, please?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2007-03-24 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04 15:28 Kevin Greiner
2005-12-04 18:44 ` Reiner Steib
2007-03-24 20:51   ` Reiner Steib [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-29 12:48 Reiner Steib

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=v9wt1674bo.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=kevin.greiner@compsol.cc \
    /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).