2167 looks great, thanks for the quick fix!
Does this mean that italics can be selectively turned off in grammars?(ie, I want to have all coments italicized, but annotations in comments are not italicized)
Does this mean that italics can be selectively turned off in grammars?
He's a tease isn't he
new rendering text is just not readable on mac os X Laptop / Screen, too thin, or I m getting too old. back to 2165
sbusso: there should be no visible differences. It'd be great if you could provide screenshots of 2166 vs earlier, as well as details of your system.
no_bold and no_italic just provide global control for turning off bold or italic rendering. For fine grained control, you'll need to edit the .tmTheme file (and possibly the .tmLanguage if the assigned scopes aren't flexible enough)
Hi the build 2167 on mac os x lion broke my theme. custom theme looks like this -
And when switched to mac classic theme, it looks like this -
Can you give details about your system?
I am having similar issues with thin text, not in the main text editing area but in the Go To Anything panel.
I'm on Mac Lion & the Soda Light theme..
Check this out:
intel macbook with 3gb ram.The issue is not clearly visible with dark theme. Look at the bottom search box in screenshot below.
Same issue here in 2166 on a Mac using Solarized (Light) color scheme and DejaVu Sans Mono font face.
But it seems to happen with all fonts and themes.
Just thought that I'd throw in the fact that on Windows 7 64bit, no problems
I have a rendering issue when selecting a text block and run 'Split into Lines' (ctrl+shift+L) after:
"font_face": "DejaVu Sans Mono",
startup, version: 2167 windows x64 channel: dev
For those OS X users experiencing issues, can you give this build a go (it has to be downloaded manually, and isn't yet available via auto update), and let me know if it's fixed. It'd also be helpful if you could check the console for the "using gamma" line and report the two numbers listed there.
Working fine for me now. Thanks for the super quick response.
the console showsusing gamma: 1 (err: 0)
The new build has fixed the issue. Thanks
I didn't check the previous build and didn't see the problems, but with this special build everything looks fine (using gamma: 1 (err: 0)).
everything looks fine
using gamma: 2 (err: 6.9282)
here are two screenshots of same file with the same config. I will try to give you information about system in another post. This happen whatever the theme, font family, font weight I choose. Current is default theme with lazy color scheme.
Thanks for the report. This bug will have to stay for a little bit though, until I'm able to get some other planning changes done