Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: William Gardella <gardellawg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: info-gnus-english-mXXj517/zsQ@public.gmane.org
Subject: Re: A Gnus Biff
Date: Fri, 28 Sep 2012 19:06:36 -0400	[thread overview]
Message-ID: <87wqzdzr0j.fsf@gmail.com> (raw)
In-Reply-To: <871uhl24iu.fsf@gmail.com>

William Gardella <gardellawg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
writes:

> ...
>
> Is there a function or variable I could use as a condition to determine
> whether Gnus is actually "running?"  Eval-after-load is probably not
> quite right, because Gnus is not exactly a normal Elisp package, and
> it's not that I need some function to be available--it's that the group
> data hasn't been populated yet until Gnus is running.  I also considered
> using the variable `gnus-demon-timers' as a condition, since the daemon
> timers are started when gnus starts/restarts and removed when it exits,
> and someone who wants a biff probably does use gnus-demon for periodic
> message checking.  Is that a kludge?  Is there a better way to check the
> status of Gnus?
>
> Thanks in advance for your thoughts,
> WGG

Hmm.  Perhaps `gnus-startup-hook' or `gnus-started-hook' is a
possibility.  I'm not entirely clear as to the difference between them.
I notice also that there's a `gnus-after-getting-new-news-hook' which
might offer another way of running my function, rather than wastefully
running it whenever display-time updates itself...pleasantly, Gnus has
more of an API than it appeared when I started :)  

  reply	other threads:[~2012-09-28 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 21:58 William Gardella
2012-09-28 23:06 ` William Gardella [this message]
2012-09-29  7:30   ` Adam Sjøgren
     [not found] <mailman.9955.1348869546.855.info-gnus-english@gnu.org>
2012-09-29  4:13 ` Ben Kibbey
2012-12-24 16:33 ` Lars Ingebrigtsen

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=87wqzdzr0j.fsf@gmail.com \
    --to=gardellawg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=info-gnus-english-mXXj517/zsQ@public.gmane.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).