On Fri, 2003-02-21 at 03:53, Joey Kelly wrote:
> Or for that matter, "cat scriptname" or "more scriptname"
Well, yeah...
However, that doesn't do things like diskply env. var. expansions.
> Thou spake:
> >To debug a script try running "sh -v scriptname"
> >To see commands and comments or "sh -x scriptname"
> >To see the commands only.
> >
> >-----Original Message-----
> >From: owner-nolug@joeykelly.net [mailto:owner-nolug@joeykelly.net] On
> >Behalf Of Ron Johnson
> >Sent: Friday, February 21, 2003 6:05 AM
> >To: NOLUG ML
> >Subject: [Nolug] Viewing each command in a bash script
> >
> >Hi.
> >
> >Normally, if one runs a script, all that one sees is the output
> >from the programs, not any comments in the script, or the actual
> >commands.
> >
> >Is there any way to enable such viewing? I'd find it very useful
> >for debugging scripts.
> >
> >TIA,
> >Ron
-- +------------------------------------------------------------+ | Ron Johnson, Jr. Home: ron.l.johnson@cox.net | | Jefferson, LA USA http://members.cox.net/ ron.l.johnson | | | | "For me and windows it became a matter of easy to start | | with, and becoming increasingly difficult to be produc- | | tive as time went on, and if something went wrong very | | difficult to fix, compared to linux's large over head | | setting up and learning the system with ease of use and | | the increase in productivity becoming larger the longer I | | use the system." | | Rohan Nicholls , The Netherlands | +------------------------------------------------------------+ ___________________ Nolug mailing list nolug@nolug.orgReceived on 02/21/03
This archive was generated by hypermail 2.2.0 : 12/19/08 EST