HDTenEightyP/NetNews huggingface dataset:
From: yoongc@syma.sussex.ac.uk (Yoong Hon Chong)
Newsgroups: comp.unix.shell
Subject: Re: Which Shell to Use ?
Keywords: shell tcsh ksh csh
Date: 13 Apr 92 12:50:31 GMT
Organization: University of Sussex

In article <1602@imec.UUCP>, kolks@imec.be (Tilman Kolks) writes:
> Hi everybody,
> 
> I am planning to use another shell than the Csh I am using right
> now on my apollo.
> I have as options:
> 	- Tcsh (version 6.01.00)
> 	- Ksh.
> 
> What I like about the Tcsh:
> - command line completion
> - fast ls-F
> - Emacs-like command editing.
> 
> The Ksh offers me (as far as I know)
> - Emacs-like command editing.
> 
> Questions:
> Is that everything I can get out of Ksh ?
> (so the Tcsh is superiour ?)
> Are there other shell-types of which I am not aware of, and
> are worth knowing about ??
> 

If you are thinking of Tcsh, do wait for the tcsh-6.02. It should be
coming out soon. It is much better than 6.01 as there is a new
programmable completion feature to suit your liking. I have tested out he beta
version and it is really mind blowing to see what it can do.

If you are thinking of Ksh, then you'd better buy a book on Korn Shell
by its author D J Korn. It is also a programmable shell but you do have
to refer to the book as it is quite different. However, it is good
experience to see Ksh behave.

Another shell which, I would recommend is Zsh2.1 (although a newer
version will be out soon). It has both features of Tcsh and Ksh. The
only drawback (my opinion...) is that it consume a lot of virtual
memory. 

>
> The point is that the although the Tcsh is good, it
> is NOT supported in my (Apollo) environment. When things get rough,
> I am all alone (sniff). The compilation of the Tcsh resulted in 
> a compilation error (fixed through the use of violance)
> and a whole lot of warnings, so I am not so sure of the result.
> In the end, I, of course, prefere a supported executable IFF it can offer
> me something as command-line completion etc.
> 

