HDTenEightyP/NetNews huggingface dataset:
From: dkeisen@leland.Stanford.EDU (Dave Eisen)
Subject: Re: difference between set and setenv?
Organization: Sequoia Peripherals, Inc.
Date: Fri, 22 Jan 93 17:27:45 GMT

In article <1993Jan22.105255.3991@newsserver.rrzn.uni-hannover.de> zzsb@kursix.rrzn.uni-hannover.de (Wolfgang Sander-Beuermann) writes:
>
>   set ...  defines variables within your current shell (only)
>
>   setenv ..defines global variables (i.e. the subshells will know them)
>

Not just subshells. Any program you run will know them as well. 
Use set for things the shell needs to know about and setenv for
things like PATH, MAIL, TERM, and VISUAL that programs you invoke
need to know about.



-- 
Dave Eisen                               Sequoia Peripherals: (415) 967-5644
dkeisen@leland.Stanford.EDU              Home:                (415) 321-5154
       There's something in my library to offend everybody. 
          --- Washington Coalition Against Censorship
Newsgroups: comp.unix.shell
From: lwv26@cas.org (Larry W. Virden)
Subject: Re: Problem with ksh read built-in parsing
Followup-To: comp.unix.shell
Reply-To: lvirden@cas.org (Larry W. Virden)
Organization: Nedriv Software and Shoe Shiners, Uninc.
Date: Fri, 22 Jan 1993 13:14:08 GMT

I have encountered strange interactions in functions where I attempted to
save off IFS and then restore it later.  I ended up using the practice
- which works for me in the sort term - of undefining IFS when I got
done inside of shell programs which needed to parse IFS.   This isn't
a great solution, but for some reason, certain programs would cease
working if I did something like:

OIFS="$IFS"
IFS=:$IFS

do work

IFS="$OIFS"

return


-- 
Larry W. Virden                 UUCP: osu-cis!chemabs!lvirden
Same Mbox: BITNET: lvirden@cas  INET: lvirden@cas.org
Personal: 674 Falls Place,   Reynoldsburg, OH 43068-1614
Newsgroups: comp.unix.shell
From: wacren@lri.fr (Laurent WACRENIER)
Subject: Re: Setting enviroment variables in a shell script
Keywords: environment variables shell script
Organization: Laboratoire de Recherche en Informatique
Date: Mon, 25 Jan 1993 00:32:13 GMT


In article <35774@sales.GBA.NYU.EDU>, elouie@sales.GBA.NYU.EDU (Euge) writes:
|> How do you set an environment variable in a C-Shell script?  I tried
|> setenv enviroment_variable value, but as soon as the script finishes, 
|> the value of the varialbe is reset to its original value.  My guess is 
|> that another "process" is created during the run of the script and
|> when the script 
|> is done, that process is killed.
|> Is there a way to set environment variables in a shell script? 
|> Thanks.

The way i know is to use shell script and the eval buildin . For example:

The shell script:

cat >script
#!/bin/csh
...
setenv VARIABLE VALUE
...
echo setenv VARIABLE $VARIABLE

^D

when you type

	% script

it returns

	setenv VARIABLE VALUE

to set the environemnt variable, do

	eval `script`
From: uwe@mpi-sb.mpg.de (Uwe Waldmann)
Newsgroups: comp.unix.shell
Subject: Re: how to distinguish set command
Date: 25 Jan 93 18:02:20 GMT
Reply-To: uwe@mpi-sb.mpg.de
Organization: Max-Planck-Institut fuer Informatik

In article <1993Jan23.132103.1@vax1.umkc.edu>, srinivasan@vax1.umkc.edu writes:
> 	I am trying to use the set command in a shell programm file
> and to my surprise it shows a list of all current shell variables 
> instead of assigning the output of the command that i have given
> in the back quote. Can someone kindly explain how i can take care 
> of this.

The set command of the Bourne shell has three purposes.  If no arguments
are given, it prints the values of all current shell variables.
If the first argument(s) start with '-', it sets the options of the shell.
The remaining arguments are assigned to the positional parameters
$1, $2, and so on.

If you write

  set `somecmd somearg`

to assign the output of somecmd to the positional parameters, two problems
may occur.  First, the output may start with '-', such that the shell
interprets it as an option.  You can use

  set -- `somecmd somearg`

