From: j <jkal@posteo.eu>
To: Chaos Eternal <eternalchaos@shlug.org>
Cc: guile-devel@gnu.org
Subject: Re: feature request: simple hashbang for executable scripts
Date: Mon, 21 Aug 2017 09:21:41 +0000 [thread overview]
Message-ID: <fb9e60fcc26b703e2e1662b2d81cd5c0@posteo.de> (raw)
In-Reply-To: <CAGyY8NtXZwK9FMwGJ7XBQefu+eshTdupfEJN4GKq_NfwGcQtTQ@mail.gmail.com>
that is correct.
i wish there was a way to still use a simple one-line hashbang.
maybe it would be possible to recognise a backslash-escaped newline for
continuing the arguments to the interpreter?
it does not seem like a commonly needed, or even necessary, feature to
support multi-line arguments to interpreter directives in executable
scripts with scsh block comments like this.
by the way, my first example with the !# on the same line does not work.
the !# apparently has to be on the second line.
On 2017-08-21 07:04, Chaos Eternal wrote:
> you can put more arguments in before !#
> that is on-purpose.
>
> On Sat, Aug 19, 2017 at 5:01 PM j kalbhenn <jkal@posteo.eu> wrote:
>
>> scripts of other languages usually need just one line to specify the
>> interpreter:
>>
>> #!/usr/bin/myinterpreter
>>
>> but with guile we have to add a final !#
>>
>> #!/usr/bin/guile !#
>>
>> or even
>>
>> #!/usr/bin/guile -s
>> !#
>>
>> in my opinion, this is not ideal. from my perspective as a guile
>> user this seems to be unnecessarily inconsistent and complicated.
next prev parent reply other threads:[~2017-08-21 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 9:00 feature request: simple hashbang for executable scripts j kalbhenn
2017-08-21 7:04 ` Chaos Eternal
2017-08-21 9:21 ` j [this message]
2017-08-23 6:00 ` Mark H Weaver
2017-08-25 1:30 ` Matt Wette
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=fb9e60fcc26b703e2e1662b2d81cd5c0@posteo.de \
--to=jkal@posteo.eu \
--cc=eternalchaos@shlug.org \
--cc=guile-devel@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).