"Charles K. Clarkson" <[EMAIL PROTECTED]> writes: > Harry Putnam <> wrote: > > : I've found over time that one or another of my editors will > : spot a missmatched syntax element with its syntax coloring. > : > : Either Emacs in cperl mode or vim always helps find something > : like this. > : > : This time I can find no lapse in the coloring, and taking the > : advice given I don't find it by hand. However I've sort of > : lost track of what all I may have edited today. But stepping > : thru the 433 lines I just don't see it. > > I use ultraedit32. It has a feature which finds the closing > bracket (or brace or parenthesis) by using the control-b shortcut. > I place the cursor before the block I'm testing and it highlights > all enclosing text. Perhaps your editor has a similar feature.
Yes, both emacs and vim can do that, however if one of those things is missing the color syntax will also indicate where because the colors go to all one color following the syntax error.. I'm not seeing that and so doubt that going thru with the closing item finder tools will find it either. However I did step thru with vim and like I suspected, it found nothing. Is there any trick way to make perl itself tell me where it is or at least ball park. Something better than the last line of the file. The error output tells me that perl has found a difference in the number of closing and opening items. Can I get finer resolution somehow? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
