2008/12/3 Matt Wozniski <[EMAIL PROTECTED]>:
>
> On Wed, Dec 3, 2008 at 3:44 AM, Fredrik Gustafsson wrote:
>>
>> Hi,
>> I'm having problem with setting the font. In the end of this mail you
>> can se my vim version. Using the gtk-gnome-gui and trying to set the
>> font in my .vimrc like this:
>> set guifont=clean:12
>> vim do not find my font clean and sets it to size 12. Using
>> set guifont=clean\ 12
>> it all works fine. This is not the way it should be according to
>> documentation (:he guifont) that states that a ":" should work instead of
>> "\ ".
>
> I see nothing that says that at :help 'guifont' ... In :help
> 'guifont', I see only 12 lines that contain a colon:
>
>        |option-backslash|.  For example: >
>            :set guifont=Screen15,\ 7x13,font\\,with\\,commas
>        For Win32, GTK, Mac OS and Photon: >
>            :set guifont=*
>        For the GTK+ 2 GUI the font name looks like this: >
>            :set guifont=Andale\ Mono\ 11
>        For Mac OSX you can use something like this: >
>            :set guifont=Monaco:h10
>        width).  An exception is GTK 2: all fonts are accepted, but
>        - takes these options in the font name:
>                cXX - character set XX.  Valid charsets are: ANSI, ARABIC,
>          Use a ':' to separate the options.
>        - Examples: >
>            :set guifont=courier_new:h12:w5:b:cRUSSIAN
>            :set guifont=Andale_Mono:h7.5:w4.5
>
> As far as I can see, colons are only valid for separating font options
> from the font name, and that's only supported on OS X and Win32...  Do
> you see something different?

Thank you for your answear. There was a few things in the help that cleary
confused me. After getting some help and explanations by the kind people in
[EMAIL PROTECTED] I've localized the "errors":

* The guifont arguments are different on different platforms (I was told that
  this is because of different font implementations, I think vim should have one
  way to set its fonts and there after translate it to the platform standard.
  The other people at #vim did not. I'm not completely shure about why yet, but
  I guess they are right and I'm wrong in this matter.
* The bullet list and the overall indentation makes it unclear where the WIN32
  stuff ends and the general stuff continues. This is also not a bug but a
  misreading by me.

Med vänliga hälsningar
iveqy

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui