Re: finding unmatched quotes in shell scripts

2002-11-19 Thread Wes Peters
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

Re: finding unmatched quotes in shell scripts

2002-11-19 Thread Greg Black
Wes Peters wrote: | 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

Re: finding unmatched quotes in shell scripts

2002-11-18 Thread Wes Peters
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

Re: finding unmatched quotes in shell scripts

2002-11-18 Thread Chris Doherty
On Sun, Nov 17, 2002 at 05:57:20PM +1000, Greg Black said: 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

Re: finding unmatched quotes in shell scripts

2002-11-17 Thread Greg Black
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

Re: finding unmatched quotes in shell scripts

2002-11-17 Thread Doug Barton
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. In addition to the other excellent suggestions, I'd suggest using the syntax highlighting editor,

finding unmatched quotes in shell scripts

2002-11-16 Thread Lyndon Nerenberg
I'm at my Witt's End trying to fix an unterminated quoted string problem in a shell script. Do any of you have any debugging tools tucked away that might help with this? (sh -[xv] have already been tried.) Something that printed a parse tree of the script would do the trick, but I can't find

Re: finding unmatched quotes in shell scripts

2002-11-16 Thread René Scharfe
On Saturday 16 November 2002 19:52, Lyndon Nerenberg wrote: I'm at my Witt's End trying to fix an unterminated quoted string problem in a shell script. Do any of you have any debugging tools tucked away that might help with this? Try using an editor with syntax highlighting, e.g., Vim or

Re: finding unmatched quotes in shell scripts

2002-11-16 Thread Lyndon Nerenberg
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

Re: finding unmatched quotes in shell scripts

2002-11-16 Thread Terry Lambert
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 -