Can't change colors for Inspections Follow
I'm using RubyMine #472. Go into Settings -> Inspections -> Ruby ->
Unresolved Ruby reference (though the exact item doesn't appear to
matter). In the Options area click the settings box. On any of the
four built-in Severities (ERROR, WARNING, INFO, SERVER PROBLEM) there is
a button to "Edit Settings|Colors & Fonts". Clicking on that button
takes me to a blank screen in Settings.
I have spent quite a while trying to edit those colors because, on a
black background with white default text, they are completely
unreadable. As far as I can tell there isn't any place in the Settings
where those colors can be edited. None of the options under Settings ->
Editor -> Colors & Fonts seems to affect those Severities.
- Nate
Please sign in to leave a comment.
Hello Nate,
Thanks for your feedback, I suppose this setting hasn`t been ported yet from ItelliJ IDEA.
I`ve created an issue in our tracker: http://www.jetbrains.net/jira/browse/RUBY-2327
Feel free to vote or track progress on it.
Thanks,
Oleg
Hi Nate,
You can send us your corrected color scheme and if it's better than our current version we can replace bundled version with it.
Are you talking about my color scheme that is used with Inspections to
show errors, warnings, etc.? Because the ability to customize those
colors isn't exposed in the UI I haven't been able to customize them at
all. I attached a screen shot to the bug that Oleg created so you can
see the problem.
http://www.jetbrains.net/jira/secure/attachment/27410/Textisimpossibletoread%21.jpg
- Nate
Roman.Chernyatchik wrote:
As a temporary quick fix you can
1. Go to Settings -> Inspections -> Ruby -> Unresolved Ruby reference -> Options -> ...
2. Create your own severity type (press plus button), e.g. MY_WARNING
3. You can specify colors and fonts for you custom severity types
4. Choose you custom severity type for "Unresolved Ruby reference"
Or you can select "vibrantInk" color scheme. That scheme was created by Idea Ruby Plugin community and inspections highlighting is fixed there.