8/10    Are there commonly used filename suffixes for sh scripts, csh scripts
        and tcsh scripts?  (e.g. .pl is for Perl scripts; .c is for C files.)
        Thanks.
        \_ Use .sh for sh/bash scripts; never use *csh for any sort of
                       \_ and ksh
           scripting purpose.  It does funny things sometimes-- see Unix
           Power Tools.
           \_ In the words of Tom Christiansen:
              http://www.faqs.org/faqs/unix-faq/shell/csh-whynot
           \_ My script is very simple and it only has several lines of
              commands.  No variable substition, no conditional, etc.  The
              only thing I need the shell to do is some filename expension
              of the form:
                cmd1 ~/foo/{`whoami`_*}/bar/{dir1,dir2,dir3} arg1 | \
                cmd2 ~/baz/`date | cut -d' ' -f1`.txt arg2
              I couldn't get this to work in my crontab file which I suppose
              uses sh syntax, so I ended up putting it in a csh script.  I
              [ Reformatted - motd formatting daemon ]
              know very little about shell scripts anyway.
              [ Reformatted - motd formatting god ]
              \_ It only works in csh because of the ~.  Some other shells
                 will let you use ~, but you should be able to rewrite it in
                 \_ But the {} part doesn't work either.  How do I do
                 sh using ${HOME} instead of ~.
                 \_ But the {} part doesn't work in sh either.  How do I do
                    "bar/{dir1,dir2,dir3}" in sh so that it expands correctly?
                    \_ for i in dir1 dir2 dir3 ; do <stuff> ; done
              \_ DIR="$HOME/foo/`whoami`_*/bar"
                 FILE="$HOME/baz/`date | cut -d' ' -f1`.txt"
                 for i in dir1 dir2 dir3 ;
                 do cmd1 "$DIR/$i" arg1 | cmd2 "$FILE" arg2 ; done
                 \_ But that means running the commands three times instead
                    of running the commands once with the three paths as
                    three arguments.
                    \_ DIR="$HOME/foo/`whoami`_*/bar"
                       FILE="$HOME/baz/`date | cut -d' ' -f1`.txt"
                       for i in dir1 dir2 dir3 ;
                       do MYDIR="$MYDIR $DIR/$i" ; done
                       cmd1 $MYDIR arg1 | cmd "$FILE" arg2
            \_ Actually, .pl is supposed to be for "perl library" files, or
               included snippets of scripts.  Whole perl scripts are supposed
               to be .p, though I never bother putting an extension on them,
               as they're executable in their own right.
               \_ What's your source? Nothing on google that supports your
                  statement, and .pl is absolutely standard usage (with
                  .ph = perl header [mostly perl4 and down] and .pm = perl
                  module [perl5 and up]). Furthermore there's a story floating
                  around about Larry Wall taking the last 2 letters of "BCPL"
                  to complete the sequence of BCPL descendants (.b, .c, .pl).
                  \_ perlcc, for starters.
               \_ In actual usage, I always see .pl as perl executables,
                  and never see .p
                  \_ indeed.
               \_ I thought perl libraries and modules had the .pm extension
                  \_ no, just modules