Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: Sivaram Neelakantan <nsivaram.net@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, info-gnus-english@gnu.org
Subject: Re: saving gwene RSS posts
Date: Thu, 17 Apr 2014 12:56:14 +0200	[thread overview]
Message-ID: <851twwte27.fsf@iznogoud.viz> (raw)
In-Reply-To: <877g6qcwk5.fsf@gmail.com>

On Tue, Apr 15 2014, Sivaram Neelakantan wrote:

> On Thu, Mar 06 2014,Lars Ingebrigtsen wrote:
>
>> Sivaram Neelakantan <nsivaram.net@gmail.com> writes:
>>
>>> I've had a look at article caching and I can't figure how that would
>>> apply to my use case.  Some RSS articles I want to save for long term
>>> reference.  Is it enough to simply copy them to some other folder,
>>> preferably in the same format that I see in the gwene ng?  
>>
>> The `*' command will cache the message locally.
>
> Looks like I misunderstood what the * option does for caching. I've
> been marking some articles with * and I see that it has all expired
> now and no longer in the group.

They should be still there, try `Y c' in the summary buffer, see

(info "(gnus) Summary Generation Commands")

> How I keep certain articles in the group without it ever expiring
> unless I mark it for deletion or delete it.

Change the value of gnus-use-cache from `passive' to some other non-nil
value.  You can then mark those articles as `ticked' or `dormant' and
that will automatically mark them as persistent as well.

See (info "(gnus) Article Caching") and (info "(gnus) Unread Articles").

Alternatively (well, even at the same time...) you could agentize the
server in question and then you don't need any of the stuff described
above since, by default, the agent doesn't expire ticked articles in its
own cache (which is different from the cache described above).

Wolfgang


  reply	other threads:[~2014-04-17 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.15223.1392529451.10748.info-gnus-english@gnu.org>
2014-02-18  0:06 ` N. Jackson
2014-03-05 13:10 ` Lars Ingebrigtsen
2014-03-06 17:04   ` Sivaram Neelakantan
2014-03-06 17:08     ` Lars Ingebrigtsen
2014-04-15 17:49       ` Sivaram Neelakantan
2014-04-17 10:56         ` Wolfgang Jenkner [this message]
2014-04-23  3:30           ` Sivaram Neelakantan
2014-04-18 16:55         ` Sharon Kimble
2014-02-16  5:43 Sivaram Neelakantan

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=851twwte27.fsf@iznogoud.viz \
    --to=wjenkner@inode.at \
    --cc=info-gnus-english@gnu.org \
    --cc=larsi@gnus.org \
    --cc=nsivaram.net@gmail.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).