If you are realy considering support, I will suggest that you go for
Ksh (although you may miss features like command-line completion etc. in
which Tcsh & Zsh has :-( ). Ksh is not bad but one has to get use to.

Chris
--

-- 
===============================================================================
Chris Y H Chong - Comp.Sc. 		Internet: yoongc@central.susx.ac.uk
University Of Sussex				  yoongc@cogs.susx.ac.uk
United Kingdom					  yoongc@syma.susx.ac.uk
Newsgroups: comp.unix.shell
From: lezz@merlin.dev.cdx.mot.com (Lezz Giles)
Subject: Re: Sehll Script to C Translator
Reply-To: lezz@merlin.dev.cdx.mot.com (Lezz Giles)
Organization: Motorola Codex, Canton, MA
Date: Thu, 9 Apr 1992 17:28:06 GMT

In article <1992Apr9.013419.21077@ucsu.Colorado.EDU>, brandy@tramp.Colorado.EDU (BRANDAUER CARL M) writes:
|> I suggest that you use either the Bourne or Korn shell and forget about
|> translating to C.  C-shell is a notoriously poor programming language
|> (slow, missing many essentials etc., etc) and of you scripts involve
|> many calls to standard UNIX commands you won't buy much by translating
|> to C.
|> 
|> Try reading "Programming in the UNIX environment" be Kernighan and Pike.
|> 

Of course there is always perl, which gives the advantages of shell
programming (simple file manipulation, good string manipulation including
extensive pattern matching, etc.), UNIX programming (process handling,
pipes, sockets, etc) and high-level language programming (all the control
structures you could want, including recursive functions, etc., packages
with distinct namespaces, list processing).  The only excuse for not
writing any system scripts or simple (or complex!) utilities in perl is
if you haven't heard of it, and if you're reading this then you don't even
have that excuse.  It's free and it is easy to install on just
about any system.

Lezz "no signature" Giles
Newsgroups: comp.unix.shell
From: def2@engr.uark.edu (Don Faulkner)
Subject: Why doesn't this work (sh) and what's the (t)csh version?
Organization: University of Arkansas
Date: Thu, 16 Apr 1992 04:47:08 GMT

Ok, here's the scoop: I'm running screen and need to see at each login
if it's already running. I tried this:

scr = ps | grep -c screen
if ( $scr >= 2 ) then
   #screen is running (1 for screen, 1 for grep screen)
   #so ignore the rest
fi

What's the problem? I'm lost. BTW, I'm just a *little* unfamillar with 
shell programming, but this is the only way (it goes in either .cshrc 
or .login). Also, what do I need to do to get this sort of thing to work
under tcsh?

Furthermore, if screen is not running, I want to resume a detached
screen if one exists. If not, I want to start screen. If screen is running
do nothing. Here's a synopsis:

IF NOT screen_running DO:
   Attempt to resume screen
   if resume fails
      start screen
   endif
endif

alternatively,

if screen not running,
   if detached screen exists ;(check ~.screen/ ?)
      start it
   else
      start screen
   endif
endif

Any ideas would be *GREATLY* appreciated.

                                   Many thanks,
                                   Don Faulkner

-- 
*******************************************************************************
| Donald Faulkner         | Only on    // /\       _   _         __           |
| def2@engr.uark.edu      |           // /  \    |/ \_/ \   |   /  \    /\    |
| dfaulkne@uafhp.uark.edu |       \\ // /----\   |   |   |  |  |   _   /--\   |
| u7335@nes.nersc.gov     |        \X/ /      \  |   |   |  |   \__/  /    \  |
*******************************************************************************
Newsgroups: comp.unix.shell
From: gwilliam@crc.ac.uk (Gary Williams x3294)
Newsgroups: comp.unix.shell
Subject: Re: appending a single quote
Date: 9 Apr 92 15:09:47 GMT
Organization: MRC Human Genome Resource Centre

In article <1992Apr9.122221.5509@crc.ac.uk> gwilliam@crc.ac.uk (Gary Williams x3294) writes:

>I'm having trouble using sed to append a single quote ' to the end of a
>line. 

>The command should look something like this (commented for
>readability):

> alias | sed -e 's/\!/\\\!/g' \		# change all ! to \!
>	    -e 's/^/&alias /' \		# stick 'alias ' in front of the line
>	    -e "s/  /       \'/1" \	# change the first <TAB> to <TAB>'
>	    -e "s/$/\'/" \	# append a ' (** THIS DOESN'T WORK **)
> > file



I have a workaround. It is horrible, but much of shell programming is :-)

set dollar = '$'
alias | sed -e 's/\!/\\\!/g' \
	    -e 's/^/&alias /' \
	    -e "s/	/	\'/1" \
	    -e "s/$dollar/\'/" \
> file

Thanks to Mike Smith for the suggestion.



-- 
GARY WILLIAMS,  Computing Services Section,  Janet:       G.Williams@UK.AC.CRC
MRC-CRC & Human Genome Mapping Centre,       Internet:    G.Williams@CRC.AC.UK
Watford Rd, HARROW, Middx, HA1 3UJ, UK
Tel 081-869 3294   Fax 081-423 1275   
Newsgroups: comp.unix.shell
From: janantha@magnus.acs.ohio-state.edu (Jayanth N Anantharaman)
Subject: help with shell scripts (csh)
Organization: The Ohio State University
Distribution: usa
Date: Tue, 14 Apr 1992 18:30:47 GMT

I am trying to write a shell script in csh.  I found that aliases of
the "parent" shell are not passed on to the (sub)shell that executes
the script (I presume another shell is created).  Is there any way that
this information can be "read in" by the script?  Any gurus out there
who can help me?

-Jayanth
-jayanth@ee.eng.ohio-state.edu


Newsgroups: comp.unix.shell
From: merlyn@iWarp.intel.com (Randal L. Schwartz)
Subject: Re: sed - use with multiple files
Reply-To: merlyn@iWarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Date: Wed, 8 Apr 1992 03:08:54 GMT

