Date: Tue, 19 Nov 2002 11:05:32 -0800 From: Wes Peters <wes@softweyr.com> To: Greg Black <gjb@gbch.net> Cc: Lyndon Nerenberg <lyndon@orthanc.ab.ca>, freebsd-hackers@freebsd.org Subject: Re: finding unmatched quotes in shell scripts Message-ID: <3DDA8B7C.9BA63DC8@softweyr.com> References: <200211170159.gAH1xCG1052133@orthanc.ab.ca> <nospam-1037519839.91122@bambi.gbch.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Black wrote: > > Lyndon Nerenberg wrote: > > | I've tried a number of syntax-colouring editors, to no avail. The quotes > | (single, double, and back) *are* balanced, according to everything I've > | thrown the script at. That's why I'm more interested in something that > | can actually parse Bourne shell syntax (quiet Terry - I *know* what > | you're going to say) and dump out what it thinks the parse tree looks > | like. The problem isn't with the quotes being unbalanced, it's something > | else that's making the shell ignore one (or more) of those quotes. > > Surely the simple thing is to put an exit statement in the > middle of the script and see which half has the problem? Move > the exit statement forwards or backwards in a binary search > until the problem leaps out and hits you in the face. Or simply set -x at the beginning of the script? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DDA8B7C.9BA63DC8>