HDTenEightyP/NetNews huggingface dataset:
From: jdell@nefertiti.mit.edu (John Ellithorpe)
Newsgroups: comp.unix.shell
Subject: Re: How can I rm a file with a '&' ????
Date: 15 Aug 92 03:53:25 GMT
Organization: Massachusetts Institute of Technology

On Fri, 14 Aug 92 22:03:04 GMT, nummer_5@obh.in-berlin.de (Christian Wierzbicki) said:

> Can anybody answer this question... Please be quick cos this file is about
> 3 megs of size...

I'm using tcsh 6.02, and I can just put single quotes, like

% rm '&it'

and it works fine.

-John

--

===============================================================================
John Ellithorpe                           | Internet: jdell@maggie.mit.edu  
Dept. of Physics, Rm 26-349               | Phone   : (617) 253-3074  Office
Massachusetts Institute of Technology     |           (617) 253-3072  Lab   
Cambridge, MA  02139                      |           (617) 236-4910  Home  
===============================================================================
From: kenj@yarra.pyramid.com.au (Ken McDonell)
Newsgroups: comp.unix.shell
Subject: Re: Sed with shell variables
Date: 20 Aug 92 23:09:34 GMT
Organization: Pyramid Technology Corp PL, Melb., Australia

ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig) writes:

>rgasch@nl.oracle.com (Robert Gasch) writes:

>>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 -e s/$this_pattern/$that_pattern/

It is generally safer to use something like ...

    echo "$something" | sed -e "s/$this_pattern/$that_pattern/"