to avoid this problem.  Second, the output of somecmd may be empty (or
consist of whitespace characters only).  In this case you have two
possibilities:  Either use

  set -- "`somecmd somearg`"

which assigns the whole output of somecmd to the first positional parameter
$1 (including the surrounding whitespace).  Alternatively, you can use
a dummy 'xxx' (so that 'set' has always at least one argument) and shift
it away afterwards.  The command

  set xxx `somecmd somearg`
  shift

splits the output of somecmd into words and assigns them, in order,
to $1, $2, and so on (even if the output is empty).  I assume that this
is what you want.

-- 
Uwe Waldmann, Max-Planck-Institut fuer Informatik
Im Stadtwald, D-W6600 Saarbruecken 1, Germany
Phone: +49 681 302-5431, Fax: +49 681 302-5401, E-Mail: uwe@mpi-sb.mpg.de
Newsgroups: comp.unix.shell
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Re: >& redirects stderr AND stdout.
Organization: Computer Science, University of Melbourne, Australia
Date: Sun, 24 Jan 1993 11:56:03 GMT

aet@mullian.ee.mu.OZ.AU (bert thompson) writes:

>hi!
>
>i would like to know if there is a way to redirect ONLY stderr
>rather than both stderr and stdout in csh (or in sh).

It's not possible in csh.
In sh, do
	command 2>errs

>one other question:
>
>how would i write a shell script which writes some text to the
>stdin of a program and then hands stdin over to the user (tty).

Do something like this, in sh:

	{
	   echo "some text"
	   echo "some more text"
	   cat   # hand stdin over to the user
	} | program

You can do something roughly similar in csh, but sh is a much better
language for writing scripts in.

>many thanks and sorry if these are FAQs,

Apology accepted :-)

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
Newsgroups: comp.unix.shell
From: davisre@sage.cc.purdue.edu (Robert Davis)
Subject: Re: multiple sub's with 'sed'
Organization: Purdue University Computing Center
Date: Sun, 24 Jan 1993 02:50:08 GMT

In article <1jsl5oINN4da@shelley.u.washington.edu> adrian@stein.u.washington.edu (Adrian Mariano) writes:
>
>I think Ultrix is just like everyone else.  To clear things up, here's
>the sed man page section on 'w'.  This is from the Ultrix 4.2 manual,
>but the Dynix manual is very similar:
>
>     (2)w wfile
>             Write.  Append the pattern space to wfile.
>
>The use of "append" is somewhat misleading.  The actual behavior is to
>overwrite the file that existed before the sed invocation, and then
>append thereafter within the same sed program.  

	Exactly.  I thought you were saying that w always appended,
even to a file that existed before sed was invoked.  I guess I was
vague as well.


Rob
-- 
| Robert Davis                                    davis@sonata.cc.purdue.edu
| "Look up, Hannah.  Look up."                            NeXT Mail accepted
--
Newsgroups: comp.unix.shell
From: Steinar.Haug@delab.sintef.no (Steinar Haug)
Subject: Re: Where to get tcsh for SPARC
Organization: SINTEF DELAB, Trondheim, Norway.
Date: Sat, 23 Jan 1993 17:22:42 GMT

wacren@lri.fr (Laurent WACRENIER) writes:
>   You can get the 6.02.00 version in the anonymous ftp server lri.lri.fr
> in the 
> /pub directory. You can also read the FAQ to find other sites

Um, I would definitely recommend you to get the latest version, which is
tcsh-6.03. You can pick it up from the original source, tesla.ee.cornell.edu,
directory pub/tcsh, or from a number of archive sites (try archie).

Steinar Haug, system/networks administrator
SINTEF DELAB, University of Trondheim, NORWAY
Email: Steinar.Haug@delab.sintef.no, 
	sthaug@idt.unit.no, steinar@tosca.er.sintef.no
From: sanjay@eng.umd.edu (Kumarasamy Sanjay)
Newsgroups: comp.unix.shell
Subject: wwb
Date: 26 Jan 1993 22:23:34 GMT
Organization: College of Engineering, Maryversity von Uniland, College Park
Distribution: world
NNTP-Posting-Host: valkyrie.eng.umd.edu
Keywords: Text processing
Originator: sanjay@valkyrie.eng.umd.edu


 Does anybody know whether wwb (Writers Work Bench), a text processing
tool, is available in the public domain?. 

Tanx a million.

Have fun

-sanjay
________________________________________________________________________
Sanjay Kumarasamy                |   
sanjay@eng.umd.edu               |                       
yajnas@wam.umd.edu               |    Thou art That
Voice:(H)301-345-0628            |
......(O)301-405-6872            |
------------------------------------------------------------------------
From: hartman@informix.com (Robert Hartman)
Newsgroups: comp.unix.shell
Subject: Re: multiple sub's with 'sed'
Date: 22 Jan 93 18:33:34 GMT
Organization: Informix Software, Inc.

In article <19891@mindlink.bc.ca> Ian_Staines@mindlink.bc.ca (Ian Staines) writes:
>
>How can I get 'sed' to do multiple substitutions?  I would like to replace
>certain words in a text file with bold type.  I have tried the following:
>
>for WORD in ${LIST}
>do
>        BOLD="${bold}${WORD}${unbold}"
>        sed "/s/${WORD}/${BOLD}/gw ${FILE}" ${FILE}
>done
>
>The shell appears to keep ${FILE} intact within the script, and does not
>updated it with each loop.  I only get the last substitution, not the entire
>list.
>
>Is there a way to loop within sed?

I'm not quite sure why you have the ${FILE} within quotes.  Also, I
don't know what the "w" is for after at the end of your substitution
command; I've never used it.  You're only getting the last substitution
because you aren't writing the earlier ones out to file.  This might
work better:

    cat /dev/null > /tmp/sedscript.$USER

    for WORD in ${LIST}
    do
	    BOLD="${bold}${WORD}${unbold}"
	    echo "s/${WORD}/${BOLD}/g" >> /tmp/sedscript.$USER
    done
    sed -f /tmp/sedscript.$USER ${FILE} > ${FILE}.sed


This shell script fragment builds a sed script that includes all of the
substitutions you want to make.  It then applies the sed script to
the file and saves the output in a file with the .sed suffix.  It
doesn't get rid of the sed script because you might want it around
for debugging purposes.  However, it does overwrite any previous sed script
created by you to avoid accumulating files in /tmp.

-r
Newsgroups: comp.unix.shell
From: fan1321@cs.cuhk.hk (George Fan )
Subject: Re: Problem with ksh read built-in parsing
Keywords: ksh, read, parsing
Organization: Faculty of Engineering, The Chinese U. of Hong Kong
Date: Thu, 21 Jan 1993 13:20:49 GMT

donp@mail.boi.hp.com (Don Peterson) writes:


>I am using ksh on HPUX 8.0 and I've run into a feature of the read
>command that makes my script run incorrectly.  

>So my question is:  Is there another command in ksh that simulates 
>the read command, but doesn't do the whitespace stripping and parsing 
>(if indicated).

>Here's what I mean.  I have the following line in my script:

>   read -u3 LINE

>(File descriptor 3 was opened earlier).

>Let's say the line I wanted to input was:

>"    This is a test line for the script."

>where the line does not include the quotes, but all spaces are important.

>What I get back when I use echo $LINE is:

      Please, Try   echo "$Line"  (i.e with the quote )

>This is a test line for the script.

>i.e., the leading spaces have been removed.  Is there a way to 
>avoid this and get the whole line printed?

>Please email responses to me at donp@hpbs1639.boi.hp.com and I'll
>post a summary if there are enough responses.

George Fan.
--
---------------
Email : fan1321@cs.cuhk.hk ( georgef@cuhk.hk )
Home Phone: (825)356-1084
    .------------------------------------------------.
From: ndl@unix.brighton.ac.uk (Nathan Lock)
Newsgroups: comp.unix.shell
Subject: padding things out
Date: 26 Jan 93 19:40:57 GMT
Organization: University of Brighton, UK

How can I take a variable length field 
(e.g the gecos field in the password file)
and pad it out in a shell script so that it is always the same length 
for the next field to line up. 
(with a tab I will not always get the same column, sometimes I need 1,
other times 2 for a shortname) how can I determine whether I need 1 or 2 
in a shell script?

e.g a single tab

