From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Notification tools
Date: Thu, 14 May 2009 15:04:44 +0200 [thread overview]
Message-ID: <1242305907-sup-1542@ausone.inria.fr> (raw)
In-Reply-To: <391beaa80905131723k4b59090bi5bd541d97d1a75f2@mail.gmail.com>
Excerpts from Henri Ducrocq's message of Thu May 14 02:23:00 +0200 2009:
> On Wed, May 13, 2009 at 7:54 PM, William Morgan <wmorgan-sup at masanjin.net>wrote:
>
> > Periodically dumping all new messages into a dummy mbox file is a
> > terrible idea, but I think that's your only Sup-specific option.
> > Patching mail-notification is a better idea, though that may not be what
> > you want to hear.
>
>
> It isn't :)
>
> > If you're using a recent Gnome, you have some other options. If you're
> > running notification-daemon (e.g. Ubuntu 9.04), you can install the
> > libnotify-bin package and having the after-poll hook call notify-bin on
> > new email. (Not quite the same.) You can also look at the
> > indicator-applet: libindicate also has Python bindings, so you could
> > install python-indicate and write a python short program to use that.
>
>
> I don't use Gnome or KDE (or anything really.)
> Re. the notification-daemon tip, that's what I'm doing already (via a python
> script of mine, I didn't know about notify-bin!), but sure it isn't the
> same.
> What I might do: Have after-poll dump the number of unread messages into a
> file,
> and display that value in my dzen status bar. It might be good enough.
I'm doing something quite similar:
I have a status-bar-text hook.
$ cat ~/.sup/hooks/status-bar-text.rb
dir = ENV['HOME']+'/.sup/'
state_new = dir+'state.new'
File.open(state_new, 'w') do |f|
f.puts "SupState { sup_num_inbox_unread = #{num_inbox_unread} }"
end
File.rename(state_new, dir+'state') rescue nil
nil
Then I have tweaked my xmonad config to inject the contents of this
file in my dzen bar.
Best regards,
--
Nicolas Pouillard
next prev parent reply other threads:[~2009-05-14 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 11:37 Henri Ducrocq
2009-05-13 18:54 ` William Morgan
[not found] ` <391beaa80905131723k4b59090bi5bd541d97d1a75f2@mail.gmail.com>
[not found] ` <1242261120-sup-2999@cabinet>
2009-05-14 1:52 ` William Morgan
[not found] ` <1242273707-sup-1213@cabinet>
2009-05-14 8:37 ` Marcus Williams
[not found] ` <1242331711-sup-4976@cabinet>
2009-05-15 12:41 ` David Guibert
2009-05-17 19:23 ` Henri Ducrocq
2009-05-18 18:44 ` William Morgan
2009-05-18 20:03 ` Henri Ducrocq
2009-05-18 18:31 ` William Morgan
2009-05-14 13:04 ` Nicolas Pouillard [this message]
2009-05-15 21:22 Henri Ducrocq
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=1242305907-sup-1542@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
/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