all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ernobe <ernobe@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [Gnus] persistent marks
Date: Mon, 11 Nov 2013 13:04:10 -0600	[thread overview]
Message-ID: <87zjpa4v6d.fsf@002215fd0050.amnet.co.cr> (raw)
In-Reply-To: 87li0xnvl5.fsf@nl106-137-194.student.uu.se

Emanuel Berg <embe8573@student.uu.se> writes:

> ernobe <ernobe@yahoo.com> writes:
>
>>> So you want Gnus *not* to delete 'R' articles? And
>>> "delete" in this case is that equivalent to "not show
>>> up in the summary next time I bring up the group"?
>>
>> Exactly.
>
> OK, I suspect this is actually possible to do by just
> telling Gnus about it. How, and where, you'll have to
> digest that manual, or wait for the Gnus foxes to get
> out of their lairs.
>
> But, three points to investigate:
>
> - those posts that you would like to keep, you could
>   mark collectively as something other than 'R' (this
>   could be automatized, for example when you close a
>   summary)
>   
> - when bringing up the group, could you configure it to
>   show 'R' posts as well? (This is the least hackish
>   approach. Examine `gnus-group-select-group' with
>   C-h f, *or* C-h k RET in the groups buffer.)

It turns out this is possible by setting 'gnus parameters':

(setq gnus-parameters
  '((".*"
    (display . all))))

The 'all' in this case means that read ones are included (exactly what I
wanted).  I found out about this from the 'Limiting' section of the
'Summary Buffer' section of the info, which links to the 'Group
Parameter' section of the 'Group Buffer' section.

With this setting entering the group is kind of slow.  Is there
something else I can turn off to speed it up?  Maybe I could mark most
of them dormant and send them to a cache, but then it will probably get
out of sync with slrnpull's cache which is where the articles are
actually received from the net.  If they are expired in the spool, will
they expire in the gnus cache?  I'll give it a try and report back here
if everything goes well.


>
> - when writing to ~/.newsrc, could you inhibit it from
>   noting those Rs?


-- 
"The world of existence is an emanation of the merciful attribute of God."
Abdu'l-Baha
http://www.costarricense.cr/pagina/ernobe


  reply	other threads:[~2013-11-11 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 14:11 [Gnus] persistent marks ernobe
2013-11-08 19:37 ` Emanuel Berg
2013-11-08 21:00   ` ernobe
2013-11-08 21:37     ` Emanuel Berg
2013-11-09 15:58       ` ernobe
2013-11-09 20:55         ` Emanuel Berg
2013-11-11 19:04           ` ernobe [this message]
2013-11-11 22:39             ` Emanuel Berg
2013-11-09  2:33     ` Eric Abrahamsen
     [not found]     ` <mailman.5618.1383964331.10748.help-gnu-emacs@gnu.org>
2013-11-09 16:34       ` ernobe
2013-11-09 17:37         ` Joost Kremers
2013-11-09 19:36         ` Emanuel Berg
2013-11-09 21:33           ` Eli Zaretskii
2013-11-09 21:32         ` Eli Zaretskii

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=87zjpa4v6d.fsf@002215fd0050.amnet.co.cr \
    --to=ernobe@yahoo.com \
    --cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.