From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: retaining marked articles in summary buffer?
Date: Mon, 27 Feb 2017 09:09:54 -0800 [thread overview]
Message-ID: <87shmzblwd.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871sukdpbp.fsf@enricoschumann.net>
Enrico Schumann <es@enricoschumann.net> writes:
> On Sun, 26 Feb 2017, Eric Abrahamsen writes:
>
>> Sivaram Neelakantan <nsivaram.net@gmail.com> writes:
>>
>>> On Sun, Feb 26 2017,Enrico Schumann wrote:
>>>
>>>> On Sun, 26 Feb 2017, Adam Sjøgren writes:
>>>
>>> [snipped 20 lines]
>>>
>>>> When 'gnus-use-cache' is t, ticking (!) will also copy the
>>>> article to the cache. See http://gnus.org/manual/gnus_42.html .
>>>>
>>>
>>> if it's set to t (gnus-use-cache), won't all articles be cached? I
>>> only want to do this for interesting articles
>>
>> Its default value, the symbol 'passive, should do what you want: only
>> cache articles when you tell it to, with * or !.
>
> Hm, I've just tested this, and with gnus-use-cache set
> to 'passive, Gnus does *not* cache articles that I tick
> with '!'. It may well be, as always, that I have
> something in my .gnus.el that prevents this :-) But it
> is also in line with the docs
> (http://gnus.org/manual/gnus_42.html):
>
> ,----
> | To turn caching on, set gnus-use-cache to t. By
> | default, all articles ticked or marked as dormant
> | will then be copied over to your local cache
> | (gnus-cache-directory).
> `----
>
> So only 'articles ticked or marked as dormant' are
> copied to the cache, not all articles.
Right, I just looked through the code and it won't enter either * or !
articles into the cache when `gnus-use-cache' is 'passive. I guess
you could set `gnus-use-cache' to t and see what happens. There are
plenty of other knobs to twiddle to reduce the scope of articles that
are cached.
Eric
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2017-02-27 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 7:19 Sivaram Neelakantan
2017-02-26 7:25 ` Eric Abrahamsen
2017-02-26 17:33 ` Sivaram Neelakantan
2017-02-26 17:57 ` Adam Sjøgren
2017-02-26 20:02 ` Enrico Schumann
2017-02-27 2:49 ` Sivaram Neelakantan
2017-02-27 6:09 ` Eric Abrahamsen
2017-02-27 8:12 ` Enrico Schumann
2017-02-27 17:09 ` Eric Abrahamsen [this message]
[not found] ` <ecece4d5dbc84494872f88e25ad5102f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-28 14:47 ` Eric S Fraga
2017-03-02 14:49 ` Ben Bacarisse
2017-03-02 17:31 ` Sivaram Neelakantan
[not found] ` <fe0a029526d340169f5a5bd53785055a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-02 15:13 ` Eric S Fraga
2017-02-27 8:40 ` Kevin Brubeck Unhammer
2017-02-27 16:32 ` Sivaram Neelakantan
2017-02-26 18:25 ` Eric Abrahamsen
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=87shmzblwd.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).