man pages in gvim
Hello! If I hit K in normal mode, then I get man page for the word I'm in. But in gvim this does not quite work. First I get the warning Terminal is not fully functional, and then comes the man page with formatting like this [1mSYNOPSIS[0m [1m#include sys/poll.h[0m [1mint poll(struct pollfd *[4m[22mufds[24m[1m, unsigned int [4m[22mnfds[24m[1m, int [4m[22mtimeout[24m[1m);[0m [1mDESCRIPTION[0m AFAIK, this is the preformatted man page. If I look at the man file, then I see exactly that. Out of curiousity, I've tried to use the tip 167 (I believe) to redirect output of man into vim, but got very similar result. On the other hand hitting K in terminal vim displays the page correctly. Do I miss some settings? vim-7.0. Thank you -- Minds, like parachutes, function best when open
Re: man pages in gvim
I don't know how to fix the problem, but I use manpageview.vim(http://vim.sourceforge.net/scripts/script.php?script_id) to view man page, info page, python docs, perl docs and more(the plugin is configurable to view other help docs similiar with man page). It works perfectly. Suggest you give it a try. Best regards, Vincent http://vincent:8080/lps-3.1/my-apps/sportbook-trunk/src/livebet/bo-client/index.lzx?debug=truelzr=swf6game_id=99livebet_bo_xml_external_host=vincentlivebet_bo_xml_external_port=8107livebet_bo_http_external_host=vincentlivebet_bo_http_external_port=8091lbfo_host0=vincentlbfo_xml_port0=8007lbfo_http_port0=8097bo_server_ip=vincentbo_server_port=8090livebet_bo_use_secure_protocol=0session_id=21b145dddf9fbaaae269301a2720758alivebet_bo_client_sending_ack_interval=10Andrei A. Voropaev wrote: Hello! If I hit K in normal mode, then I get man page for the word I'm in. But in gvim this does not quite work. First I get the warning Terminal is not fully functional, and then comes the man page with formatting like this [1mSYNOPSIS[0m [1m#include sys/poll.h[0m [1mint poll(struct pollfd *[4m[22mufds[24m[1m, unsigned int [4m[22mnfds[24m[1m, int [4m[22mtimeout[24m[1m);[0m [1mDESCRIPTION[0m AFAIK, this is the preformatted man page. If I look at the man file, then I see exactly that. Out of curiousity, I've tried to use the tip 167 (I believe) to redirect output of man into vim, but got very similar result. On the other hand hitting K in terminal vim displays the page correctly. Do I miss some settings? vim-7.0. Thank you -- The tool that save the most labor in a programming project is probably a text-editing system -- The Mythical Man-Month Try to make life easier ... http://vincent-wang.livejournal.com
Re: man pages in gvim
On 9/6/06, Andrei A. Voropaev [EMAIL PROTECTED] wrote: Hello! If I hit K in normal mode, then I get man page for the word I'm in. But in gvim this does not quite work. First I get the warning Terminal is not fully functional, and then comes the man page with formatting like this [1mSYNOPSIS[0m I also get Terminal is not fully functional, but otherwise, contents of the manpage looks normal. This is FC5 fedora core linux, vim7.0.86/gtk2. The message Terminal is not fully functional comes from 'less' pager, it seems. Try these things: 1. export MANPAGER=more or set kp=man\ -P\ more 2. If that does not fix the problem, then try this: set kp=myman where myman is following 1-liner script which you need to puto put it into your PATH --- myman #!/bin/sh man $@ | col -b | more Yakov
Re: man pages in gvim
On Wed, Sep 06, 2006 at 09:44:22AM +, Yakov Lerner wrote: On 9/6/06, Andrei A. Voropaev [EMAIL PROTECTED] wrote: Hello! If I hit K in normal mode, then I get man page for the word I'm in. But in gvim this does not quite work. First I get the warning Terminal is not fully functional, and then comes the man page with formatting like this 1mSYNOPSIS0m I also get Terminal is not fully functional, but otherwise, contents of the manpage looks normal. This is FC5 fedora core linux, vim7.0.86/gtk2. The message Terminal is not fully functional comes from 'less' pager, it seems. Try these things: 1. export MANPAGER=more or set kp=man\ -P\ more Aha, that gave me an idea. After reading thru the man pages for man, I've found that it passes the formatting to grotty program. The man page for grotty says that newer version puts into the output escape sequences for colors and bold/italic. These are the ones that cause problems for col -b, since it does not recognize them. So col -b simply strips esc codes leaving all those pesky 1m and 0m behind. To overcome that problem one may add -c option in /etc/man.conf to the command lines for NROFF TROFF and JNROFF. Thank you for help -- Minds, like parachutes, function best when open
