From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
To: info-gnus-english@gnu.org
Subject: Re: retaining marked articles in summary buffer?
Date: Mon, 27 Feb 2017 09:40:57 +0100 [thread overview]
Message-ID: <87shn0qb52.fsf@fsfe.org> (raw)
In-Reply-To: <87poi48i1p.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
Sivaram Neelakantan <nsivaram.net@gmail.com> čálii:
> 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
No, see Info gnus:
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’).
(That probably shouldn've been mentioned in the docstring for
gnus-use-cache, which is rather misleading: "use the cache to the full
extent of the law" sounds like "cache everything").
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2017-02-27 8:40 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
[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 [this message]
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=87shn0qb52.fsf@fsfe.org \
--to=unhammer@fsfe.org \
--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).