Very Computer

by **Stephen Riehm [Romuli** » Sat, 06 Jul 1991 16:23:57

The #!/bin/csh line is a lot more powerfull that it first appears.
essentially you can specify ANY program in this line, and it will be
executed, with the script file being specified just after the last arg
specified in this line. sound confusing?
examples:

--- awk script to indent the text in the input stream ---
#!/usr/bin/awk -f
{
print ">" $0;
}
--- end script ---
set the executable flag, and type the following..

script_file < in_file

what actually gets run is..

awk -f script_file < in_file

its cute and can be used with just about anything, including make,
cat, sed, ed, vi, and lots lots more.

have fun guys!

catchya
thanx in advance

=========================================================================
Romulis [Stephen Riehm] BKX Australia Pty. Ltd.

=====< My employer is too busy with his own ideas, these are MINE!>======
--
catchya
thanx in advance

under new management

by **Michael Meissn** » Tue, 09 Jul 1991 01:45:43

| The #!/bin/csh line is a lot more powerfull that it first appears.
| essentially you can specify ANY program in this line, and it will be
| executed, with the script file being specified just after the last arg
| specified in this line. sound confusing?

Note that most systems put a limit on the size of the pathname (32 is
a common value for this limit). This means you can typically execute
stuff in /bin, /usr/bin, or /usr/local/bin, but would have problems
with longer pathnames.
--

Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142

You are in a twisty little passage of standards, all conflicting.

Very Computer

Something which is not so obvios but real cute..

Something which is not so obvios but real cute..

Something which is not so obvios but real cute..