From: Andy Wingo <wingo@pobox.com>
Subject: Proposal: allow "guile foo.scm"
Date: Thu, 11 Nov 2004 20:26:26 +0200 [thread overview]
Message-ID: <1100197586.19830.125.camel@localhost> (raw)
Hey all,
What do you think of allowing guile to be run as "guile foo.scm"? The
proposal is for it to be the same as "guile -s foo.scm". This would
allow the #! sequence to be shorter, e.g.
#! /usr/bin/env guile
!#
...
instead of
#! /bin/sh
exec guile -s $0 "$@"
!#
assuming you want to find `guile' in the path, of course.
Thoughts?
--
Andy Wingo <wingo@pobox.com>
http://ambient.2y.net/wingo/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-11-11 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 18:26 Andy Wingo [this message]
2004-11-12 14:08 ` Proposal: allow "guile foo.scm" Greg Troxel
2004-11-12 15:19 ` Paul Jarc
2004-12-22 16:25 ` Marius Vollmer
2004-11-12 15:32 ` Jose A. Ortega Ruiz
2004-11-12 15:39 ` Paul Jarc
2004-11-12 21:43 ` Neil Jerram
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=1100197586.19830.125.camel@localhost \
--to=wingo@pobox.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).