HDTenEightyP/NetNews huggingface dataset:
From: hall@beta.lanl.gov (Michael L. Hall)
Subject: Escaping brackets in csh - SUMMARY
Organization: Los Alamos National Laboratory
Date: Wed, 12 Aug 1992 23:46:45 GMT

I posted a question yesterday about renaming some VMS files that
had the [dir1.dir2.dir3]filename.ext format into a unix format
which retained the directory structure. I was wanting to do it 
with a foreach (csh) or for (sh) command, but was having trouble
escaping (or quoting) the brackets ([]). The best (or at least
easiest for me to implement) answer was from Arne H. Juul - 
<arnej@lise.unit.no>:

------------------------------------
This is my csh solution - 'do it with sh'!

csh% ls
[asd.efg]gruff  [asd.hij]spiff  [asd.xcv]qwerty [bfd.zxc]foo    [jkl.bnm]bar
csh% 
csh% cat > rename.sh
#!/bin/sh

/bin/ls \[* | while read filename; do
    dir=`echo $filename | sed 's/^\[\(.*\)\].*/\1/' | tr . /`
    dirs=`echo $filename | sed 's/^\[\(.*\)\].*/\1/' | tr . ' '`
    file=`echo $filename | sed 's/^\[.*\]//'`
    set $dirs
    ( for x do mkdir $x 2>/dev/null; cd $x; done )
    echo making $dir/$file
    cp $filename $dir/$file
done
csh% sh rename.sh
csh% ls
asd/    bfd/    jkl/
csh% 
csh% find . -print
.
./asd
./asd/efg
./asd/efg/gruff
./asd/hij
./asd/hij/spiff
./asd/xcv
./asd/xcv/qwerty
./bfd
./bfd/zxc
./bfd/zxc/foo
./jkl
./jkl/bnm
./jkl/bnm/bar


There is a reason why csh isn't very well-liked in comp.unix.shell - and
this is an example of the reason. Or to put it another way: I tried
to make csh's foreach do it, but no way.

You could do the above in sh with
	for filename in \[* ; do
instead of the while, but the "ls | while read" is nicer.
You could also do mv instead of cp in the shell-script above, of course.
---------------------------

Icarus Sparry gave me a similar answer, but I used the first one 
because it was more easily deciphered. Many others suggested that
I use the bourne shell, as brackets and fors mix much better than
brackets and foreaches.

I am continually amazed at how people out in netland are willing to
help you solve your problems.

Hearty thanks to:

Arne Henrik Juul <arnej@lise.unit.no>
Icarus Sparry    <I.Sparry@sunlab1.bath.ac.uk>
Watanabe Maki    <maki@jit.dec.com>
Georg Wittig     <Georg.Wittig@gmd.de>
Leo              <leo@ine.philips.nl>
Tom Christiansen <tchrist@pixel.convex.com>
                 
-- 
+----------------------------------------------------------------------+
| Michael L. Hall    There are times, sir, when men of good conscience |
| hall@lanl.gov      cannot blindly follow orders. - Jean-Luc Picard   |
+----------------------------------------------------------------------+
Newsgroups: comp.unix.shell
From: s902113@minyos.xx.rmit.oz.au (Luke Mewburn)
Subject: testing if running shell script in {t}csh
Organization: RMIT Computer Centre, Melbourne Australia.
Date: Wed, 19 Aug 1992 02:15:23 EST


What is a good reliable method of testing if you are not running as a
user shell (i.e, as a script).

Now, don't tell me about the existance of $prompt. This is no good if
the prompt is setup in /etc/csh.cshrc (or whatever), which I have no
control over whatsoever....


Thanx in advance

Luke.
-- 

"...(and) We've heard how teen prostitution, pregnancy,        Luke Mewburn
drug use, cults, runaways, suicide and poor hygiene are          s902113@
sweeping this nation. We thought you might like to share          minyos.
with the committee any particular *causes* you might see            xx.
for those latter problems..."                                      rmit.
"  I dunno, Maybe the proliferation of narrow, suffocating          oz.
zealotry masquerading as parenting in this country."                au
              Steve Dallas, 'Bloom County'.

Newsgroups: comp.unix.shell
From: arnej@Lise.Unit.NO (Arne Henrik Juul)
Subject: Re: Escaping brackets in csh - SUMMARY
Reply-To: arnej@lise.unit.no
Organization: Norwegian Institute of Technology
Date: Fri, 14 Aug 92 03:34:45 GMT

In article <glaze.093@glaze>, glaze@cs.mu.oz.au (Glaze) writes:
 > One thing you may need to do is change the ``mkdir'' to ``mkdir -p'' above.
 > The -p option requesting that mkdir create any missing parent directories.
 > However, older mkdir's don't support it, so here's a small script I
 > whipped up for you:

Wrong - it was already in the script. Read it carefully:

#!/bin/sh
/bin/ls \[* | while read filename; do
    dir=`echo $filename | sed 's/^\[\(.*\)\].*/\1/' | tr . /`
    dirs=`echo $filename | sed 's/^\[\(.*\)\].*/\1/' | tr . ' '`
    file=`echo $filename | sed 's/^\[.*\]//'`
    set $dirs
    ( for x do mkdir $x 2>/dev/null; cd $x; done )
    echo making $dir/$file
    cp $filename $dir/$file
done


The 'for' loop is in there just to make the subdirectories in the
needed order, like this:

filename is '[asdf.zxcv]qwer'.
after the "dirs=" line, the dirs variable is "asdf zxcv".
after the set line, $1 is asdf, $2 is zxcv.
in the for loop, x get set to $1 $2 ..., that is asdf first, then zxcv.
asdf is mkdir'd, and we cd into asdf.
zxcv is mkdir'd, and we cd into zxcv.

This is why the ( ) is there - we don't want the main loop to cd into
asdf/zxcv, so we just loose that subprocess.


Did you test it? No. Did I test it? Yes.

Moral: Never ever post anything without testing first (unless you're a
wizard, which I am not, and which you apparently are not :-).


--
Arne H. Juul  --  arnej@lise.unit.no  --  University of Trondheim, Norway
Newsgroups: comp.unix.shell
From: dattier@ddsw1.mcs.com (David W. Tamkin)
Subject: Re: Octal chmod status
Organization: Contributor Account at ddsw1, Chicago, Illinois  60657
Date: Sun, 16 Aug 1992 02:56:15 GMT
X-Disclaimer:  Material posted in this article is the sole responsibility of
                the poster and does not represent MCSNet or the system owners.

hsc@sybase.com (Howard Cohen) wrote in <22411@sybase.sybase.com>:

| Well, here's a brute force method I've used successfully.  This can
| certainly be done in a smarter way, and it could also be made to understand
| things like the sticky bit, the setuid bit, the setgid bit, etc.  I didn't
| need that stuff though because I knew the files were source code.
| 
| ------------------------- cut here --------------------------------------
| 
| #!/bin/sh
| 
| LSPERMS=`ls -l "$1" | sed -e "s:^\([^  ][^     ]*\).*:\1:"`
| USR=`echo $LSPERMS X| sed -e "s:.\(...\).*:\1:"`
| GRP=`echo $LSPERMS X| sed -e "s:....\(...\).*:\1:"`
| OTH=`echo $LSPERMS X| sed -e "s:.......\(...\).*:\1:"`

How about this to replace those four lines:

eval `ls -ld "$1" | sed 's/^.\(...\)\(...\)\(...\).*/USR=\1 GRP=\2 OTH=\3/'`

| PERMS=""
| for elem in $USR $GRP $OTH
| do
|      case "$elem" in
|        ---)    PERMS="${PERMS}0";;
|        --x)    PERMS="${PERMS}1";;
|        -w-)    PERMS="${PERMS}2";;
|        -wx)    PERMS="${PERMS}3";;
|        r--)    PERMS="${PERMS}4";;
|        r-x)    PERMS="${PERMS}5";;
|        rw-)    PERMS="${PERMS}6";;
|        rwx)    PERMS="${PERMS}7";;
|      esac
| done
| 
| echo $PERMS

