From: mascheck@in-ulm.de (Sven Mascheck)
Subject: [TUHS] History of #! interpretation in Unix
Date: Sun, 16 Jan 2011 22:08:12 +0100 [thread overview]
Message-ID: <20110116210812.GB26424@lisa.in-ulm.de> (raw)
In-Reply-To: <20110116201745.GE3374@mercury.ccil.org>
John Cowan wrote:
> Sven Mascheck scripsit:
> > DMR might have known the csh-hack [...]
>
> Having two different people invent the shebang independently
who (or what system) do you mean was the 2nd?
> > > > > Modern shells will use /bin/sh to run scripts that *don't* have shebangs,
[...]
> No, I meant that bash does what ksh does: uses itself, [...]
With /bin/sh you actually meant any shell calling "itself"?
Otherwise I'm afraid, I have some difficulties following you.
> IMHO the Posix sh definition should be extended so that all
> shells claiming Posix-compliance should do shebangs.
Shells themselves should implement it, not the kernel?
There was a working group resolution to standardize #!, which didn't
make it, http://www.opengroup.org/platform/resolutions/bwg2000-004.html
you could chime in
next prev parent reply other threads:[~2011-01-16 21:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 8:43 Warren Toomey
2011-01-16 9:55 ` John Cowan
2011-01-16 13:20 ` Sven Mascheck
2011-01-16 17:17 ` John Cowan
2011-01-16 19:19 ` Sven Mascheck
2011-01-16 20:17 ` John Cowan
2011-01-16 20:42 ` Larry McVoy
2011-01-16 21:08 ` Sven Mascheck [this message]
2011-01-16 21:37 ` John Cowan
2011-01-17 16:35 ` Warner Losh
2011-01-17 20:47 ` John Cowan
2011-01-17 10:09 ` Tim Bradshaw
2011-01-16 10:53 ` Wilko Bulte
2011-01-17 16:25 ` Warner Losh
2011-01-17 19:02 ` Jeremy C. Reed
2011-01-17 20:51 ` John Cowan
2011-01-17 22:41 ` Jeremy C. Reed
2011-01-17 20:58 ` Sven Mascheck
2011-01-19 4:10 ` Cyrille Lefevre
2011-01-19 20:35 ` Sven Mascheck
2011-01-20 4:09 ` Cyrille Lefevre
2011-01-28 19:38 ` Jeremy C. Reed
2011-01-30 15:05 ` Sven Mascheck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110116210812.GB26424@lisa.in-ulm.de \
--to=mascheck@in-ulm.de \
/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 NNTP newsgroup(s).