Fred Bloggs 	next field
Joe Smith	next field
Samantha Smith-jones	next field
Sam Wheeler	next field

what I want to achieve:-

Fred Bloggs		next field
Joe Smith		next field
Samantha Smith-Jones	next field
Sam Wheeler		next field

Standard shell or awk solutions please as I do not have perl etc.

Awaiting you reply

Nathan Lock.
From: stephen@wstuart
Newsgroups: comp.unix.shell
Subject: Re: help with a script files
Date: 28 Jan 93 15:27:35 GMT
Reply-To: stuart@siesoft.co.uk
Organization: Siemens Nixdorf Information Systems Ltd.
X-Newsreader: Tin 1.1 PL4

rickt@aruba.UUCP (Rickey Thomas Tom) writes:
: I a working on a script that basicaly moves files from a subdirectory to
: a current directory.
: 
: The problem is that if there are no files in the subdirectory, the script
: terminates and returns an error code that says that no files were found.
: 
: I tried    if ( -e "<dir x>/* ) then
:                 .....
: 
: but this does not work either
: 

It appears that you are using csh for your scripts.

In my experience csh is harder to use, more bug-ridden
and less portable than sh and so recommend that you use
sh for your scripts.  (By all means use, as I do, csh
for an interactive shell.)

In sh, you can do exactly as you tried (obviously the
sytax is different):

    if test -f <dir x>/*
    then
	# there exist files in <dir x>
    else
	# there are no files in <dir x>
    fi

In csh, if you must:

    set nonomatch
    if ( -e <dir x>/* ) then
	# there exist files
    else
	# there don't
    endif
 
    Note: 1. this still fails if <dir x> doesn't exist
	  2. "-e <dir x>/*" returns true for both directories
	     and files


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 -
Xref: sparky comp.unix.shell:5446 news.answers:5363
From: bnb@ukc.ac.uk (B.N.Blackmore)
Newsgroups: comp.unix.shell
Subject: Re: padding things out
Date: 27 Jan 93 18:00:27 GMT
Reply-To: bnb@ukc.ac.uk (The Impossible Dreamer)
Organization: Computing Lab, University of Kent at Canterbury, UK.

In article <1993Jan26.194057.1884@unix.brighton.ac.uk> ndl@unix.brighton.ac.uk (Nathan Lock) writes:
:How can I take a variable length field 
:(e.g the gecos field in the password file)
:and pad it out in a shell script so that it is always the same length 
:for the next field to line up. 
:(with a tab I will not always get the same column, sometimes I need 1,
:other times 2 for a shortname) how can I determine whether I need 1 or 2 
:in a shell script?

Try this for size it should do what you require (I hope)

#!/bin/sh
# A shell script to nicely format a file which is TAB seperated
# By Brian Blackmore
if test $# != 1 
then
	echo Usage: $0 file
fi
# Pass one to find out the length of the largest line
maxlength=0
# Note this is a TAB below		The @ avoid splitting spaces
for a in "`sed 's/	.*//' < $*|tr ' ' '@'`"
do
	thislength="`echo $a|wc -c|sed 's/ //g'`"
	if test $thislength -gt $maxlength
	then
		maxlength=$thislength
	fi
done
# Pass two print out the lines
awk -F'	' "{printf (\"%-${maxlength}s %s\\n\", \$1, \$2)}" < $*
# Note the File seperator is a TAB
--
Brian Blackmore, Darwin College,
The University of Kent at Canterbury, United Kingdom.
Newsgroups: comp.unix.shell
From: katzung@i88.isc.com (Brian Katzung)
Subject: Re: Is there a "foreach" loop control in ksh?
Organization: Interactive Systems Corporation, Naperville, IL
Date: Fri, 22 Jan 1993 17:37:54 GMT

In article <1304@alsys1.aecom.yu.edu> manaster@yu1.yu.edu (Chaim Manaster) writes:
|I want to do a series of comands on each file in the current
|directory, with some sort of "foreach" construct that will loop
|over every file in some list (something like in perl), or in some
|cases every file in the current directory. How would one do this in
|ksh?

For every file except, regardless of type, try:

	for file in `find . -print -prune`
	do
		...
	done

For regular files, use:

	for file in `find ..?* .[!.]* * -prune -type f -print 2> /dev/null`
	do
		...
	done

You can also use the one above without the "-type f" if you want
all types of files, but don't want ./ in front of each one.  Just
omit the "." patterns if they are excessive for your needs.

|In particular, I want to run compress on each file in the directory
|that does not already end in a .Z

	find ..?* .[!.]* * -prune ! -type f -name '*.Z' -print 2> /dev/null |
	xargs compress

|(dito for uncompress in
|reverse).

	find ..?* .[!.]* * -prune -type f -name '*.Z' -print 2> /dev/null |
	xargs uncompress

There is nothing ksh-specific here BTW, so these should work in sh just
as well.

  -- Brian Katzung  katzung@i88.isc.com
Newsgroups: comp.unix.shell
From: sivesh@rebels.b23b.ingr.com (sivesh pradhaan)
Subject: How to use find to traverse links
Reply-To: sivesh@rebels.b23b.ingr.com
Organization: Intergraph Corp. (Huntsville, Al.)
Date: Thu, 21 Jan 1993 21:55:11 GMT

Hi netters,

I am trying to use find to list files in a dir. and its sub dirs. But find does
not list the files in a sub dir. which is a link. Does any one know of a way to
accomplish this?

FYI I am using SYSV flavored unix.

Please e-mail your responses to me. 
Thanx.

-Sivesh
sivesh@rebels.b23b.ingr.com
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.shell
Subject: Re: Problem with sh-commands from a Makefile
Date: 22 Jan 93 23:04:03 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1993Jan20.211940.18612@odin.diku.dk>, turin@diku.dk (S|ren Turin) writes:

| all	:
| 	(for dir in $(DIRS) ; do cd ${dir} ; make VARS=$(VARS) ; done)


I think two things here, first you probably need $${dir} to delay
expansion, and second you want the () arond the cd, resulting in:
  for dir in $(DIRS) ; do (cd $${dir} ; make VARS=$(VARS)) ; done
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: mick@muppet.bt.co.uk (Mick Burnell)
Newsgroups: comp.unix.shell
Subject: Re: Another sed question.
Date: 28 Jan 93 09:23:32 GMT
Reply-To: mick@muppet.bt.co.uk
Organization: British Telecom

In article 23339@nmsu.edu, jsz@scf.nmsu.edu (Henri De Valois) writes:
>
> I am trying to write a script,that would append to each EOL
> some string,say `blah'. but when I do "sed -e 's/^/blah/g' inputfile > outputfile"
> `blah' inserts at the begining of each line.
>


Try   sed -e 's/$/blah/g'


     ^    As the leftmost character, a caret (or circumflex) con-
          strains the RE to match the leftmost portion of a line.

     $    As the rightmost character, a  dollar  sign  constrains
          the RE to match the rightmost portion of a line.


Hope this helps,
		Mick.
From: ln_smr@pki-nbg.philips.de (Stephen Riehm)
Newsgroups: comp.unix.shell
Subject: Re: Problem with sh-commands from a Makefile
Date: 21 Jan 93 09:27:29 GMT
Reply-To: ln_smr@pki-nbg.philips.de

turin@diku.dk (S|ren Turin) writes:

>Hi netters.

>all	:
>	(for dir in $(DIRS) ; do cd ${dir} ; make VARS=$(VARS) ; done)

>sh), i assume that i am missing something obvious. But what? Having
>read man-pages for both `sh' and `make', the solution still eludes me.

