Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!auspex!guy From: guy@auspex.auspex.com (Guy Harris) Newsgroups: comp.unix.questions Subject: Re: #! shells (was: Re: AIX (is it unix)?) Message-ID: <2501@auspex.auspex.com> Date: 26 Sep 89 18:24:13 GMT References: <1702@naucse.UUCP><978@mtxinu.UUCP> <868@cirrusl.UUCP> <2486@auspex.auspex.com> <3367@fireball.cs.vu.nl> Reply-To: guy@auspex.auspex.com (Guy Harris) Organization: Auspex Systems, Santa Clara Lines: 39 >You forgot to important `shells': > > #!/bin/sed -f > #!/bin/awk -f >:-) And *you* forgot #! /bin/make -f :-) :-) and, for that matter, #! /usr/ucb/vi #! /usr/local/emacs #! /bin/ed etc. :-) :-) :-) :-) :-) >Can you figure out why I don't want sed's `#n' hack to be limited to the first >line of the script only? The headache with that hack is that somebody might have a long comment (I think the S5R4 "sed" will support "#" as a general comment character, as BSD's "sed" already does) one of the lines of which begins with "n". A better fix would be to teach "sed" about "getopt", so that #!/bin/sed -nf works. >What I REALLY want, of course, is to get rid of that (understandable but) >stupid 32-characters-and-1-option `#!' limitation. It'd be nice, but I don't know if it's coming in S5R4 - or 4.4BSD, for that matter.