unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-user@gnu.org
Subject: Re: request: libguile to wrap getsid(2)
Date: Sun, 27 Dec 2009 12:46:39 +0000	[thread overview]
Message-ID: <87pr601t5c.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ws09y3g3.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Sat, 26 Dec 2009 19:50:52 +0100")

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> I've just about finished porting ratpoison (a CVS snapshot prior to its
> author's abandoning it in favor of stumpwm) to Guile (1.4.x) scheme.
> This means no more Xlib (et al)!

Cool.  (I like ratpoison, and I wasn't aware it had been abandoned.  A
Guile-enabled ratpoison would be great.)

> However, the last bit of C glue (outside of ttn-do) it needs is getsid(2).
> Here is the Guile 1.4.x-flavored wrapping:
>
>   GH_DEFPROC
>   (rpx_getsid, "getsid", 1, 0, 0,
>    (SCM pid),
>    doc: /***********
>   Return the session id associated with @var{pid}.  */)
>   {
>     return gh_int2scm (getsid (gh_scm2int (pid)));
>   }
>
> I'm sure it would be no trouble to adapt this to other Guile versions.
> This function will go into Guile 1.4.1.119, so i'm hereby requesting
> that a future Guile 1.9.x include it, as well.  This way, i can release
> rpx (working name of the port -- kind of like "ratpoison exhumed") with
> only ttn-do as its dependency, and no C bits whatsoever.

No problem, I'll add this.  Can you point to a specific 1.4.x commit, to
help with any extra bits that are needed, e.g. anything in configure.ac?

> "But ttn, why do you care about any Guile other than 1.4.x?"
>
> Well, why not?

Well, indeed.  Let's make 2010 the year of repairing our divisions...

With Guile 1.9.x/2.0, we have a fantastic new base system that I think
will serve us well for some years.  With that in place, it would be
great to pull together all the Guile apps and extensions that are out
there, and showcase them working together and doing interesting things.
Plus, as far as possible, I hope we can find ways of making everything
work with older versions of Guile too.

> thi

Regards,
      Neil




  reply	other threads:[~2009-12-27 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 18:50 request: libguile to wrap getsid(2) Thien-Thi Nguyen
2009-12-27 12:46 ` Neil Jerram [this message]
2009-12-27 18:21   ` Neil Jerram
2009-12-27 23:01     ` Thien-Thi Nguyen
2009-12-27 22:58   ` Thien-Thi Nguyen
2009-12-27 23:33     ` Linas Vepstas
2009-12-29  1:08       ` Jeff Wilkinson
2009-12-28  6:34     ` Ken Raeburn
2009-12-28 12:25       ` Thien-Thi Nguyen
2009-12-28 11:11     ` Neil Jerram
2009-12-28 12:18       ` Thien-Thi Nguyen

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=87pr601t5c.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@gnu.org \
    --cc=ttn@gnuvola.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).