The rest is pretty darn clever.

David W. Tamkin   Box 59297   Northtown Station, Illinois  60659-0297
dattier@ddsw1.mcs.com    CompuServe: 73720,1570    MCI Mail: 426-1818
From: chuckt@scnteam1.austin.ibm.com (Charles N. Tomlinson)
Newsgroups: comp.unix.shell
Subject: Re: If shell command switches.
Date: 18 Aug 92 18:45:36 GMT
Organization: IBM, Austin


>does anyone know where I can find the complete switch listing 
>of the "if" statement?  I can't seem to find it anywhere..ie:
>man csh/tcsh/ksh.., yet I know of the if [-f] and if [-r] 
>only because I saw it used in other scripts.  There are other
>switches..but apparently sparse documentation as to what they 
>are and do.
>
>---
>Dan.

If you look up the man pages on the command "test" or "[ ]",  this should give
you the list that you are looking for.  

Chuck T.

---

================================================================================
  Peasant 1 : " He must be a king. "    | Charles N. Tomlinson    (Chuck)
  Peasant 2 : " Why? "                  | Phone: @AIC: (512) 794-8016 ext.384
  Peasant 1 : " He hasn't got sh*t all  |        @IBM: (512) 823-8845
                over him."              | 
                                        |
  Monty Python's "The Holy Grail"       | Inet  : chuckt@scnteam1.austin.ibm.com
