(Javascript syntax highlighter) */ characters incorrectly read when inside a regular expression
Bug #465721 reported by
Jared Klingenberger
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GtkSourceView |
Fix Released
|
Low
|
|||
| gtksourceview2 (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: gedit
While editing Javascript in gedit, I find that I will sometimes have an asterisk at the end of a regular expression. In Javascript, regular expressions are begun and ended with a / (forward slash) instead of quotes. However, gedit identifies any regular expressions with an asterisk as the last letter as the incorrect end of a comment (*/) and highlights the two characters red.
For example, if I have the regular expression:
/\d*/
gedit will highlight the asterisk and forward slash red as if it were an end-comment marker.
| description: | updated |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #1 |
| affects: | gedit (Ubuntu) → gtksourceview2 (Ubuntu) |
| Changed in gtksourceview2 (Ubuntu): | |
| importance: | Undecided → Low |
| affects: | gtksourceview2 (Ubuntu) → gedit (Ubuntu) |
| affects: | gedit (Ubuntu) → gtksourceview2 (Ubuntu) |
| affects: | gtksourceview2 (Ubuntu) → gedit (Ubuntu) |
| affects: | gedit (Ubuntu) → gtksourceview2 (Ubuntu) |
| affects: | gtksourceview2 (Ubuntu) → gedit (Ubuntu) |
| affects: | gedit (Ubuntu) → gtksourceview2 (Ubuntu) |
Revision history for this message
| Jared Klingenberger (itsjareds) wrote | #2 |
Revision history for this message
| Pedro Villavicencio (pedro) wrote | #3 |
| Changed in gtksourceview2 (Ubuntu): | |
| assignee: | nobody → Ubuntu Desktop Bugs (desktop-bugs) |
| status: | New → Triaged |
| Changed in gtksourceview: | |
| status: | Unknown → New |
| Changed in gtksourceview: | |
| importance: | Unknown → Low |
| Changed in gtksourceview: | |
| status: | New → Fix Released |
To post a comment you must log in.
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/