The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Bourne shell and comments
Date: Fri, 21 Apr 2017 02:07:00 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.02.1704210205530.81367@frieza.hoshinet.org> (raw)
In-Reply-To: <272995B6-6842-4E4F-8A69-8B5C57EE4E35@bitblocks.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On Thu, 20 Apr 2017, Bakul Shah wrote:

> From the horse’s mouth (as per https://www.talisman.org/~erlkonig/documents/dennis-ritchie-and-hash-bang.shtml ):
>
>
> From: "Ritchie, Dennis M (Dennis)** CTR **" <dmr at research.bell-labs.com>
> To: <erlĸonigⓐtαlismαn.org>
>
> Date: Thu, 19 Nov 2009 18:37:37 -0600
> Subject: RE: What do -you- call your #!<something> line?
>
> I can't recall that we ever gave it a proper name.
> It was pretty late that it went in--I think that I
> got the idea from someone at one of the UCB conferences
> on Berkeley Unix; I may have been one of the first to
> actually install it, but it was an idea that I got
> from elsewhere.
>
> As for the name: probably something descriptive like
> "hash-bang" though this has a specifically British flavor, but
> in any event I don't recall particularly using a pet name
> for the construction.
>
>   Regards,
>   Dennis
>
>
> [Sorry about the html]

In the process of replying, I've de-htmlized it. ;)

Anyway, I use "pound-bang" which is basically the same thing, although I 
must say it has a particular violent quality about it...

-uso.


  reply	other threads:[~2017-04-21  6:07 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 [this message]
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
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=alpine.BSF.2.02.1704210205530.81367@frieza.hoshinet.org \
    --to=usotsuki@buric.co \
    /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).