On 5 June 2013 18:34, Ivan Kanakarakis <[email protected]> wrote: > On 5 June 2013 18:21, Ben Fritz <[email protected]> wrote: >> On Friday, May 24, 2013 12:10:18 PM UTC-5, c00kiemon5ter wrote: >>> >>> colorscheme molokai >>> set guifont=Cousine\ 10 >>> >>> (that's the whole ~/.gvimrc) >>> >>> Upon opening gvim I got this: http://i.imgur.com/FfZHYCR.png >>> >> >> I can't see anything like this on Windows. Setting my font to Cousine in my >> .vimrc works just fine. >> >> I got Cousine from: >> http://www.google.com/fonts#UsePlace:use/Collection:Cousine >> >> Is the same font you've found? >> > > I think I got it from fontsquirrel: > http://www.fontsquirrel.com/fonts/cousine >
Success :D Using the fonts from google it seems that everything is fine. > >>> >>> adding 'gui' before setting the guifont, so changing my ~/.gvimrc to >>> >>> colorscheme molokai >>> gui >>> set guifont=Cousine\ 10 >>> >>> fixed it, and gvim now loads the font and works great. >>> >>> So, could this be a bug ? >> >> So, the GUI actually needs to be running before setting the font works? >> That's not normal, it could be a bug. >> >> Can you reproduce it with no plugins or .vimrc or anything at all, except >> for setting the font? >> > > Yes, it is reproducible. > Removing ~/.gvimrc and having ~/.vimrc to only include > > set guifont=Cousine\ 10 > > I get the same result; less colourful: http://i.imgur.com/ptHM4NE.png > > >> As a nicer workaround you could use a GUIEnter autocmd to set the font. >> >>> >>> Let me note that if I change ~/.gvim to >>> >>> colorscheme molokai >>> set guifont=DejaVu\ Sans\ Mono\ 12 >>> >>> then it loads that font fine, no need for 'gui'. >>> >> >> Curiouser and curiouser! Have you found any other fonts that suffer this >> issue? I wonder if it is an anti-aliasing thing or something. I don't know >> how to check that. >> > > No; no other fonts that I've tried did this. > I attached the font files in case someone > is interested in trying with those files. > > I don't think bad or even horrible antialiasing > could cause that. It mostly looks like the > font file is not read correctly. > So, I guess it was the font files that were corrupted and not a bug. That's a good thing. > I will now try with the font files from google > > Thanks > > >> -- >> -- >> You received this message from the "vim_dev" maillist. >> Do not top-post! Type your reply below the text you are replying to. >> For more information, visit http://www.vim.org/maillist.php >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "vim_dev" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/vim_dev/uxS2HxmzdZc/unsubscribe?hl=en. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > > > -- > Ivan c00kiemon5ter Kanakarakis >:3 Thanks for all the help again -- Ivan c00kiemon5ter Kanakarakis >:3 -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
