From: Dan Christensen <jdc+news@uwo.ca>
Subject: not showing expirable articles
Date: 02 Apr 2001 17:47:07 -0400 [thread overview]
Message-ID: <87puevotyc.fsf@uwo.ca> (raw)
This was discussed a long time ago, but I don't know if a good
solution was ever proposed. I use auto-expire, or manually mark
articles as expirable. When I've done this, I would like it if
by default such articles didn't show up in the summary buffer
(unless I enter with `C-u RET' or something like that). And
that the expirable articles could be brought in with a keystroke
like `/ E'.
I accomplish this with the following code:
; This runs only when the summary is first prepared, and not after
; other limiting commands. Thus `/ w' pop's this limit, and others,
; as one would like it to.
(add-hook 'gnus-summary-prepared-hook
(lambda ()
(if (or (string-match "^nnfolder:" gnus-newsgroup-name)
(string-match "^nnvirtual:Both" gnus-newsgroup-name)
(string-match "^nnml:" gnus-newsgroup-name))
(jdc-gnus-summary-limit-exclude-unwanted))))
(defun jdc-gnus-summary-limit-exclude-unwanted ()
(interactive)
(gnus-summary-limit-to-marks "EG" t))
I also add the following to my summary-mode-hook:
(define-key gnus-summary-mode-map "/e" 'jdc-gnus-summary-limit-exclude-unwanted)
Then `/ w' shows me the expired articles when I choose to see them,
and `/ e' gets rid of them.
The only problem with this set-up is that entering a group is quite
slow, since the summary buffer gets generated twice, and the first
time tends to be a fair bit larger than the second time. So it is
usually more than a factor of two slower than necessary.
What I would like is a variable "gnus-summary-show-expirable". If
this is nil, then expirable articles aren't included by default,
but can be brought in with a new command. I would suspect that
many users would like this behaviour.
Any thoughts?
--
Dan Christensen
jdc+news@uwo.ca
reply other threads:[~2001-04-02 21:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87puevotyc.fsf@uwo.ca \
--to=jdc+news@uwo.ca \
/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).