From: Cecil Westerhof <Cecil@decebal.nl>
To: help-gnu-emacs@gnu.org
Subject: Re: Using Emacs Lisp for script writing
Date: Tue, 22 Dec 2009 18:04:10 +0100 [thread overview]
Message-ID: <87skb32b5h.fsf@Traian.DecebalComp> (raw)
In-Reply-To: 871vinrp52.fsf@hubble.informatimago.com
pjb@informatimago.com (Pascal J. Bourguignon) writes:
>>> It is not a big deal, but when the script is put on another system and
>>> on this system clisp is in another location, the script has to be
>>> modified (or a link has to be created). But halving the execution time
>>> is important enough.
>>
>> There is a trick used by other scripting languages to get around the
>> issue of the script interpreter being in a different location and for
>> those systems which only handle 30 characters in the #! line
>>
>> #!/bin/sh
>> # the next line restarts using the interpreter foobar \
>> exec foobar "$0" "$@"
>>
>> I wonder if something like this could work.
>
> Sure.
>
> [pjb@hubble :0.0 ~]$ cat ./s
> #!/bin/sh
> #| Both a lisp and sh comment.
> exec clisp "$0" "$@"
> |#
Works like a charm. I made it:
#!/usr/bin/env bash
#| Both a lisp and sh comment.
exec clisp -C "$0" "$@"
|#
And now all three work:
script.cl
clisp -C script.cl
clisp -c script.cl
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
next prev parent reply other threads:[~2009-12-22 17:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 15:32 Using Emacs Lisp for script writing Cecil Westerhof
2009-12-16 16:24 ` Sam Steingold
2009-12-16 17:18 ` Teemu Likonen
2009-12-16 23:37 ` Cecil Westerhof
2009-12-17 19:08 ` Sam Steingold
2009-12-16 23:04 ` Pascal J. Bourguignon
2009-12-18 21:39 ` Andreas Politz
2009-12-19 10:02 ` David Engster
[not found] ` <mailman.13065.1260980854.2239.help-gnu-emacs@gnu.org>
2009-12-16 23:31 ` Cecil Westerhof
2009-12-17 11:29 ` Cecil Westerhof
2009-12-21 18:35 ` Frank Fredstone
2009-12-21 19:20 ` Cecil Westerhof
2009-12-21 20:57 ` Sam Steingold
2009-12-21 21:13 ` Sam Steingold
2009-12-21 23:06 ` Tim X
2009-12-22 0:46 ` Cecil Westerhof
2009-12-22 11:26 ` Tim X
2009-12-22 13:51 ` Cecil Westerhof
2009-12-22 15:36 ` Pascal J. Bourguignon
2009-12-22 16:54 ` Cecil Westerhof
2009-12-23 2:50 ` Tim X
2009-12-23 7:38 ` Cecil Westerhof
[not found] ` <mailman.18.1261429198.1956.help-gnu-emacs@gnu.org>
2009-12-22 0:06 ` Cecil Westerhof
2009-12-22 12:51 ` Tim X
2009-12-22 15:42 ` Pascal J. Bourguignon
2009-12-22 17:04 ` Cecil Westerhof [this message]
2009-12-22 19:02 ` Pascal J. Bourguignon
2009-12-22 20:49 ` Cecil Westerhof
2009-12-23 3:19 ` Tim X
2009-12-23 6:27 ` Cecil Westerhof
[not found] ` <mailman.21.1261430019.1956.help-gnu-emacs@gnu.org>
2009-12-22 0:28 ` Cecil Westerhof
2014-05-10 5:54 ` mug896
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skb32b5h.fsf@Traian.DecebalComp \
--to=cecil@decebal.nl \
--cc=help-gnu-emacs@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).