almost obvious...

>I'd appreciate e-mail replys (to turin@freja.diku.dk) but will of
>course read comp.unix.shell to see if anything comes up.

good, this is a common problem so I'm posting, at least you read the
man pages (or at least you SAY you read the manpages.)

To access shell variables like $dir, you need to use $$dir from within
Makefiles. This is because Make expands $ first, and $$ expands to $
for the shell, so the shell would then see $dir (or ${dir} as you have
it)

catchya

--------------------------------------------------------------------
Stephen Riehm		   Configuration Management	      _-_|\ 
ln_smr@pki-nbg.philips.de  Philips Kommunikations Industrie  /     \
Work: +49 911 526 2975	   Nu"rnberg, Germany		     \_.-.!/
Fax:  +49 911 526 3678	   "I was there, now I am here!"          v 
"My company speaks another language, I CAN'T speak on its behalf"
PS: You may think I am joking, I can't speak the language that well so
		PLEASE DON'T REPLY IN GERMAN!
			 - thanks -
Newsgroups: comp.unix.shell
From: pan@us-es.sel.de (Pawel Nabe)
Subject: Re: padding things out
Organization: SEL-Alcatel LTS Dept. US/ES
Date: Thu, 28 Jan 93 08:38:29 GMT

In article <1993Jan27.175539.17114@bnr.ca>, webster@bnr.ca (Brent Webster) writes:
|> In article 1884@unix.brighton.ac.uk, ndl@unix.brighton.ac.uk (Nathan Lock) writes:
|> >How can I take a variable length field 
|> >(e.g the gecos field in the password file)
|> >and pad it out in a shell script so that it is always the same length 
|> >for the next field to line up. 
|> >(with a tab I will not always get the same column, sometimes I need 1,
|> >other times 2 for a shortname) how can I determine whether I need 1 or 2 
|> >in a shell script?
|> >
.....
|> Try awk  ie
|> % echo "biff stuff	junk"|awk -F"	" '{printf "%-30s %s\n",$1, $2}'