================================================================================
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.shell
Subject: Re: Octal chmod status
Date: 20 Aug 92 02:50:36 GMT
Article-I.D.: news.1992Aug20.025036.12745
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
Originator: tchrist@pixel.convex.com
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of jerry@incc.com (Jerry Rocteur):
:Why is this person continually annoying people with information about perl ??? 

Like stress, annoyance in internally not externally generated.
I merely offer solutions.  If you don't like them, and it upsets
you, then you bring this on yourself.

:Please excuse my ignorance but is perl a shell ????? is this not
:comp.unix.shell ?? I may be wrong but *who* want to be pestered with
:perl tidbits ?? I don't, if I did I would join a perl newsgroup ?? 

In a shell discussions, you expect to hear solutions suggesting 
tools like sed, awk, tr, sort, and their ilk.  Perl is just
another one of these, albeit more functional.  

I try to propose the right solution, irrespective of its parentage.
Often tasks aren't implementable in sh alone, but since this is a 
shell newsgroup, as you've pointed out, I try very hard to avoid 
writing the answer in C.  

I will excuse your ignorance for this post alone.  In penitence,
however, you get to read the perl FAQ, which I shall send in the mail.

You're welcome.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

"The number of UNIX installations has grown to 10, with more expected."
    - _The UNIX Programmer's Manual_, Second Edition, June, 1972.
Newsgroups: comp.unix.shell
From: ash@ulysses.mr.ams.com (Alan Harder)
Subject: Re: Octal chmod status
Organization: American Math. Society
	<104.22185@incc.com> <1992Aug20.025036.12745@news.eng.convex.com>
Date: Thu, 20 Aug 1992 15:53:24 GMT

In article <1992Aug20.025036.12745@news.eng.convex.com> Tom Christiansen <tchrist@convex.COM> writes:

   >From the keyboard of jerry@incc.com (Jerry Rocteur):
   >:Why is this person continually annoying people with information about perl ??? 

   >Like stress, annoyance in internally not externally generated.
   >I merely offer solutions.  If you don't like them, and it upsets
   >you, then you bring this on yourself.

   >:Please excuse my ignorance but is perl a shell ????? is this not
   >:comp.unix.shell ?? I may be wrong but *who* want to be pestered with
   >:perl tidbits ?? I don't, if I did I would join a perl newsgroup ?? 

   >In a shell discussions, you expect to hear solutions suggesting 
   >tools like sed, awk, tr, sort, and their ilk.  Perl is just
   >another one of these, albeit more functional.  

   >I try to propose the right solution, irrespective of its parentage.
   >Often tasks aren't implementable in sh alone, but since this is a 
   >shell newsgroup, as you've pointed out, I try very hard to avoid 
   >writing the answer in C.  

   >I will excuse your ignorance for this post alone.  In penitence,
   >however, you get to read the perl FAQ, which I shall send in the mail.

   >You're welcome.

