unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Krister Svanlund <krister.svanlund@gmail.com>
To: Andrew Gwozdziewycz <apgwoz@gmail.com>
Cc: Ian Price <ianprice90@googlemail.com>, guile-devel@gnu.org
Subject: Re: Running non-scheme scripts: some thoughts
Date: Thu, 12 Jul 2012 00:15:46 +0200	[thread overview]
Message-ID: <CAO_vGe-1tBj_qA_c4XmvK_SXv+urcfKMJ4+25KEvyeOTsDuH1w@mail.gmail.com> (raw)
In-Reply-To: <CADoGzsfZ1XFA_i_NcagNcbFvcdaeBKQRT3Mtb0zXzNJ8duGMWw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

Personally I would think that having Guile guess by extension would be the,
in most cases, most reliable. Otherwise there could be problems loading
several files in different languages etc.

I would think that one of the best solution would be to have a switch to
execute arbitrary commands such as ,L so you would call guile with `guile
--switch ",L elisp"`. The separate executables could then be done as
aliases if one wanted.

On Wed, Jul 11, 2012 at 5:37 PM, Andrew Gwozdziewycz <apgwoz@gmail.com>wrote:

> On Wed, Jul 11, 2012 at 11:31 AM, Ian Price <ianprice90@googlemail.com>
> wrote:
> >
> > Hi,
> >
> > Though guile is really a multi-language vm, it does not provide a simple
> > way to run scripts for languages other scheme from the command line. I
> > think we should add a --language switch that takes a mandatory argument,
> > and use that to determine the language.
>
> Seems smarter to just have different executables:
>
>     guile (and guile-scheme for completeness via hard/soft link)
>     guile-elisp
>     ...
>     guile-LANG
>
> That seems like it'd lead to far less confusion overall.
>
> Andrew
>
> --
> http://www.apgwoz.com
>
>

[-- Attachment #2: Type: text/html, Size: 1709 bytes --]

  reply	other threads:[~2012-07-11 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 15:31 Running non-scheme scripts: some thoughts Ian Price
2012-07-11 15:37 ` Andrew Gwozdziewycz
2012-07-11 22:15   ` Krister Svanlund [this message]
2012-07-12  3:12     ` nalaginrut
2012-07-12  3:27       ` William ML Leslie
2012-07-12  7:40         ` Neil Jerram
2012-08-26 21:16 ` Ludovic Courtès
2013-01-21 11:33   ` Andy Wingo
2013-01-21 16:19     ` Ludovic Courtès
2013-01-22 14:59       ` Andy Wingo
2013-01-22 21:45         ` 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=CAO_vGe-1tBj_qA_c4XmvK_SXv+urcfKMJ4+25KEvyeOTsDuH1w@mail.gmail.com \
    --to=krister.svanlund@gmail.com \
    --cc=apgwoz@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ianprice90@googlemail.com \
    /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).