Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
Subject: Re: fun function: get new news, dammit.
Date: Mon, 12 May 2003 00:58:03 -0400	[thread overview]
Message-ID: <87vfwgep7o.fsf@cs.uga.edu> (raw)
In-Reply-To: <87bryah5rc.fsf@cs.uga.edu>

Ed L Cashin <ecashin@uga.edu> writes:

> Despite gnus' great features, I often wind up switching to the *Group*
> buffer, hitting "L", and then doing "M-g" about twenty times or so to
> see whether there's new news/mail.
>
> Finally I made a function that does just that.  

OK, I this function appeared to work, but here's something really
wierd: although the function does exactly what I do -- it calls the
same functions the keys are bound to, it sometimes doesn't show new
mail when the keys do!

That is, I can run elc-get-news-dammit and not see any new mail, then
manually hit M-g on an nnimap mailbox, and it shows new messages!
That, to me, seems very strange, since "ESC g" is bound to
gnus-topic-get-new-news-this-topic, the same function called in
elc-get-news-dammit. 

...
>
> (defun elc-get-news-dammit ()
>   "get the news, dammit!"
>   (interactive)
>   (let ((gbuf (get-buffer "*Group*")))
>     (if (not gbuf)
> 	(error "Cannot find *Group* buffer"))
>     (switch-to-buffer gbuf)
>     (gnus-group-list-all-groups)
>     (save-excursion
>       (beginning-of-buffer)
>       (labels
> 	  ((rec ()
> 	     (gnus-topic-get-new-news-this-topic)
> 	     (if (= (forward-line) 0)
> 		 (rec))))
> 	(rec)))))

-- 
  Singing Science  | Now anyone can tell you what a mammal is,
  "Mammal"         | Anyone who understands!
                   | They're warm blooded, have hair on their bodies,
                   | And suckle their young from mammary glands.   


           reply	other threads:[~2003-05-12  4:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87bryah5rc.fsf@cs.uga.edu>]

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=87vfwgep7o.fsf@cs.uga.edu \
    --to=ecashin@uga.edu \
    /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).