ClosestStorm / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

"Monaco:h9" font is scrunched when using Core Text renderer #492

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Enable "Use Core Text Renderer" in the advanced preferences.
2. Open a new window, and type ':set guifont=Monaco:h9'.

What is the expected output? What do you see instead?

The text should be rendered as it is with the Core Text renderer disabled, as 
shown in attachment "core-text-disabled". Instead, it ends up scrunched 
horizontally, as shown in attachment "core-text-enabled".

What version of MacVim and OS X are you using (see "MacVim->About MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6
Intel")?

MacVim snapshot 72 on OS X 10.9.1.

Please provide any additional information below.

Original issue reported on code.google.com by arc...@gmail.com on 3 Jan 2014 at 4:48

Attachments:

GoogleCodeExporter commented 9 years ago
It is not true that the two renderers should look identical.  In some 
situations the default renderer is way too "loose" and I do not want to emulate 
that with the Core Text renderer.

Arguably in this case the CT renderer looks bad, but I can't code special cases 
for different font/size combinations.

You can adjust the width of glyphs by opening Terminal and entering

defaults write org.vim.MacVim MMCellWidthMultiplier 1.2

Then restart MacVim.  Fiddle with the value (1.2) until it suits you.  (This is 
documented under ":h macvim-prefs".)

Original comment by bjorn.winckler@gmail.com on 3 Jan 2014 at 1:46

GoogleCodeExporter commented 9 years ago
Thanks for telling me about the width multiplier, but other apps render Monaco 
9 correctly without twiddling with defaults; shouldn't MacVim as well? I don't 
expect the renderers to be exactly the same—I was only using the default 
renderer as an example of correct rendering of the font. 

Original comment by arc...@gmail.com on 3 Jan 2014 at 2:14