In article <1992Apr8.022554.8516@unixland.natick.ma.us>, trw@unixland (Tim Weil) writes:
| I'm looking for a way to use sed with an editor (vi would be fine)
| to make global changes to a set of files in a subdirectory.  The
| use of sed isn't mandatory but the concept is to 
|       Open File
|       Make Global Change (sed or no sed)
|       Close File
|       Repeat for all files in directory

(He said the magic words: "sed isn't mandatory". :-)

perl -pi.bak -e 's/old/new/g' *

to change all of the files in the directory.

print "Just another Perl hacker,"
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Intel: putting the 'backward' in 'backward compatible'..."====/
From: brandy@tramp.Colorado.EDU (BRANDAUER CARL M)
Newsgroups: comp.unix.shell
Subject: Re: Sehll Script to C Translator
Date: 9 Apr 92 01:34:19 GMT
Article-I.D.: ucsu.1992Apr9.013419.21077
Organization: University of Colorado, Boulder

I suggest that you use either the Bourne or Korn shell and forget about
translating to C.  C-shell is a notoriously poor programming language
(slow, missing many essentials etc., etc) and of you scripts involve
many calls to standard UNIX commands you won't buy much by translating
to C.

Try reading "Programming in the UNIX environment" be Kernighan and Pike.
Newsgroups: comp.unix.shell
From: jik@athena.mit.edu (Jonathan I. Kamens)
Subject: Re: Extracting characters from a string.
Organization: Massachusetts Institute of Technology
Date: Thu, 9 Apr 1992 21:40:50 GMT

In article <1992Apr8.221355.21685@ngala001.nt.com> galpf01@ngala005.NT.COM (pat finnerty) writes:

   I am attempting to write a script which will rename files. I need to be able
   extract characters from a string in order to do this. 
     For example, if I have a file with name of "abcdef" how could I strip off the
   first 2 characters for use later in the script. Should I use awk? If so, how?

There are a plethora of UNIX utilities that can do what you describe;
a brief perusal of available documentation for any of them would
probably give you enough information to figure out how to do it, and
it would be a learning experience as well.

Here are some examples:

% expr abcdef : '^\(..\)'
ab
% echo abcdef | sed 's/^\(..\).*/\1/'
ab
% echo abcdef | awk '{print substr($0, 1, 2)}'
ab
% echo abcdef | colrm 3
ab
% 

The first three are almost completely portable; "colrm" may not exist
on some systems, and I've omitted an example using "cut" because my
system doesn't have it.  You could also, of course, use "perl," but
that's probably overkill :-).

If you have decimal numbers indicating the position in the string that
you want to extract, then awk is the easiest to use, since it takes
numerical arguments.  Without more information about what you're doing
exactly, it's hard to make a precise determination of which utility
would be best for you.

What exactly is the shell script you're writing for?  I have a
sneaking suspicion that it's probably already been done....

-- 
Jonathan Kamens						jik@MIT.Edu
MIT Information Systems/Athena		    Moderator, news.answers
    (Send correspondence related to the news.answers newsgroup
	{and ONLY correspondence related to the newsgroup}
		 to news-answers-request@MIT.Edu.)
From: pbecker@bert.East.Sun.COM (Paul Becker, ACE - Answer Center East)
Newsgroups: comp.unix.shell
Subject: CSH - alias;
Keywords: csh alias set ;
Date: 8 Apr 92 18:07:55 GMT
Reply-To: pbecker@bert.East.Sun.COM
Organization: Sun Microsystems
NNTP-Posting-Host: bert.east.sun.com


	Is this a "csh" bug or feature. Why does a variable take affect
on the same command line, but an alias does not.

	(also in tcsh 6.00.03)

Script started on Wed Apr  8 11:45:49 1992
example> 
example> 
example> alias s pwd ; s
s: Command not found.
example> s
/home/bert/pbecker
example> set paul = becker ; echo $paul
becker
example> set paul = nothing ; echo $paul
nothing
example> setenv PAUL BECKER; echo $PAUL
BECKER
example> setenv PAUL NOTHING; echo $PAUL
NOTHING


--Thank you