No, use buildin things of sh(1). This runs much faster than the awk(1) example.
   while :
         do
              case "${field}" in
                  ??????????*)
                        break;;
              esac
              field="${field} "
         done
Now ${field} is at least 10 charcters long (the '*' at the end of ?????????? avoids infinite loops).
The above loop should pad field with the right number of spaces to make it 10 characters long. You can get unexpected results if field already containted more than 10 chars or some funny chars like tabs or newlines,...
-- 

Pawel Nabe                                   PaN Super Sonic Software Service
Business: +49/711/821 71 786                 expert for hi tech & low budget
Private:  +49/30/6 22 52 46 or +49/30/6 22 51 93
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.unix.shell
Subject: Re: Is there a "foreach" loop control in ksh?
Date: 23 Jan 93 03:20:10 GMT
Organization: CWI, Amsterdam

In article <1993Jan22.173754.17016@i88.isc.com> katzung@i88.isc.com (Brian Katzung) writes:
 > |In particular, I want to run compress on each file in the directory
 > |that does not already end in a .Z
 > 
 > 	find ..?* .[!.]* * -prune ! -type f -name '*.Z' -print 2> /dev/null |
 > 	xargs compress
Better put the exclamation point before -name.
But I think this is a bit of overkill.
-- 
dik t. winter, cwi, kruislaan 413, 1098 sj  amsterdam, nederland
home: bovenover 215, 1025 jn  amsterdam, nederland; e-mail: dik@cwi.nl
From: adrian@stein.u.washington.edu (Adrian Mariano)
Newsgroups: comp.unix.shell
Subject: Re: multiple sub's with 'sed'
Date: 23 Jan 1993 17:29:42 GMT
Organization: University of Washington
NNTP-Posting-Host: stein.u.washington.edu

In <C19uz1.43t@mentor.cc.purdue.edu> davisre@sage.cc.purdue.edu (Robert Davis) writes:

>	sed's w command writes the pattern space to a file, creating
>the file if it does not exist, and *overwriting* it if it does.  You
>want it to *append* the pattern space to $FILE, but sed does not have
>an option for that.

This is false (at least for my version of sed under Ultrix 4.2).  As
documented in my man page and as revealed by actuals tests, the 'w'
command appends to the specified file.

When I tried writing with 'w' to the same file that I was reading from
I got an empty file.  




 
Newsgroups: comp.unix.shell
From: zzsb@kursix.rrzn.uni-hannover.de (Wolfgang Sander-Beuermann)
Subject: Re: difference between set and setenv?
Organization: RRZN
X-Newsreader: Tin 1.1 PL4
Date: Fri, 22 Jan 1993 10:52:55 GMT

Looking at your question, I'll assume, you work with csh (i.e. you can
see a % as (or within) your prompt); then it is as following:

   set ...  defines variables within your current shell (only)

   setenv ..defines global variables (i.e. the subshells will know them)


Wolfgang Sander-Beuermann             zzsb@kursix.rrzn.uni-hannover.de
Newsgroups: comp.unix.shell