thegooglecodearchive / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 1 forks source link

PyStudio systax error marking makes code impossible to read #186

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What Plugin does this relate to? What version of the Plugin?
PyStudio: 0.2

What steps will reproduce the problem?
1. Set up PyStudio to "Check for syntax errors on save."
2. Create syntax error in an open source file and save it.

What is the expected output? What do you see instead?
Expected: Line with error is rendered with different background and text colors.
Observed: Line with error is rendered with same background and text colors, 
making text impossible to read.

What version of Editra are you using? On what operating system?
Editra 0.6.48
Ubuntu Linux 10.10

Please provide any additional information below.
Screenshot of an example problematic line attached.

Original issue reported on code.google.com by mithatko...@gmail.com on 18 Jun 2011 at 11:21

Attachments:

GoogleCodeExporter commented 9 years ago
What syntax style highlighting scheme are you using?

The syntax error highlighting uses your syntax highlighting themes error_style 
to highlight the background. The scheme in your screenshot looks custom and 
that you may not have setup error_style so it is defaulting to black. This can 
be confirmed by checking the syntax highlighting editor dialog.

Original comment by CodyPrec...@gmail.com on 18 Jun 2011 at 3:06

GoogleCodeExporter commented 9 years ago
I am/was using the "Guepardo" theme that ships with Editra. Indeed, selecting 
"Default" highlighting fixes this. If I edit "Guepardo" using the Style Editor 
to provide a custom error_style foreground color (#FFD7D7 seems to work well), 
it fixes Guepardo's rendering as well. So I guess the bug report should be 
"Guepardo's error rendering makes code impossible to read."

Original comment by mithatko...@gmail.com on 18 Jun 2011 at 3:29

GoogleCodeExporter commented 9 years ago
Fixed in Editra for next release

Thanks

Original comment by CodyPrec...@gmail.com on 18 Jun 2011 at 4:27