Maybe this thread belongs on alt.talk.religion.  Believe me, many
people out there think we're *all* crazy for working with *unix* boxes.
This problem would obviously be easier to solve in cobol on an AS400
machine ;-).
From: stuart@wstuart (Stuart Hood)
Newsgroups: comp.unix.shell
Subject: Help: how to keep spaces in args
Summary: How do I maintain an argument with spaces in
Keywords: sh, getopt
Date: 19 Aug 92 15:36:07 GMT
Organization: Siemens Nixdorf Information Systems Ltd.
X-Newsreader: Tin 1.1 PL4

Basically I want the following program to output "Hi there",
rather than just "Hi"

Script started on Wed Aug 19 14:07:35 1992
$ cat t
#!/bin/sh

set -- `getopt a:b "$@"`

while test $# -gt 0
do
    case $1 in
        -a)
            echo $2
            shift 2
            ;;
	-b)
	    shift
	    ;;
        *)
            shift
            ;;
    esac
done
$ ./t -a "Hi there"
Hi
$ 
script done on Wed Aug 19 14:08:00 1992

Adding an "eval" to the "set" line doesn't help because
"getopt" doesn't out put any quote characters around its
arguments.

I can think of 2 hacks to get round this:

- have the "-a" case grab in all arguments until it reaches
  another option.
- replace all spaces in the arguments with, say, '!' before
  doing the getopt and then restore them when needed.

I don't like either of these solutions, can anyone suggest
a better solution?

Thanks in advance for any help,

Stuart.
-
--
S I E M E N S  Stuart Hood === Siemens Nixdorf House, Bracknell, Berks, UK
-------------  Phone: + 44-344-850892          Email: stuart@siesoft.co.uk
N I X D O R F  - Never let ignorance stand in the way of a good argument -
Newsgroups: comp.unix.shell
From: rantapaa@s6.math.umn.edu (Erik E. Rantapaa)
Subject: Re: Array and looping in Bourne Shell
Organization: University of Minnesota
Date: Sun, 23 Aug 1992 04:09:38 GMT

peter@merlin.acadiau.ca (Peter Steele) writes:

>I need to write a script that takes a list and generates
>various permutations of that list, e.g., if the list is
>"a b c", I want to generate the following data sets:
...

I guess that you want all strings "p1 p2" where p1 and p2 are
prefixes of 'a,b,...' and p1 is a prefix of p2.

In that case, try this.  (Invoke as 'script a b c', for example.)

#!/bin/sh
(
	mkdir /tmp/abc$$
	cd /tmp/abc$$
	f=
	for x
	do
		cat < /dev/null > "$f$x"
		f="$f$x,"
	done
	for x in * ;
	do
		for y in `echo $x*` ;
		do
			echo $x $y
		done
	done
	rm -rf /tmp/abc$$
) | sort # just in case globbing doesn't return files in alphabetical order
--
        Erik Rantapaa                   rantapaa@math.umn.edu

 Imagination is the one weapon in the war against reality.
 		-- Jules de Gaultier
From: abmg@cathedral.cerc.wvu.wvnet.edu (Aliasghar Babadi)
Newsgroups: comp.unix.shell
Subject: mail script
Keywords: mail
Date: 20 Aug 92 19:52:35 GMT



Hi,
        I have a file of email addresses. I want to send the same mail
to each address in the file, separately (one address in the mail header
for each one). Is there any script that I can use for that. Thanks.
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Octal chmod status
Originator: tchrist@pixel.convex.com
Date: Thu, 20 Aug 1992 13:10:38 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of jerry@incc.com (Jerry Rocteur):
:Please excuse my ignorance but is perl a shell ????? is this not
:comp.unix.shell ?? I may be wrong but *who* want to be pestered with
:perl tidbits ?? I don't, if I did I would join a perl newsgroup ?? 

