From: brian@lorf.org (Brian)
Subject: [sup-talk] new mail notification hook
Date: Wed, 30 May 2007 02:27:11 -0500 [thread overview]
Message-ID: <1180509997-sup-405@doses> (raw)
In-Reply-To: <1180508946-sup-2933@south>
Excerpts from William Morgan's message of Wed May 30 02:11:59 -0500 2007:
> I've been thinking about writing a (simple) general framework for
> hooking user-written Ruby code onto Sup events. You could then trivially
> use that to accomplish this by calling system(...). What do you think?
That'd be great.
next prev parent reply other threads:[~2007-05-30 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 3:31 Brian
2007-05-27 19:56 ` jeff covey
2007-05-28 2:32 ` Brian
2007-05-28 10:32 ` jeff covey
2007-05-28 10:51 ` Brian
2007-05-30 7:11 ` William Morgan
2007-05-30 7:27 ` Brian [this message]
2007-08-19 0:30 ` William Morgan
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=1180509997-sup-405@doses \
--to=brian@lorf.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