unless you can be certain that the variables something, this_pattern and
that_pattern
	- do not contain white space, and
	- do not contain meta characters (e.g. * [ ?)

Of course, if this_pattern and/or that_pattern contain the character /
then one needs to resort to something even more obtuse!
-- 
Ken McDonell			  E-mail:     kenj@pyramid.com
Systems Technology Laboratory		      kenj@yarra.pyramid.com.au
Pyramid Technology Corporation	  Phone:      +61 3 521 3799
Melbourne, Australia		  Disclaimer: I speak for me alone, of course.
From: bernard@sirius.gte.com (Bernard Silver)
Newsgroups: comp.unix.shell
Subject: Re: How to make tcsh the login shell w/0 bothering operator? !FAQ
Date: 12 Aug 92 14:56:04 GMT
Organization: GTE Laboratories Incorporated
In-reply-to: scotth@felix.filenet.com's message of 11 Aug 92 16:48:06 GMT

In article <19451@fritz.filenet.com> scotth@felix.filenet.com (Scott Hopson) writes:

   In article <28267@option.GBA.NYU.EDU> jcao@option.GBA.NYU.EDU (Jingbin Cao) writes:
   >	I do know, though, that someone on my machine can do exactly
   >what I want. I haven't asked him because I don't know him. Can someone
   >on the netland please enlighten me?

   AS for changing your shell try 'chsh' change shell, it's in the man pages also.

   Example: chsh /What_Ever_Directory_it's_in/tcsh

   If you were using Borne Shell (sh) and wanted to change to 'C' Shell (csh) 
   you would type: chsh /bin/csh

As others have indicated, on many systems, you can only chsh to a
shell listed in /etc/shells (if the file doesn't exist, only csh and
sh can be used).  SunOS at least also requires the users shell to be
in /etc/shells for ftp to work.

--
				Bernard Silver
				GTE Laboratories
				bsilver@gte.com
				(617) 466-2663
Newsgroups: comp.unix.shell
From: warner@redding.etdesg.trw.com (Jeff Warner)
Subject: Re: How to make tcsh the login shell w/0 bothering operator? !FAQ
Organization: TRW, Inc., Redondo Beach...
Date: 17 Aug 92 14:42:39

In article <Bsr2Jy.oD@news.cso.uiuc.edu> tinsel@uiuc.edu (Thomas Aaron Insel) writes:

   > I built the tcsh myself and can have it run by typing "tcsh" in a csh
   > (the login shell). Now, I want to make tcsh the default login shell,
   > BUT do it without bothering the system operator. Trust me, I've done
   > some homework, read the faq and fine-manual, but I can't find an
   > answer.

heres what I do.  I placed the following code in the top of my .cshrc;
since the .cshrc is read first, before the .login.  Place at top of
the .cshrc because starting tcsh will be faster.

#
# Start up tcsh if it is not already running, it exists, and this
# is an interactive shell.  This should be on initial login only;
# thus, start tcsh as a login shell.  We cannot start tcsh, or any
# shell as a login shell because we would need to set argv[0]=(-tcsh)
# So instead, source the .login, then execute tcsh..  Oops -l starts
# tcsh as login shell
#
set tcshpath = ~kelly/bin4/tcsh
set host = `hostname`

if ($host != triton && $host != moshpit) then     # temp cluge for old OS
if ($?prompt != 0 && -x $tcshpath && $shell != $tcshpath) then
  #
  # Spawn tcsh next time Leave this last
  #
  setenv SHELL $tcshpath
  set shell=$tcshpath
#  source ~/.login
  exec $tcshpath -l
endif
endif



J Warner
Newsgroups: comp.unix.shell
From: digdon@ug.cs.dal.ca (Mike Digdon)
Subject: Re: How can I rm a file with a '&' ????
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Date: Sat, 15 Aug 1992 14:25:58 GMT

In article <S025H1G@obh.in-berlin.de> nummer_5@obh.in-berlin.de (Christian Wierzbicki) writes:
>Can anybody answer this question... Please be quick cos this file is about
>3 megs of size...
>
>Ciao...
>    nummer_5@obh.in-berlin.de
>
>

Easy.. if the filename is test& then simply use:

	rm test\&

In any case, just put a backslash before the & (or any metacharacter)..

-- 
	     Mike Digdon - Vice Prez DSCSS - Dalhousie University
		     digdon@ug.cs.dal.ca  -- Halifax, NS
	 	 - Real programmers never work nine to five -
From: nagel@Cigna.COM (Mark Nagel)
Newsgroups: comp.unix.shell
Subject: Re: unwinding $variables in csh
Keywords: resolve, unwind $variables, csh
Date: 12 Aug 92 23:04:38 GMT
Organization: CIGNA FIRST, Irvine, CA

In <1992Aug9.194325.1476@sol.UVic.CA> stilley@csr.UVic.CA (Scott  Tilley) writes:

>What is the easiest way to completely resolve variables in csh? I have
>several variables that are made up of other $variables. I do not
>want them expanded until the end of the script, so I use

>	set var1 = '$HOME'
>	set var2 = '$var1/dir'

>for example. At the end of the script I need to propagate var2 to the
>environment, such as

>	setenv DIR $var2

>but this produces "$DIR = $HOME/dir", i.e., $HOME does not
>get expanded. How can I get csh to fully expand all variables
>in one shot?

Try using eval:

#! /bin/csh -f

set var1 = '$HOME'
set var2 = '$var1/dir'
echo "var1 = $var1"
echo "var2 = $var2"
setenv DIR $var2
echo "DIR = $DIR"
eval setenv DIR $var2
echo "eval'ed DIR = $DIR"
eval eval setenv DIR $var2
echo "eval'ed eval'ed DIR = $DIR"
-- 
Mark Nagel <nagel@cigna.com>	| DISCLAIMER: Any resemblence of these
Network Administrator		| opinions to those of CIGNA are purely
CIGNA/FIRST			| coincidental.
          (Don't start vast projects with half-vast ideas)
Newsgroups: comp.unix.shell
From: tporczyk@novell.com (Tony Porczyk)
Subject: Re: csh echo newlines
Organization: Novell, Inc.
Distribution: na
Date: Wed, 19 Aug 1992 04:19:37 GMT

wb8foz@skybridge.SCL.CWRU.Edu (David Lesher) writes:

>How do I get a csh echo statement to output a newline?
>All the book examples talk about supressing them. I want one!

echo ""


t.
From: jerry@incc.com (Jerry Rocteur)
Newsgroups: comp.unix.shell
Subject: Re: Octal chmod status
Summary: perl ignorance ...
Date: 19 Aug 92 20:50:56 GMT
Organization: InCC.com Perwez Belgium

In article <1992Aug19.130558.8488@news.eng.convex.com>, tchrist@convex.COM (Tom Christiansen) writes:
> From the keyboard of mju@mudos.ann-arbor.mi.us (Marc Unangst):
> :In article <1992Aug18.181609.8988@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
> :>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)'
> :
> :Hmm.  Huge a.out, huh?  Overly large foo.c, huh?  Hmm.
> :
> :mju@mudos:~$ ls -l getperms getperms.c
> :-rwxr-xr-x   1 mju      group       4780 Aug 19 01:06 getperms
> :-rw-r--r--   1 mju      group        445 Aug 15 01:08 getperms.c
> [deleted .......]
> Sure, the C solution does run faster: one one-hundredth of a second
> faster.  Big deal.  That infinitesimal time difference is surely not
> [deleted ......]
> --tom

Why is this person continually annoying people with information about perl ??? 

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 ?? 

I work on Pyramid, SCO, AT&T 3B2, Ultrix, Sun and I have not seen perl
on any of these machines, now these companies may be wrong for not
supplying what seems to be a great product, but it is not on the
popular systems and I subscribe to comp.unix.shell.

If perl *is* a shell, then I apologize, but if perl *is* a shell why
is this person doing 'perl -e .......' ????

Just looking for information......
-- 
 __^__                                                              __^__
( ___ )------------------------------------------------------------( ___ )
 | / | Jerry Rocteur                         Email: jerry@InCC.COM  | \ |
 | / | Independent Computer Consultants  Division de DELRA s.p.r.l  | \ |
 |___|                 Perwez Belgique Europe                       |___|
(_____)------------------------------------------------------------(_____)
   ^                                                                  ^
From: gsa@alcor.concordia.ca ( CON U GRADUATE STUDENTS' ASSOC )
Newsgroups: comp.unix.shell
Subject: Re: If shell command switches.
Date: 17 Aug 92 17:19:24 GMT
Distribution: comp.unix.shell
Organization: Concordia University, Montreal, Quebec

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.
Newsgroups: comp.unix.shell
From: wittig@gmd.de (Georg Wittig)
Subject: Re: csh: escaping "{" and "}" in command substitution
Organization: GMD, Sankt Augustin, Germany
Date: Wed, 12 Aug 1992 11:36:34 GMT

In <1992Aug11.202955.24144@afterlife.ncsc.mil> ahw@afterlife.ncsc.mil (Andrew White) writes:

>foreach name ( names )
>	awk '$1 == /$name/ { print $3 }' somefile
>end

	What about the following:

	foreach name ( names )
		awk '$1 == /'$name'/ { print $3 }' somefile
	end
--
Georg Wittig                  GMD-I8.IT                                         Schloss Birlinghoven          P. O. Box 1316                                    D-W-5205 Sankt Augustin 1     Germany
email: Georg.Wittig@gmd.de    telephone: (+49) 2241 14-2294
 ------------------------------------------------------------------------------
"In the beginning was the word, but it wasn't a fixed number of bits."
Newsgroups: comp.unix.shell
From: thomson@zarda.macc.wisc.edu (Don Thomson)
Subject: Exit status of command executed by rsh
Organization: University of Wisconsin Academic Computing Center
Date: 20 Aug 92 07:37:55

I'm executing commands on a remote machine using rsh in a Bourne shell script
and then want to test the exit status of the remote command.  Of course, after
the rsh, the exit status is that of the rsh executed on my machine rather than
the command executed on the remote machine.  Is there a particularly
slick/elegant way to pass back and test the exit status from the remote
machine?
--
 
----- Don Thomson ----- MACC, 1210 W. Dayton, Madison, WI  53706 -------------
    (608) 262-0138      thomson@macc.wisc.edu / thomson@wiscmacc.bitnet
Newsgroups: comp.unix.shell,comp.sys.hp
From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
Subject: Re: ksh bk-gnd behaviour
Organization: University of Toronto Chemistry Department
Date: Wed, 19 Aug 1992 00:11:30 GMT

In article <891@marvin.jpl.oz> tony@marvin.jpl.oz (Tony Sanderson) writes:
>
> With ksh (HP-UX on a new '720), I find that scripts which successfully
>used either the "[ -t 0 ]" or "tty" commands on our old system to detect
>that the script has been backgrounded no longer work.  I'm told (by HP)
>that this is a result of the job control feature (which is absent in the
>ksh on our older machines),  causing stdin to remain attached to the user
>terminal when a script is backgrounded.

I just posted our solution to this last week; the real solution is
for HP to fix 'stty' and friends so they don't hang your script when
they are in the background (BSD fixed this years ago). Anyways, here it is
again (.kshrc is read for each ksh via the ENV variable):

#
# Prompt generator - keep track whether prompt was already set,
# since that is used to determine whether the shell is "interactive"
# or not.
#
if [ "$LEVEL" = "" ]; then
   let "LEVEL = 0"
fi
if [ "$PS1" != "" -a "$LEVEL" = "0" ]; then
   interactive=yes
else
   interactive=no
fi
host=`hostname`
PS1=${host}:'${PWD}# '
export PS1
let "LEVEL = $LEVEL + 1"
export LEVEL
...
#
# Do some terminal dependent stuff.
#
if [ "$interactive" = "yes" ]; then
   stty -tabs erase ^H kill ^U intr ^C susp ^Z dsusp ^Y tostop ixon ixoff
fi
-- 
What are the chances that any computer system will ever "work" properly?
... and Slim just left town. -*- Mike Peterson, SysAdmin, U/Toronto Chemistry
Newsgroups: comp.unix.shell
From: fitzgb@mml0.meche.rpi.edu (Brian Fitzgerald)
Subject: Re: challenge: hex sort
Organization: Rensselaer Polytechnic Institute, Troy, NY
Date: Thu, 13 Aug 1992 13:46:28 GMT

Wow!  That didn't take long!

Thanks to:
ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig)
mfg@castle.ed.ac.uk (Michael Gordon)

for their awk solutions.

Brian
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: csh commands
Originator: tchrist@pixel.convex.com
Date: Tue, 18 Aug 1992 16:34:21 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Keywords: commands csh read file
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 cld@gmhgate.gmh.edu (Charles D'Englere):
:I have been working on a project that requires that I use the csh shell
:to work with the exsiting program. I have a few questions: 1 - Is there
:a way to parse the command line using either pipes '|' or newlines - 
:example
:
:ncs% cat $homedir/$1 |
:
:If I do this with a RETURN I get a "Invaild null command."
:
:2 - I need a routine to replace the following Bourne shell routine
:
:cat $homedir/$1 | while read EADDR IPADDR SW_VER
:
:to  a csh shell equivalent.

Your constraint of using csh dooms you to immense frustratation if you're
lucky, and most likely to failure as well.

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

	    "AT&T -- anything better is illegal."
		  -- Keith Lofstrom, comp.unix.bsd, "AT&T sues BSDI" thread
Xref: sparky comp.unix.shell:3515 comp.sys.hp:9407
From: tony@marvin.jpl.oz (Tony Sanderson)
Newsgroups: comp.unix.shell,comp.sys.hp
Subject: ksh bk-gnd behaviour
Date: 19 Aug 92 07:21:13 GMT
Reply-To: tony@marvin.jpl.oz (Tony Sanderson)
Distribution: world
Organization: Boral Elevators, Melbourne


 With ksh (HP-UX on a new '720), I find that scripts which successfully
used either the "[ -t 0 ]" or "tty" commands on our old system to detect
that the script has been backgrounded no longer work.  I'm told (by HP)
that this is a result of the job control feature (which is absent in the
ksh on our older machines),  causing stdin to remain attached to the user
terminal when a script is backgrounded.  Suggestion was to insert a !sh
command at the top of every script to ensure processing by the bourne
shell.  I suppose I could do that,  but it seems like a pretty pathetic
"solution" to me (esp as we don't use job control around here anyway!).

 They suggested I read "The Korn Shell" by Dave Korn - I've just flicked
thru that for an hour or so,  but I'm none the wiser!  Have I just found
a major deficiency or limitation of ksh,  or is this an HP implementation
quirk? I find it difficult to believe that there's no simple way for a
script to tell that it's running in the background! (Incidentally,  both
tests work fine where the script gets installed in a pipe.)

 A test script (for anyone who may be interested) using the aforementioned
commands is as follows:

----------------------------- snip 'ere ---------------------------------
#  Test for foreground v/s background execution of this script, and its
#  ability to detect same.
#  To simplify things (with stdout blocking or whatever),  writes result
#  to file "yy":

echo 'Result via "test -t 0", method (a): \c' > yy

if [ -t 0 ]
then
        echo "Terminal attached" >> yy
else
        echo "Terminal not attached" >> yy
fi

echo 'Result via output of tty command, method (b): \c' >> yy

if [ "`tty`" = "not a tty" ]
then
        echo "Terminal not attached" >> yy
else
        echo "Terminal attached" >> yy
fi

# End
----------------------------- and 'ere too ------------------------------

Any suggestions?

PS: had a look thru the FAQ's for ...unix.shell about a month ago and saw
no reference to it there,  hence the post.

PS 2: Just in case anyone reading this did answer another recent post re
methods for an efficient 16 bit integer divide-by-5 method (which I'm
looking for), we just lost the last 2 weeks news around here as a result
a disc crash - so could u re-post!

-----------------------------------------------------------------------------

Tony Sanderson		Boral Elevators, Melbourne, Australia
			e-mail tony@marvin.jpl.oz.au

-----------------------------------------------------------------------------
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Octal chmod status
Originator: tchrist@pixel.convex.com
Date: Wed, 19 Aug 1992 14:30:59 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 messina@netcom.com (Tony Porczyk):
:Tom Christiansen <tchrist@convex.COM> responds to Marc Unangst:
:
:>Big deal.  That infinitesimal time difference is surely not
:>worth all the hassle of writing a C program for each and every little
:
:Even though I agree that the perl solution was fine (by being so
:small), but I do not understand the bruhaha about the "hassle" of
:writing a C program for small tasks.  It is often much simpler and
:*faster* to write the C code than to implement other solutions.  At
:least it is much more *readable* than the aformentioned perl script... 

Fine, if you want me to optimize for legibility, I'll do that.

    require 'stat.pl';
    @sb = stat($ARGV[0]);
    printf("%04o\n", $sb[$ST_MODE]);

The bruhaha stems from having to install a hundred binaries on a hundred
systems spanning a dozen different architectures.  Programs that aren't
self-contained are a major hassle.  

For this reason, I'd much rather see an embedded here-is document used
than an auxiliary data file, and I'd much rather see a solution calling
sed, awk, or perl than one requiring dedicated C programs.  

In many cases (of which this is a prime example) by the time you've
written your C program, I'll be long done with the perl version, and will
have probably finished a couple other programs as well.

Putting your interpreted programs in a commonly-mounted directory is a
major win in convenience as well as in disk space.

--tom

-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
"I sincerely hope that the future does not mean we must continually restrict
 ourselves to the tools that were available 10 years ago."
	Mark Bush in comp.unix.wizards <4235@inca.comlab.ox.ac.uk>
Newsgroups: comp.unix.shell
From: glaze@cs.mu.oz.au (Glaze)
Subject: Re: Escaping brackets in csh - SUMMARY
Organization: Computer Science, University of Melbourne, Australia
Date: Thu, 13 Aug 1992 23:38:13 GMT

hall@beta.lanl.gov (Michael L. Hall) writes:
>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>:

[...delete area...]
>This is my csh solution - 'do it with 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

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:

#! /bin/sh
# simulate a "mkdir -p"
parent()
{
	if test \! -d $1 ; then
	    parent `dirname $1` 
	    mkdir `echo $1 | sed 's@/$@@'`
	fi
}
usage()
{
	echo "mkdirp: Usage: mkdirp dirname"
	exit 1
}
if test $# -ne 1 ; then
    usage
else
    parent $1
fi
exit 0
From: jerry@incc.com (Jerry Rocteur)
Newsgroups: comp.unix.shell
Subject: Re: searching for 1st occurrence
Summary: awk, sed, ed
Date: 17 Aug 92 17:25:59 GMT
Organization: InCC.com Perwez Belgium

In article <1992Aug17.001516.29088@news.acns.nwu.edu>, navarra@casbah.acns.nwu.edu (John Navarra) writes:
> In article <MITCH.92Aug16153742@mira.clsi> mitch@clsi (Mitchell N. Perilstein) writes:
> >
> >You can just skip the grep and do it in one step:
> >
> >    awk '/SS2/ {print; exit}' < systems
> >
> 
> or, you can just skip awk and do it in sed:
> 
>     sed -n '/123/{p;q;}' filename
> 
or, you can just skip sed and do it in ed:

	echo /123|ed filename

This is very silly and could go on for a while.
-- 
 __^__                                                              __^__
( ___ )------------------------------------------------------------( ___ )
 | / | Jerry Rocteur                       Email: jerry@InCC.COM    | \ |
 | / |             Independent Computer Consultants                 | \ |
 | / | Phone +32.2.235.7045  +32.81.65.53.58    fax +32.81.65.70.20 | \ |
 | / |--------------------------------------------------------------| \ |
 |___|                It's beyond my control.                       |___|
(_____)------------------------------------------------------------(_____)
   ^                                                                  ^
Newsgroups: comp.unix.shell
Subject: Re: Sed with shell variables
From: ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig)
Date: Thu, 20 Aug 1992 10:57:37 GMT
Organization: University of Auckland, New Zealand.

rgasch@nl.oracle.com (Robert Gasch) writes:

>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 -e s/$this_pattern/$that_pattern/
-- 
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