---
Paul Becker       - Sun Microsystems           -      paul.becker@East.Sun.COM 
~~~~~~~~~~~       - Andover, Massachusetts     -      508-794-5252      x25252
From: krs@uts.amdahl.com (Kris Stephens [Hail Eris!])
Newsgroups: comp.unix.shell
Subject: Re: sed - use with multiple files
Date: 8 Apr 92 17:13:00 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Apr8.030516.2467@umbc3.umbc.edu> rouben@math9.math.umbc.edu (Rouben Rostamian) writes:
>In article <1992Apr8.022554.8516@unixland.natick.ma.us> trw@unixland.natick.ma.us (Tim Weil) writes:
>>I'm looking for a way to use sed with an editor (vi would be fine)
>>to make global changes to a set of files in a subdirectory. 
>>Can this be done with shell programming?
>
>This can be done in most shells.  The particular sequence of commands
>depends on the shell.   With sh you can do:
>
>for filename in *
>do
>[your sed command here applied to the file $filename]
>done

Be careful about how you handle edit-in-place operations, though....

	:
	# sh or ksh example
	temp=temp.$$		# Use $$ here, not inside the loop.
	for file in *		# ...or whatever your file-selection is.
	do
		if sed	-e 's/old/new/g'	\
			-e 's/Old/New/g'	\
			$file > $temp
		then
			mv -f $temp $file
		else
			echo "$0: sed returned $? on file '$file' 1>&2
			rm -f $temp
		fi
	done

The reason to reference $$ outside the loop (assigning it to the temp file
name and *not* using temp.$$ within the loop) is that based on how you set
up the loop (for or while) and the specific shell, $$ may change value in
the loop.  So if you get errors, you may spin off a residual temp file for
each bad pass through the loop.  Reusing the same temp file over and over
avoids that possibility and keeps things neater.

...Kris
-- 
Kristopher Stephens, | (408-746-6047) | krs@uts.amdahl.com | KC6DFS
Amdahl Corporation   |                |                    |
     [The opinions expressed above are mine, solely, and do not    ]
     [necessarily reflect the opinions or policies of Amdahl Corp. ]
Newsgroups: comp.unix.shell
From: errant@polari.com
Subject: File Access Counts
Summary: Need a Shell towards this end
Keywords: File Access Counts
Organization: Seattle Online Public Access Unix.  (206) 328-4944 (all lines telebit-equipped)
Date: Tue, 14 Apr 1992 13:03:20 GMT

Need a script for counting the number of accesses to a given file
during the day.  File will be accessed numerous times a minute.
Bourne format prefered.
Thanks in advance!
From: spencer@shade.Princeton.EDU (S. Spencer Sun)
Newsgroups: comp.unix.shell
Subject: Re: File Access Counts
Keywords: File Access Counts
Date: 15 Apr 92 01:05:09 GMT
Organization: Princeton Univ. Class of '94
Originator: news@ernie.Princeton.EDU

In article <1992Apr14.130320.6029@polari.com> errant@polari.com writes:
>Need a script for counting the number of accesses to a given file
>during the day.  File will be accessed numerous times a minute.
>Bourne format prefered.

I seriously doubt you could do this from a shell script.  In fact, I'd
bet it can't be done at all... seems to me something like this would
have to be embedded in the OS.
----------
Spencer Sun - Princeton Univ. Class of '94 - Dept. of Computer Science
Clockwork Orange (Princeton Ultimate) (when I bother to show up for practice)
Playing bridge is like having sex.  You don't need a partner if you
have a good hand.
From: subbarao@phoenix.Princeton.EDU (Kartik Subbarao)
Newsgroups: comp.unix.shell
Subject: Re: appending a single quote
Date: 9 Apr 92 15:27:36 GMT
Organization: putchar('I'); for (i = 0; i < 3; i++) putchar('E');

In article <1992Apr9.122221.5509@crc.ac.uk> gwilliam@crc.ac.uk (Gary Williams x3294) writes:

>alias cmd	'do things \!*'
>
>It is obvious why the offending sed command doesn't work - but can
>anyone see a way to work around the problem?

Hmm. Here is something that does what you basically want:

% alias | perl -ne 's/\\!/\\\!/g; $_ =~ "(.*)	(.*)$";  \
  print "alias $1 '\''$2'\''\n"'

(note: is a TAB character between the (.*) and the (.*)$ in the regexp).

