From: Cecil Westerhof <Cecil@decebal.nl>
To: help-gnu-emacs@gnu.org
Subject: Re: Using Emacs Lisp for script writing
Date: Wed, 23 Dec 2009 07:27:20 +0100 [thread overview]
Message-ID: <87637y2ojb.fsf@Traian.DecebalComp> (raw)
In-Reply-To: 87r5qm4bt8.fsf@lion.rapttech.com.au
Tim X <timx@nospam.dev.null> writes:
>>> Works like a charm. I made it:
>>> #!/usr/bin/env bash
>>
>> IMO, there's higher probability that /bin/bash be present than /usr/bin/env.
>> And even higher probability that /bin/sh be present.
>>
>> Since you're not using any bash feature in the script, you could as
>> well go for the sure case, and use #!/bin/sh.
>
> I second this. If I remember correctly, to be posix compliant, you must
> have sh, but you don't have to have bash or env.
I have to look into that. I know that bash is not always there -I have
worked on a Tru-64 system, which did not have it-, I also understood
that /usr/bin/env should always be there -as a real file or a link- and
I had it once -I think on a BSD system- that the shell was in another
directory. But I 'always' work with bash, so it could be that /bin/sh is
always there. So lets just change it. And if there is a system where
there is not a /bin/sh lets hope that the administrator is willing to
make the link. Otherwise the script(s) have to be changed, but that is
no rocket science. ;-)
On my system the three calls still work. ;-)
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
next prev parent reply other threads:[~2009-12-23 6:27 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
[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
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 [this message]
[not found] ` <mailman.21.1261430019.1956.help-gnu-emacs@gnu.org>
2009-12-22 0:28 ` Cecil Westerhof
2009-12-18 21:39 ` Andreas Politz
2009-12-19 10:02 ` David Engster
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=87637y2ojb.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).