![]() ![]() This means that text applications that use boldface as part of their "prettification" of source code can seriously screw up the major reason to use a monospaced font, which is the consistent spacing of characters from line to line.įor what it's worth, gvim appears to fall into the former category and renders Progg圜leanTT Bold at the same width as the normal face. Other applications (notably those using the native Win32 GDI string rendering routines) render the text by drawing each character at the offset left by the previous one. Some applications get this right and still render the text in a rigid matrix with each character in the correct position. This makes the boldface of Progg圜leanTT one pixel wider than the normal face. The problem with that is that when Windows is asked to render it bold, it will synthesize a bold face by "smearing" the font one pixel to the right. I have a problem with Progg圜leanTT, and it's this the font has no bold face. Set guifont=Progg圜leanTTSZBP:h12:cDEFAULT This gives nearly the same size as Notepad, and fits as much text. Working on a 1024x768 screen under Windows, I find Courier-New:h11 too big. Weight (50 = normal, 25 = light, 63 = semibold, 75 = bold, 87 = black) Style hint (what to do if requested family can't be found 5 = AnyStyle = default) The parameters are in the following order:įont family (in this example, "Courier New") So in that case one may use something like Internal spaces must, as always, be backslash-escaped. when has("gui_kde") is TRUE), there are several positional parameters separated by slashes. Start with this, change the "set" statements as needed, and put it in your vimrc. Here is a snippet of code that should work on all versions of gvim.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |