You need to log in before you can comment on or make changes to this bug.
I tend to switch editor schemes pretty frequently. Sometimes all I want is a smaller font to maximise the amount of visible code. Other times I want a bigger font because my eyes are straining after lengthy coding sessions. Some fonts, for example ProFont (http://www.tobiasjung.net/profont/) and Windows Courier New, really suck when anti-aliased. Most other fonts suck when they are NOT anti-aliased. Can we have the anti-aliasing option as part of the syntax coloring scheme instead of global for the whole editor? Thanks.
Ondro, could you please think about this? We would probably need to have this in Tools-Options -> Fonts & Colors -> Hightlights. Thanks
Highlights seem not to be a place where one would search for antialiasing. Logically, in the structure of current options, it belongs to the Font Chooser, but the problem is that there is a way to set a separate font for various syntax elements, whereas antialiasing needs to be done per editor basis (thanks to vstejskal for this info). However, none of our standard themes actually does set specific font. So, can the option be added to the font-chooser, but shared? I.e. if the option was turned off in the font-chooser for default font and then file-chooser for "comment" was opened, it would "remember" the state. I know this means somewhat obscuring the model from the user, but under normal circumstances it works as expected (Unless someone specifically tries to set different antialiasing for different syntax elements, and even then it is rather easy to understand what has happened). I'm not sure if this change actually can be done (possibly the font-chooser is the java one and cannot be tampered with?). If not, the only way to address this enhancement is probably the "Text Antialiasing" option in Tools-Options -> Fonts & Colors -> Highlights, but in that case, I would suggest not to address this at all because having difficult-to-discover feature/option is about the same as having this feature/option not at all, maybe worse (it is cluttering the UI). I also tried some "non-conceptual" changes such as adding the option directly to the syntax panel, but it does not seem to be the right approach considering majority of users are OK with anti-aliasing as it is.
*** Issue 144516 has been marked as a duplicate of this issue. ***
I believe an appropriate place for this would be Syntax tab directly or maybe Miscellaneous -> Appearance or perhaps Editor section somewhere. Add my vote.