But this doesn't handle quotes inside of an alias though...

	-Kartik
From: krs@uts.amdahl.com (Kris Stephens [Hail Eris!])
Newsgroups: comp.unix.shell
Subject: Re: appending a single quote
Date: 9 Apr 92 18:50:17 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Apr9.122221.5509@crc.ac.uk> gwilliam@crc.ac.uk (Gary Williams x3294) writes:
>
>I'm having trouble using sed to append a single quote ' to the end of a
>line. 
>
>The actual problem I'm trying to solve is to create a file containg csh
>alias commands that can later be sourced to set up the current aliases
>again.  The command should look something like this (commented for
>readability):
>
>alias | sed -e 's/\!/\\\!/g' \		# change all ! to \!
>	    -e 's/^/&alias /' \		# stick 'alias ' in front of the line
>	    -e "s/  /       \'/1" \	# change the first <TAB> to <TAB>'
>	    -e "s/$/\'/" \	# append a ' (** THIS DOESN'T WORK **)
>> file
>
>This is intended to change a line produced by 'alias' like:
>
>cmd	do things !*
>
>into:
>
>alias cmd	'do things \!*'
>
>It is obvious why the offending sed command doesn't work - but can
>anyone see a way to work around the problem?

You're on the right track, but had the escape (\) in the wrong place
in the last edit instruction.  Escape the $, not the ', like:

--
alias |

#
# change all ! to \!
# stick 'alias ' in front of the line
# change the first <TAB> to <TAB>'
# append a '
#
sed	-e 's/\!/\\\!/g'	\
	-e 's/^/alias /'	\
	-e "s/	/	'/"	\
	-e "s/\$/'/"		\
	> file
--

