From: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
To: Neil Jerram <Neil.Jerram@metaswitch.com>
Cc: guile-user@gnu.org
Subject: Re: Using libnotify from Guile
Date: Mon, 04 Jan 2016 19:35:19 -0500 [thread overview]
Message-ID: <1cc86ddb1d867536c0e35871638434f9@openmailbox.org> (raw)
In-Reply-To: <SN1PR02MB169504B6A5D361F6B6BC921E99F20@SN1PR02MB1695.namprd02.prod.outlook.com>
On 2016-01-04 13:26, Neil Jerram wrote:
> Hi Luis,
>
> I noticed you asked about libnotify on IRC; unfortunately I wasn't
> quick
> enough before you left the channel, but I had a quick play and found
> that it was quite easy to generate a notification using the FFI:
Oh, great Neil! Thank you very much. It works for me :)
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/
next prev parent reply other threads:[~2016-01-05 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 18:26 Using libnotify from Guile Neil Jerram
2016-01-05 0:35 ` Luis Felipe López Acevedo [this message]
2016-01-05 9:40 ` Ludovic Courtès
2016-01-05 10:07 ` Neil Jerram
2016-01-05 20:22 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1cc86ddb1d867536c0e35871638434f9@openmailbox.org \
--to=felipe.lopez@openmailbox.org \
--cc=Neil.Jerram@metaswitch.com \
--cc=guile-user@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).