Why are strings in my code no longer highlighted in red in TOAD 9.1?
From the TOADBeta list, answer supplied by Norm. I just upgraded to Beta 9.1.0.62 and the highlighting for strings stopped working. Instead of red they show up in black. View→Options→Editor→Behaviour Click pl/sql and then the Edit button. On the highlighting tab, check what’s set for STRING. That should be what you get, however, there seems to be a slight anomaly in the beta upgrade path of late, so click on the parser tab. In my Beta 56 there’s a load of stuff and near the bottom of the list of categories there’s a STRING 1 and a STRING 2. I do not have STRING here, but others have had. Ok, do this next : If you have it, highlight STRING and DELETE it. If you don’t have it, panic not. Select STRING 1 (should be above STRING 2) and see what it says on the right for Token type and default highlighting – both should say STRING. Ditto for STRING 2. I suspect your token type or default highlighting is set to NONE, so the parser parses out a string and sees that you don’t want it to be high
Related Questions
- When searching for a word in the source code (using the "find" field), the required word appears highlighted in red or in pink. Is there a code of color for the highlighting?
- I understand that you play with Red Code 1.30 strings. Have you tired the Kirschbaum Pro Line II 1.30 or do you have to play Tecnifibre?
- Why are strings in my code no longer highlighted in red in TOAD 9.1?
