Gerald Lai wrote:
On Mon, 15 May 2006, Donal wrote:

Now that my primary issue of getting Windows Explorer to use gvim to open .prg files has been fixed, I have 2 further issues. I will seperate them so they do not get confused...

My eyes are not what they once were, and I use a high-res monitor. I don't want to decrease my screen res as I am used to all the real estate I need to keep multiple things going at once :) but I need to increase the default font size for my program files in gvim. I need a line for _vimrc, I suppose, that will set the default font to Lucida Console and 14pt.

Select your font to your liking via Edit -> Select Font...

Once you're done, do

:echo &guifont

Copy what you see to set the option 'guifont' (see ":help 'guifont'").
It'd probably look something like

:set guifont=Lucida\ 14

(spaces are escaped with backslashes)

You can place this in your vimrc.

HTH.
--
Gerald


The hitch with the guifont option is that there are 4 mutually incompatible formats for it, and each build of gvim recognises only one of them. If you're not sure which format you need, or if you want to use your vimrc with more than one version of Vim (for instance on a dual-boot system, or with different flavors of X11 graphical interfaces, or even with Vim-for-Mac-classical and Vim-for-MacOsX+X11) you may want to use something like the following:

if has("gui_running")
if has("gui_gtk2")
set guifont=B&H\ LucidaTypewriter\ 14
elseif has("gui_kde")
set guifont=B&H\ LucidaTypewriter/14
elseif has("x11")
set guifont=*-lucidatypewriter-medium-r-normal-*-*-168-*-*-m-*-*
else
set guifont=Lucida_Console:h14:cDEFAULT
endif
endif

See my tip http://vim.sourceforge.net/tips/tip.php?tip_id=632 "Setting the font in the GUI" (including the user comments at bottom) for more info.

In addition to all the above, you may (or may not) want to consult an oculist and get a prescription for eyeglasses adapted to what your eyes are now ;-) -- or if the "ageing problem" is (as in my case) with your monitor rather than with your eyes, then a hardware upgrade might be the cure.


Best regards,
Tony.

Reply via email to