From: Neil Jerram <neil@ossau.homelinux.net>
To: guile-user@gnu.org
Subject: Re: Using libnotify from Guile
Date: Tue, 5 Jan 2016 10:07:15 +0000 [thread overview]
Message-ID: <568B95D3.1@ossau.homelinux.net> (raw)
In-Reply-To: <87k2no74ad.fsf@gnu.org>
On 05/01/16 09:40, Ludovic Courtès wrote:
> Neil Jerram <Neil.Jerram@metaswitch.com> skribis:
>
>> I noticed you asked about libnotify on IRC
>
> Also note that glibc built for the Linux kernel provides wrappers for a
> bunch of inotify syscalls in <sys/inotify.h>:
>
> --8<---------------cut here---------------start------------->8---
> $ objdump -T .guix-profile/lib/libc.so.6 | grep inotify
> 00000000000e9cc0 g DF .text 0000000000000021 GLIBC_2.9 inotify_init1
> 00000000000e9cf0 g DF .text 0000000000000021 GLIBC_2.4 inotify_rm_watch
> 00000000000e9c90 g DF .text 0000000000000021 GLIBC_2.4 inotify_init
> 00000000000e9c60 g DF .text 0000000000000021 GLIBC_2.4 inotify_add_watch
> --8<---------------cut here---------------end--------------->8---
>
> So you could avoid libnotify altogether with things like:
>
> (dynamic-func "inotify_init" (dynamic-link))
>
> Ludo’.
>
>
But isn't inotify (a Linux kernel subsystem for noticing changes to the
filesystem) unrelated to libnotify (a thing for popping up a
notification message on the desktop)?
next prev parent reply other threads:[~2016-01-05 10:07 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
2016-01-05 9:40 ` Ludovic Courtès
2016-01-05 10:07 ` Neil Jerram [this message]
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=568B95D3.1@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--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).