unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user@gnu.org
Subject: Re: CGI scripting with Guile
Date: Sun, 16 Mar 2008 14:16:26 +0100	[thread overview]
Message-ID: <87myoy3j2t.fsf@ambire.localdomain> (raw)
In-Reply-To: 87lk4iddzf.fsf@moley.moleskin.org

() Sebastian Tennant <sebyte@smolny.plus.com>
() Sun, 16 Mar 2008 14:56:20 +0200

   This is incredibly useful.  Thank you for pointing it out.

You're welcome.  If you find any bugs in it, i'm all ears...

   Just out of curiostiy, why the '.in' file extension?
   Is it to do with make?

It's customary for autoconf-substituted files (see configure.in)
to use the .in extension.  Running the configure script produces
id.cgi from id.cgi.in, with the @var@ sequences expanded.

   > #!/bin/sh
   > exec @GUILE@ -s $0 "$@" # -*- scheme -*-
   > !#

   Also, why the shell?

This preamble can accomodate Guile installed in different places.
For example, in my case, @GUILE@ becomes /home/ttn/local/bin/guile,
but for you it would most likely be different.  You should be able
to safely replace it w/ the preamble used in your test script.

thi





  reply	other threads:[~2008-03-16 13:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 22:10 CGI scripting with Guile Sebastian Tennant
2008-03-15 22:40 ` Thien-Thi Nguyen
2008-03-16  0:41   ` Sebastian Tennant
2008-03-16  9:16     ` Thien-Thi Nguyen
2008-03-16 10:41       ` Sebastian Tennant
2008-03-16 12:51   ` Sebastian Tennant
2008-03-16 13:06     ` Thien-Thi Nguyen
2008-03-16 15:11       ` Sebastian Tennant
2008-03-16 12:56   ` Sebastian Tennant
2008-03-16 13:16     ` Thien-Thi Nguyen [this message]
2008-03-18 20:19       ` Sebastian Tennant
2008-03-19  7:22         ` Thien-Thi Nguyen
2008-03-19  9:24           ` Sebastian Tennant
2008-03-15 22:48 ` Sebastian Tennant
2008-03-15 22:52   ` Sebastian Tennant

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=87myoy3j2t.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --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).