My, but who would want to be pestered with C tidbits?  This is
after all a shell group, so we should allow no solutions requiring
anything but shell built-ins, right?  Wrong.

--tom

-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
Unix is like a toll road on which you have to stop every 50 feet to
pay another nickel.  But hey!  You only feel 5 cents poorer each time.
	--Larry Wall in <1992Aug13.192357.15731@netlabs.com>
Newsgroups: comp.unix.shell
From: ckd@eff.org (Christopher Davis)
Subject: Re: Portability of ASCII across Unixes (was Re: How do I get .login to pause ?)
Organization: Electronic Frontier Foundation Tech Central
	<1992Aug6.195643.4702@prl.dec.com> <Bss2xD.GKE@root.co.uk>
	<22412@sybase.sybase.com> <Bt4qL6.JpA@root.co.uk>
	<22651@sybase.sybase.com>
Date: Sun, 23 Aug 1992 03:09:35 GMT

HC> == Howard Cohen <hsc@sybase.com> 

 HC> Any *Unix* machine, yes.  So name one that doesn't support ASCII.

I bet something running AIX/370 is still thinking in EBCDIC.

Of course, whether or not you define that as a Unix machine... ;)
--
Christopher Davis * ckd@eff.org * System Administrator, EFF * +1 617 864 0665
            ``Ed Gruberman, you fail to grasp Ti Kwan Leep.
            Approach me that you might see.'' -- The Master
Newsgroups: comp.unix.shell
From: qpliu@phoenix.princeton.edu (q.p.liu)
Subject: Re: csh echo newlines
Originator: news@nimaster
Reply-To: qpliu@princeton.edu
Organization: Princeton University
Distribution: na
Date: Sat, 22 Aug 1992 22:39:00 GMT

In article <1992Aug22.193400.14637@Princeton.EDU> rtbunker@tan.Princeton.EDU (Ross T. Bunker) writes:

>>> wb8foz@skybridge.SCL.CWRU.Edu (David Lesher) writes:
>>> >How do I get a csh echo statement to output a newline?

>i do it this way in sh

That's csh, not sh.

> ( echo "blah"; echo "blah"; echo "blah" ) | whatever cmd.

Yuck!  For sh, what's wrong with:

echo "asdf
l;kj
asldkfj" | whatnot
-- 
qpliu@princeton.edu           Standard opinion: Opinions are delta-correlated.
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Octal chmod status
Originator: tchrist@pixel.convex.com
Date: Tue, 18 Aug 1992 18:16:09 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of mju@mudos.ann-arbor.mi.us (Marc Unangst):
:Boy, all the solutions that have been offered so far have been pretty
:gross.  Might I suggest this one?

You might, and people might even use it if they want to lug
another huge a.out and overly large and misplaceable foo.c 
around with them wherever they go.  I'd just use this:

    perl -e 'printf("%04o\n", (stat($ARGV[0]))[2] & 07777)'

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

"The number of UNIX installations has grown to 10, with more expected."
    - _The UNIX Programmer's Manual_, Second Edition, June, 1972.
Newsgroups: comp.unix.shell
Subject: Re: challenge: hex sort
From: ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig)
Date: Thu, 13 Aug 1992 07:56:16 GMT
Organization: University of Auckland, New Zealand.

fitzgb@mml0.meche.rpi.edu (Brian Fitzgerald) writes:

>Write a shell script to sort hex in numerical order.

tr [a-f] [A-F] | awk ' { printf "%80s\n",$1 } ' | sort | awk ' { print $1 } '
-- 
Thomas Koenig, ecmtwhk@ccu1.aukuni.ac.nz, ib09@rz.uni-karlsruhe.de
The joy of engineering is to find a straight line on a double logarithmic
diagram.
Newsgroups: comp.unix.shell
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Subject: Re: Octal chmod status
Date: Sat, 15 Aug 1992 05:11:08 GMT
Organization: The Programmer's Pit Stop, Ann Arbor MI

