Guy Smith ([log in to unmask]) wrote:
: Larry Boyd ([log in to unmask]) wrote:
 
: > I have an additionally suggestion.  What if HP selected a filecode that
: > would define command files?  If the file is ASCII it would still work, and
: > if the file is binary, the code could be checked.
 
: I wish to respectfully disagree.  Being the type who never remembers to
: do a chmod on my UNIX scripts, and who then spends several seconds in
: dememtia figuring out why the script won't run, I know I'd make the same
: omission with file codes.
 
I will strongly second that.  I have the same problem with my occasional
UNIX scripts.  90% of the command files I write (MPE or UNIX) are
quick and dirty, emphasis on quick.  Hop in the editor, type out
a couple of lines, and let the system do the typing.  I _don't_ want
to fool around with file codes, chmods, etc.
 
Hmmm, speaking of which, I'll bet I could ...
 
$ cat mkcmd
vi $1
chmod u+x $1
ll $1
 
there, perfect example, q&d homebrew for the unix side.  Don't forget to
chmod the mkcmd file though :-)
 
Dave Day - CSY Performance Consulting