From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Etymology of shebang
Date: Fri, 21 Apr 2017 11:07:48 -0400 [thread overview]
Message-ID: <CAC20D2MT0UsODkGzcHONwOFA7BpKn4bPXMHCwsVRXbkrX=68uQ@mail.gmail.com> (raw)
In-Reply-To: <040501d2baae$47bc8a20$d7359e60$@ronnatalie.com>
Sorry, yes -- which is why I think the exec hack first show up in the BSD
kernel. It was an efficiency trick on the PDP-11's. The idea was to catch
the change of shell as soon as possible.
On Fri, Apr 21, 2017 at 10:48 AM, Ron Natalie <ron at ronnatalie.com> wrote:
> Oldest actual use in a post I can find is 1997
>
>
>
> *I did find something I had completely forgot about. The csh used to
> (probably still does?) differentiate between Bourne shell scripts and csh
> scripts by looking for #.*
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170421/ab35ba85/attachment.html>
prev parent reply other threads:[~2017-04-21 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 14:48 Ron Natalie
2017-04-21 15:07 ` Clem Cole [this message]
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='CAC20D2MT0UsODkGzcHONwOFA7BpKn4bPXMHCwsVRXbkrX=68uQ@mail.gmail.com' \
--to=clemc@ccc.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 NNTP newsgroup(s).