Inside double-quotes, a single-quote is a normal character but a dollar-sign
isn't, so it needs to be escaped.  I assume that the comments on each line
(after the lagging "\") were informational only -- really put them in like
that and the \ only escapes the white-space in front of the comment.

By the way, on my csh, the first instruction can be simplified to

	-e 's/!/\\!/g'

because, again, inside single-quotes, ! has no special meaning.  Further
simplification leads to:

--
alias |

#
# quote the string following the first <TAB>
# change all ! to \!
# stick 'alias ' in front of the line
#
sed	-e "s/	\(.*\)/	'\1'/"	\
	-e 's/!/\\!/g'		\
	-e 's/^/alias /'	\
	> file
--

I would also do the append last so the pattern-matching on earlier edits
doesn't have to read past the extra characters.

...Kris
-- 
Kristopher Stephens, | (408-746-6047) | krs@uts.amdahl.com | KC6DFS
Amdahl Corporation   |                |                    |
     [The opinions expressed above are mine, solely, and do not    ]
     [necessarily reflect the opinions or policies of Amdahl Corp. ]
Newsgroups: comp.unix.shell
From: jch+@cs.cmu.edu (Jonathan Hardwick)
Subject: Re: How does one compare strings in zsh?
Date: Tue, 07 Apr 92 12:51:28 GMT
Organization: School of Computer Science, Carnegie Mellon

zubin@dworkin.wustl.edu (Zubin Dittia) writes:
> The only difference between the two compiles was that I had used 
> "gcc -traditional" the first time, and "cc" the second. Apparently, zsh 
> misbehaves when compiled with gcc.

Counter-example: zsh runs fine on a DECstation 2100 when compiled with
V2.0 gcc -traditional -O2.  It also gets a 10% size reduction over zsh
compiled with ultrix cc -O3.  What machine and version of gcc are you
using? 

Jonathan H.

ObShell : implementing Mach's setpath(1) as a single zsh function.
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Wanted:  Generate sequential file names
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Tue, 14 Apr 1992 17:35:05 GMT
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 root@candle.uucp (Bruce Momjian):
:Does anyone have a nifty bourne shell script which turns filenames like: 
:
:	fred003	 	into 	fred004
:	barney06	into	barney07
:
:and so forth?  It should work for a variable number of zeros.  I want to
:use this for keeping log files.

    #!/bin/sh
    perl -e 'print ++$ARGV[0]' $1
or 
    #!/bin/sh
    perl -e 'for (@ARGV) { print ++$_, "\n"; }' $*
or 
    #!/usr/bin/perl
    for (@ARGV) { print ++$_, "\n"; } 

The trick here is that perl ++ works on alphanumerics.  Otherwise
you can probably use expr to parse it out and bump the numeric
part, but that's harder to write.

--tom
From: ath@jds.incom.de (Andreas Thiedecke)
Newsgroups: comp.unix.shell
Subject: How can I get the ksh88 for sun ??
Keywords: ksh88
Date: 9 Apr 92 23:10:59 GMT
Organization: JDS Sommer GmbH, Frankfurt am Main, Germany

I know the pdksh but I need the full functions
of the ksh88. I can also pay for it.

Thank you in advance,
Andreas

-- 
Name:     Andreas Thiedecke
Company:  JDS Sommer GmbH * Telephon: +49 69 593200 * FAX: +49 69 553089
Address:  D-6000 Frankfurt am Main, Jahnstr. 49 (Germany)
E-Mail:   ath@jds.in.sub.org * ath@jds.uucp
-- 
Name:     Andreas Thiedecke
Company:  JDS Sommer GmbH * Telephon: +49 69 593200 * FAX: +49 69 553089
Address:  D-6000 Frankfurt am Main, Jahnstr. 49 (Germany)
E-Mail:   ath@jds.in.sub.org * ath@jds.uucp
From: pd@x.co.uk (Paul Davey)
Newsgroups: comp.unix.shell
Subject: Re: Having stty command in .cshrc for xterm.
Date: 9 Apr 92 17:03:32 GMT
	<JIK.92Apr7112951@pit-manager.mit.edu>
Organization: IXI Ltd.


When using xterm you don't need stty. 

You can use the ttyModes resource of xterm to avoid the overhead of
the stty. 

Example: place this in ~/.Xdefaults (or use with xrdb etc)

	!
	XTerm*ttyModes: erase ^? intr ^c kill ^u  susp ^z dsusp ^y  eof ^d \
			flush ^o eof ^d rprnt ^r quit ^|  weras ^w
	!

On some platforms some modes are not supported, this is my work around
for hpux.

	!
	! weras ^w doesn't work on HP (the xterm exits!)
	! so use xterm -name hpux to look up the following resource
	!
	hpux*ttyModes: erase ^? intr ^c kill ^u  susp ^z dsusp ^y  eof ^d


Of course since I don't _always_ log on in an xterm I have something
like the following in my .login

if ( $?prompt && $TERM != xterm ) then
	# this is executed only when in an interactive shell 
	# and not in an xterm
	/bin/stty erase '^?'  intr '^C'  kill '^U'
endif

--
 Regards,			  pd@x.co.uk           IXI Ltd.
	Paul Davey		  pd@ixi.uucp          62-74 Burleigh St.
				  ...!uunet!ixi!pd     Cambridge,  U.K.
 "These are interesting times"    +44 223 462 131      CB1  1OJ
From: pjc@donuts0.uucp (Paul J. Capista)
Newsgroups: comp.unix.shell
Subject: ksh History file '?'
Date: 10 Apr 92 19:32:58 GMT
Reply-To: pjc@donuts0.uucp (Paul J. Capista)
Distribution: na
Organization: Bellcore, Piscataway, NJ

I have a couple of questions regarding the ksh  history file.
I am running on an AMDAHL 5090 under UTS 2.1.2 (SVR3+).  My
first question is why can i vi, cat, sed and ...? my history file,
but when i grep on a string that i know exists in the file it
never matches?

My second question is why can't i reexecute commands that
are towards the beginning of my history file.  For example,
HISTSIZE=1024 and lets say i have 300 lines in my history file,
i might only be able to reexecute commands 90 - 300.  Although,
commands 1-89 are still in the history file, i can't ESC and
search on the strings, however, if i do know the command number
i can reexecute them via "fc -e".

Any help would be greatly appreciated.

------------------------------------------------------------------------
Paul Capista

UUCP: bellcore!pyuxf!pjc
INTERNET: pjc%pyuxf@bellcore.com
Newsgroups: comp.unix.shell