MySQL Bugs: #46905: Improper Color Coding in Script Editor when a Line begins with Whitespace

Bug #46905	Improper Color Coding in Script Editor when a Line begins with Whitespace
Submitted:	24 Aug 2009 23:18	Modified:	26 Aug 2009 5:57
Reporter:	Matthew Clower	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S5 (Performance)
Version:	1.2.12	OS:	MacOS (Leopard)
Assigned to:		CPU Architecture:	Any
Tags:	colorcoding, functions, keywords, whitespace

Description:
aethetics:

When the first character of a line is whitespace (e.g., a tab or space) the color-coding does not code the entire string--it misses the last letter.

NOTES:

- This only occurs when there is exactly one whitespace character at the beginning of the line.
- This applies to keywords, function, strings, comments, etc.  (if the last character is whitespace in a comment or string, i.e. a tab, line feed, or space, you will not "see" the issue even though it still occurs.
- This applies to any line anywhere in the file.

How to repeat:
Open an existing or create a new script in the Script Editor.

Enter a space or tab followed by any color codable keyword or function at the beginning of any line, e.g.,

 create table `table_name` ...

The issue should present itself as soon as the characters are typed since it codes dynamically

Suggested fix:
... seems like an off-by-one error.

Thank you for the bug report. Could you please attach a picture showing the behavior reported?. Thanks in advance.

Example Behavior

Attachment: Picture 7.png (image/png, text), 19.79 KiB.

Additionally, this is unique to the Mac OS X version, it works fine in Windows.  I'm certain that I selected OS X... but now it's listed as Windows *shrugs*

Sorry, but QB is NOT supported on Mac OS X (check http://www.mysql.com/support/supportedplatforms/tools.html), so there is no chance for this bug to be fixed.