[opensuse] a good small font for developing with gvim?
Dear list I had been developing by open xterm, maximize it, run vim in it. The benefit is it happen to be more than 160 columns wide, allow me to split vertically to edit two related programs each at 80-column width. It has 3 problems: I. sometimes vim in xterm stop responding suddenly, and never coming back, reason unknown; II. my color schema doesn't work because xterm support limited number of colors III. I prefer gvim for its menu. I'd like to select a small font for gvim so that I can maximize vim window and use two 80-column window inside of it without xterm. That way I need a font at 6 pixel wide. I cannot found such a font. in xfontsel I select 6 for pxlsz and only two fonts are available: "clean" and "fixed", both are two small to be readable at 6 pixel (then what font xterm is using that is readable even at 6 pixel??) and both are not selectable in gvim's choose font dialog. Can someone recommend me a 6-pixel-wide readable font (like the one used by default in xterm) and usable in gvim? Thanks in advance! P.S. maybe the best solution is to run at 1280 px wide screen with 8-pixel font, which is 160 column wide, but yet what I need is 161 column wide because there is one column used as separator:( -- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Zhang Weiwu wrote:
Dear list
I had been developing by open xterm, maximize it, run vim in it. The benefit is it happen to be more than 160 columns wide, allow me to split vertically to edit two related programs each at 80-column width.
It has 3 problems: I. sometimes vim in xterm stop responding suddenly, and never coming back, reason unknown; II. my color schema doesn't work because xterm support limited number of colors III. I prefer gvim for its menu.
I'd like to select a small font for gvim so that I can maximize vim window and use two 80-column window inside of it without xterm. That way I need a font at 6 pixel wide. I cannot found such a font. in xfontsel I select 6 for pxlsz and only two fonts are available: "clean" and "fixed", both are two small to be readable at 6 pixel (then what font xterm is using that is readable even at 6 pixel??) and both are not selectable in gvim's choose font dialog.
Can someone recommend me a 6-pixel-wide readable font (like the one used by default in xterm) and usable in gvim? Thanks in advance!
P.S. maybe the best solution is to run at 1280 px wide screen with 8-pixel font, which is 160 column wide, but yet what I need is 161 column wide because there is one column used as separator:(
Have you looked at gvim, the x11 version of vi? -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-07-05 at 20:15 -0700, Joseph Loo wrote:
Zhang Weiwu wrote:
Dear list
I had been developing by open xterm, maximize it, run vim in it. The benefit is it happen to be more than 160 columns wide, allow me to split vertically to edit two related programs each at 80-column width.
It has 3 problems: I. sometimes vim in xterm stop responding suddenly, and never coming back, reason unknown; II. my color schema doesn't work because xterm support limited number of colors III. I prefer gvim for its menu.
I'd like to select a small font for gvim so that I can maximize vim window and use two 80-column window inside of it without xterm. That way I need a font at 6 pixel wide. I cannot found such a font. in xfontsel I select 6 for pxlsz and only two fonts are available: "clean" and "fixed", both are two small to be readable at 6 pixel (then what font xterm is using that is readable even at 6 pixel??) and both are not selectable in gvim's choose font dialog.
Can someone recommend me a 6-pixel-wide readable font (like the one used by default in xterm) and usable in gvim? Thanks in advance!
P.S. maybe the best solution is to run at 1280 px wide screen with 8-pixel font, which is 160 column wide, but yet what I need is 161 column wide because there is one column used as separator:(
Have you looked at gvim, the x11 version of vi?
Here is the screenshot having run the x11 version of vi with really small readable font (in this case I used the commonly-found font "fixed"). It happen to be 81-column wide for left and right column. $ gvim -fn -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso10646-1 gopher://sdf.lonestar.org/I/users/weiwu/gvim_two_columns.png If you are young and can read it, it's probably good to use it for development. With a 1280-pixel wide screen vim should be able to present two 80-column window with more readable font.
-- Joseph Loo jloo@acm.org
-- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/5/07, Zhang Weiwu wrote:
I'd like to select a small font for gvim so that I can maximize vim window and use two 80-column window inside of it without xterm. That way I need a font at 6 pixel wide. I cannot found such a font. in xfontsel I select 6 for pxlsz and only two fonts are available: "clean" and "fixed", both are two small to be readable at 6 pixel (then what font xterm is using that is readable even at 6 pixel??) and both are not selectable in gvim's choose font dialog.
Way to read the post Joe... Anyway, Zhang, my favorite font for this is neep, it's in the xfonts-jmk font package. Give it a try. - -- Andy Harrison public key: 0x67518262 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://firegpg.tuxfamily.org iD8DBQFGjhlxNTm8fWdRgmIRAta1AJ44Kw4OsaWOX9e4i4u9OeKO+rXkGwCfVLdE +8XL3xoHfyoteKRYt/8RID4= =tFzp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
于 Fri, 6 Jul 2007 06:28:24 -0400 "Andy Harrison" <aharrison@gmail.com> 写道:
On 7/5/07, Zhang Weiwu wrote:
I'd like to select a small font for gvim so that I can maximize vim window and use two 80-column window inside of it without xterm. That way I need a font at 6 pixel wide. I cannot found such a font. in xfontsel I select 6 for pxlsz and only two fonts are available: "clean" and "fixed", both are two small to be readable at 6 pixel (then what font xterm is using that is readable even at 6 pixel??) and both are not selectable in gvim's choose font dialog.
Way to read the post Joe...
Anyway, Zhang, my favorite font for this is neep, it's in the xfonts-jmk font package. Give it a try.
Thank you for suggestion from both Andy and Joe. Now I have a version of vim with X11 GUI installed and I quite like it. I also tried neep font (with X11 version of gvim I can use -fn to specify neep ), I am surprised to find if I specify '11' as pxlsz I get some fonts less than 6-pixel wide, so probably by pxlsz xfontsel is only trying to tell me the height of the font. Actually after I have tried, even pxlsz=13, neep give me 166 columns per line when gvim maximized, right suit me need. Thanks to you both. For newbie on this list, this is what I did 1) download latest vim source 2) 'cd src' and then 'make', then su to root, run 'make install'; 3) launch vim by using /usr/local/bin/gvim -fn '-*-neep-*-*-*-*-13-*-*-*-*-*-*' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Zhang Weiwu <zhangweiwu@realss.com> [07-06-07 13:59]:
For newbie on this list, this is what I did 1) download latest vim source 2) 'cd src' and then 'make', then su to root, run 'make install';
You should definitely look a checkinstall as an alternative to "make install". openSUSE is an rpm based system and expects to be able to find all its packages in the rpm db. "make install" does *not* up date the db. Future rpm installs may cause problems with your vim install and may overwrite files which vim depends. AND, "make install" operations are *definitely* not for newbies! -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 7/6/07, Patrick Shanahan <ptilopteri@gmail.com> wrote:
AND, "make install" operations are *definitely* not for newbies!
I don't blame him for compiling from source, though. The rpm's for vim are so badly broken, interoperability between vim components really suffers. Modelines, for example, don't work correctly. So when running gvim, opening a file with a vim modeline is completely ignored. This is not the default behavior of vim and is due to the unnecessary, forced split of vim. It's fine that there's a non-gui rpm version available, but there should also be a full fledged rpm version. -- Andy Harrison public key: 0x67518262 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Andy Harrison <aharrison@gmail.com> [07-06-07 15:02]:
I don't blame him for compiling from source, though. The rpm's for vim are so badly broken, interoperability between vim components really suffers. Modelines, for example, don't work correctly. So when running gvim, opening a file with a vim modeline is completely ignored. This is not the default behavior of vim and is due to the unnecessary, forced split of vim. It's fine that there's a non-gui rpm version available, but there should also be a full fledged rpm version.
It's not a problem of compiling from source, but from installing via "make install". Checkinstall will generate an rpm which will keep your system clean.... -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
于 Fri, 6 Jul 2007 14:06:30 -0400 Patrick Shanahan <ptilopteri@gmail.com> 写道:
* Zhang Weiwu <zhangweiwu@realss.com> [07-06-07 13:59]:
For newbie on this list, this is what I did 1) download latest vim source 2) 'cd src' and then 'make', then su to root, run 'make install';
You should definitely look a checkinstall as an alternative to "make install". openSUSE is an rpm based system and expects to be able to find all its packages in the rpm db. "make install" does *not* up date the db.
It's nice to know there is a "Checkinstall" and I'll use it in future. I had been using suse for 2 years, I constantly compile from source when I cannot find appropriate rpm or if I am tired of trying to find the good rpm package. The result is file stacking at /usr/local/.. Yes it will be difficult to remove them later, but having a 320GB harddisk the eager of finding a solution to this problem never came to me before, hence the lack of knowledge on this issue.
Future rpm installs may cause problems with your vim install and may overwrite files which vim depends.
AND, "make install" operations are *definitely* not for newbies!
I don't know why it's not for newbies, but even a newbie constantly find such thing by reading the first page in src/INSTALL of every software they wish to compile, and the only way to stop them compiling things by themself, which is not a newbie task, is to provide rich rpm database, probably as rich as other distros like Ubuntu (with packages inherited from Debian) and make sure newbies finds them easily. This would be a real newbie's wish. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Zhang Weiwu <zhangweiwu@realss.com> [07-07-07 03:09]:
于 Fri, 6 Jul 2007 14:06:30 -0400 Patrick Shanahan <ptilopteri@gmail.com> 写道:
AND, "make install" operations are *definitely* not for newbies!
I don't know why it's not for newbies, but even a newbie constantly find such thing by reading the first page in src/INSTALL of every ....
I guess I should have been more clear. "make install" operations are *definitely* not for newbies on openSUSE/SuSE systems with the possibilites of system corruption. I have *no* argument concerning following the instructions provided with most tar-balls makes the process *usually* easy. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/6/07, Zhang Weiwu wrote:
3) launch vim by using /usr/local/bin/gvim -fn '-*-neep-*-*-*-*-13-*-*-*-*-*-*'
Alternately, in your ~/.vimrc file, you add the lines: if has("gui_running") set guifont="-*-neep-*-*-*-*-13-*-*-*-*-*-*" endif - -- Andy Harrison public key: 0x67518262 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://firegpg.tuxfamily.org iD8DBQFGjo/kNTm8fWdRgmIRAvZEAKDJtmrMvKvdU3q2PVNxllmatunLKQCgujEy Q++2bQAt34bnO67rG1ncSaA= =UcrJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Andy Harrison
-
Joseph Loo
-
Patrick Shanahan
-
Zhang Weiwu