From: jidanni@jidanni.org
To: ding@gnus.org
Subject: Re: Restricting frequency of 'g'
Date: Tue, 08 Apr 2008 07:45:30 +0800 [thread overview]
Message-ID: <87fxtxqlet.fsf@jidanni.org> (raw)
In-Reply-To: <877ifaxxhz.fsf@windlord.stanford.edu>
Your time-limited and cron-job-style assisted approaches are
artificial.
I share not your pain, as I use noffle, getmail, so whatever is to be
fetched is already on the local disk, just a folder away.
However, an accidental "g" press would still send the game into
halftime for me, if it weren't for my
(defun jidanni-gnus-group-get-new-rss-news()
"Sorry attempt to seperate out painful RSS fetching."
(let ((gnus-activate-foreign-newsgroups 5))
(gnus-group-get-new-news)))
(define-key gnus-group-mode-map "v"
(lambda ()
(interactive)
(jidanni-gnus-group-get-new-rss-news)))
and my having put each RSS on level 5 etc. etc. Barf.
Yes, one could make the batch script, OK, some other day.
next prev parent reply other threads:[~2008-04-07 23:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 3:36 Russ Allbery
2008-04-06 4:54 ` Bill O'Connor
2008-04-06 6:43 ` Russ Allbery
2008-04-06 11:55 ` John SJ Anderson
2008-04-07 1:30 ` Russ Allbery
2008-04-07 23:45 ` jidanni [this message]
2008-04-08 0:54 ` John SJ Anderson
2008-04-08 3:41 ` Russ Allbery
2008-04-08 21:12 ` a Gnus biff (was: Restricting frequency of 'g') Ted Zlatanov
2008-04-09 13:59 ` a Gnus biff Wes Hardaker
2008-04-08 3:55 ` Restricting frequency of 'g' Dan Nicolaescu
2008-04-09 6:49 ` Dan Nicolaescu
2008-04-09 19:22 ` Reiner Steib
2008-04-12 14:58 ` Mark Plaksin
2008-07-29 21:14 ` Dan Nicolaescu
2008-07-30 18:04 ` Reiner Steib
2009-07-30 19:32 ` Dan Nicolaescu
2010-10-07 6:27 ` Dan Nicolaescu
2010-10-07 20:16 ` Lars Magne Ingebrigtsen
2010-10-07 21:55 ` Russ Allbery
2010-10-08 17:28 ` Ted Zlatanov
2010-10-08 15:14 ` Jason L Tibbitts III
2010-10-09 15:36 ` Lars Magne Ingebrigtsen
2010-10-09 15:50 ` Richard Riley
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=87fxtxqlet.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.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).