From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Bourne shell and comments
Date: Fri, 21 Apr 2017 10:45:12 -0400 [thread overview]
Message-ID: <03f501d2baad$e398b4b0$aaca1e10$@ronnatalie.com> (raw)
In-Reply-To: <CALMnNGjEWe8WHsMZ8dw2+RK7SFAoerA04sy47RGzDrx2vEt-Uw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Amusingly, people were asking this question in 2000. I found this in comp.unix.shell:
in news: at.linux, there's a discussion about why the
interpretersymbol #! is called shebang (you can imagine, which
theories already occurred). but does anybody know, WHY this is really
called shebang?
sorry for being a bit offtopic, but it's essential :)
thanks before.
Stefan
No origins were found in the messages other than a guess that it was a cute shortening of “SHARP BANG.”
Wasn’t it Ken Thompson who said if he had it to do over again he’d have put an “e” on the end of create. Five decades of calling it “CREE – AT”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170421/c7a2811a/attachment.html>
next prev parent reply other threads:[~2017-04-21 14:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 20:48 Warren Toomey
2017-04-18 20:51 ` Ron Natalie
2017-04-18 21:45 ` Grant Taylor
2017-04-18 22:16 ` Ron Natalie
2017-04-18 22:40 ` Toby Thain
2017-04-19 18:36 ` Stephen Kitt
2017-04-19 20:35 ` Arthur Krewat
2017-04-19 0:50 ` Lyndon Nerenberg
2017-04-19 8:35 ` Andreas Kusalananda Kähäri
2017-04-19 16:31 ` Grant Taylor
2017-04-19 16:59 ` Andreas Kusalananda Kähäri
2017-04-19 17:36 ` Bakul Shah
2017-04-19 17:59 ` Grant Taylor
2017-04-20 20:13 ` Clem Cole
2017-04-20 20:17 ` Chet Ramey
2017-04-21 3:28 ` arnold
2017-04-21 3:43 ` Bakul Shah
2017-04-21 6:07 ` Steve Nickolas
2017-04-21 11:18 ` Clem cole
2017-04-21 13:20 ` Michael Kjörling
2017-04-18 20:56 ` Chet Ramey
2017-04-19 21:02 ` Sven Mascheck
2017-04-19 22:07 ` Steffen Nurpmeso
2017-04-20 0:31 ` shawn wilson
2017-04-20 0:35 ` shawn wilson
2017-04-20 3:50 ` Andy Kosela
2017-04-20 4:47 ` Warner Losh
2017-04-21 1:42 ` Nemo
2017-04-21 10:54 ` Ron Natalie
2017-04-21 14:22 ` Andy Kosela
2017-04-21 14:45 ` Ron Natalie [this message]
2017-04-22 2:46 ` Dave Horsfall
2017-04-20 16:39 ` Sven Mascheck
2017-04-20 21:42 ` Steffen Nurpmeso
2017-04-19 19:18 Doug McIlroy
2017-04-21 17:03 Doug McIlroy
2017-04-21 18:15 ` Clem Cole
2017-04-21 19:13 ` Steve Johnson
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='03f501d2baad$e398b4b0$aaca1e10$@ronnatalie.com' \
--to=ron@ronnatalie.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).