In article <17205.2219215579@kcbbs.gen.nz> Rowan_Smith@kcbbs.gen.nz (Rowan Smith) writes:
>   Can somebody please give me a command/method by which I can get the 
>   octal equivilant of rwxrwxr-x etc so that I can do the following.
>
>   set perm = 'octalconv <filename>'
>
>   is ($perm != 0511) then
>      etc....

Boy, all the solutions that have been offered so far have been pretty
gross.  Might I suggest this one?

#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <errno.h>

int
main(int argc, char **argv)
{
  struct stat statbuf;

  if(argc != 2) {
    fprintf(stderr, "%s: usage: %s file\n", argv[0], argv[0]);
    exit(1);
  }

  if(stat(argv[1], &statbuf) != 0) {
    fprintf(stderr, "%s: can't stat file %s: %s\n", argv[0], argv[1],
	    strerror(errno));
    exit(1);
  }

  printf("%o\n", statbuf.st_mode & 07777);
  exit(0);
}

-- 
Marc Unangst                | Real men don't make backups.  Real men never
mju@mudos.ann-arbor.mi.us   | accidentally delete files that they're going
                            | to need later.
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Sed with shell variables
Originator: tchrist@pixel.convex.com
Date: Fri, 21 Aug 1992 13:46:56 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of stuart@siesoft.co.uk:
:rgasch@nl.oracle.com (Robert Gasch) writes:
:: Using sed to edit strings is usually a nice and practical
:: method of doing so. I you want to change a pattern you usually
:: say:
:: 	echo $something|sed 's/pattern1/pattern2/'
:: 
:: The problem I ran into is that I can't get shell variables to
:: work as arguments. When I type
:: 	echo $something|sed 's/$this_pattern_var/$that_pattern_var/'
:: 
:: sed throws up on me. I've tried various combinations of quotation
:: marks without success. Is there an easy way of doing this??
:: 
:
:echo "$something" | sed 's/'"$this_pattern_var"'/'"$that_pattern_var"'/'
:
:The double quotes around the shell variables are only
:needed if they contain any spaces (or tabs).

Untrue.

% set x='*' y='?'
% sed s/$x/$y/
s/: No such file or directory

This actually seems to work in a Bourne-shell, which tells 
me that there's a difference in when retokenization happens,
which was news to me.

Things like this drive people from either traditional shell
into rc or perl, where you have more control over this.

You also will have a problem if your pattern contains delimiters,
which is a bit of a hassle to work around.

Things like this drive people into perl, which doesn't have
that problem either.

Of course, you can do these things in a traditional shell.
But the variable quoting is a hassle, and the escaping of 
the regexp delims is a hassle.  

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

We should develop anti-satellite weapons because we could not have prevailed
without them in 'Red Storm Rising'.  --Vice President Dan Quayle
From: hymowitz@whatever.cs.jhu.edu (Hymie don't play that.)
Newsgroups: comp.unix.shell
Subject: an ugly shell script that i'd like to fix
Date: 19 Aug 92 01:15:02 GMT
Reply-To: hymowitz@cs.jhu.edu (Hymie don't play that.)
Organization: Creative Sensualities dept, Jacquie's House of Underwear

hello.  i've got a two-part shell script.  the main part is written
in /bin/sh.  i also have a small script, written in /bin/csh and run
via source, which calls the /bin/sh script and performs 2 setenv's.

question 1 is - can i pass parameters to the script if it's run with
source? 

question 2 - can i perform a setenv by running the script directly
without source, and keep the new values? 

question 3 - can i perform a setenv and keep the new values by running
the /bin/sh script directly?

question 4 - is it better, in this one instance, to write one script
in csh, source it, than have 2 scripts? i generally consider
''don't write scripts in csh'' to be as sacred as ''don't use goto in c.''

i believe the answer to all 3 questions is ''no.'' can anyone
prove me wrong? 

the scripts work correctly now, and i know that ''if it ain't broke, don't
fix it''... 

--hymie
hymowitz@cs.jhu.edu                                         hymie@jhuvms.bitnet
-------------------------------------------------------------------------------
It's the wimp.  KILL THE WIMP!!!!!
--Herman's Lust, to Intellect and Sensitivity, on Anxiety
-------------------------------------------------------------------------------