From: Christian Mauduit <ufoot@ufoot.org>
Cc: guile-user@gnu.org
Subject: Re: setting env variable from Guile
Date: Fri, 29 Jul 2005 21:20:35 +0200 [thread overview]
Message-ID: <42EA8183.4030706@ufoot.org> (raw)
In-Reply-To: <45e3b282050729083211575301@mail.gmail.com>
Hi,
Aurelien Chanudet a écrit :
> Thank you guys for the tip.
>
> Unfortunately, the environnement variable set in this way doesn't
> appear to be visible from the shell guile was launched from. As a
> result, the environnement variable does not appear to be visible to
> the dynamic link editor.
AFAIK this is a UNIX limitation, using setenv within a program will only
change environnement variables for *this* program. Try to execute the
script shell:
#!/bin/bash
export FOO=bar
and FOO won't be set in the "parent" shell. Type directly:
export FOO=bar
and it will be set. Point is the "export" command is interpreted by this
parent shell, so it has means to set in within this shell. No idea how
to do this with Guile, except setting your environnement variable from
Guile and then launch your program _from_ Guile. The way bash does 8-)
Hope this will help.
Christian.
--
Christian Mauduit <ufoot@ufoot.org> __/\__ ___
\~/ ~/(`_ \ ___
http://www.ufoot.org/ /_o _\ \ \_/ _ \_
http://www.ufoot.org/gnupg.pub \/ \___/ \__)
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-07-29 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 15:55 setting env variable from Guile Aurelien Chanudet
2005-07-29 14:29 ` José Roberto B. de A. Monteiro
2005-07-29 15:32 ` Aurelien Chanudet
2005-07-29 19:20 ` Christian Mauduit [this message]
2005-07-30 13:47 ` Mike Gran
2005-07-30 15:12 ` Thien-Thi Nguyen
2005-08-01 14:28 ` Jon Wilson
-- strict thread matches above, loose matches on Subject: below --
2005-07-28 14:00 Aurelien Chanudet
2005-07-29 7:28 ` David Pirotte
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=42EA8183.4030706@ufoot.org \
--to=ufoot@ufoot.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).