Gnus development mailing list
 help / color / mirror / Atom feed
From: tbennett@nvidia.com (Tony E. Bennett)
Subject: Re: relationship of cached msg to the original msg
Date: Sat, 23 Nov 2002 23:37:05 -0500	[thread overview]
Message-ID: <m33cpr7fda.fsf@uh-oh.nvidia.com> (raw)
In-Reply-To: <843cpvcg9o.fsf@lucy.cs.uni-dortmund.de>


kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> tbennett@nvidia.com (Tony E. Bennett) writes:
>
>> I've been using (gnus-cache-enter-article) to save nnimap
>> messages that I want to keep for a long time[1].
>>
>> But I just realized that if I delete the original msg using
>> another imap reader, then the cached article seems to disappear
>> also.
>
> Really?  This is not supposed to happen.  Hm.
>
> But I don't use gnus-cache-enter-article explicitly, I (setq
> gnus-use-cache t) instead and then tick interesting messages.  Could
> you check if that works?
>
> I've used the above procedure for a long time now to keep old
> messages in nntp groups.  

It now looks like the msg is not deleted when put into the cache,
just that 'tick' is cleared and msg becomes 'O' which makes it
not show up in my default summary.  Tick'ing it again after this
looks fine until I exit group and re-enter.  Cached article is
still not ticked.

I have gnus-use-cache set to 'passive.  Setting it to t does not
change this behavior.

Should cache'd articles preserve tick state of the original?
Or is tick state saved w/ original article only and lost when
original article is deleted?

Basically, I just want the summary to default to unread, ticked
and cached articles.  Maybe there is a better way to do this...

--tony



  reply	other threads:[~2002-11-24  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 20:01 Tony E. Bennett
2002-11-21 11:29 ` Kai Großjohann
2002-11-24  4:37   ` Tony E. Bennett [this message]
2002-11-24 11:58     ` Kai Großjohann

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=m33cpr7fda.fsf@uh-oh.nvidia.com \
    --to=tbennett@nvidia.com \
    /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).