hawking's weblog

vim and lzma

hawking — 2008-04-21T00:22:46+03:00

To edit .lzma files with vim add the following snippet to your vimrc:

augroup lzma
        au!

        au BufReadPre,FileReadPre       *.lzma setlocal bin
        au BufReadPost,FileReadPost     *.lzma call gzip#read("lzma -d")
        au BufWritePost,FileWritePost   *.lzma call gzip#write("lzma")
        au FileAppendPre                *.lzma call gzip#appre("lzma -d")
        au FileAppendPost               *.lzma call gzip#write("lzma")
augroup END " augroup lzma

Note you need to have lzma-utils , not lzma, for this to work.

viewing man pages with vim

hawking — 2008-04-06T12:29:17+03:00

There are two ways to use vim to display man pages. The first one is using vimmanpager and the second one is using the :Man command from within vim. Today I fixed bug 212844 which was a problem about vimmanpager and colour codes. You'll have to reinstall vim to get the updated vimmanpager.

To use vimmanpager as your default man pager build vim with vim-pager USE flag and set the environment variable MANPAGER to vimmanpager.

For those who want to use the command :Man from within vim, here is a trick to get things right. Add the following lines to your vimrc:

" make :Man command avaliable
source $VIMRUNTIME/ftplugin/man.vim
" Default MANPAGER vimmanpager doesn't play well
" with the :Man command and we don't want to see raw colour codes
" so we use sed to strip them.
let $MANPAGER = "sed -e 's:\\x1B\\[[[:digit:]\\+m::g'"

Happy vimming :-)

vimgdb

hawking — 2007-04-12T02:31:15+03:00

There are many scripts to use gdb with vim. But the best and most useful implementation is the clewn.It implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. Clewn uses netbeans interface to connect to vim and runs concurrently.
There is also the patch vimGdb which is developed by the same people. They share the same base source code set to interface with gdb. The main difference is clewn runs as a seperate process but it has some features vimGdb doesn't have:

display of gdb expression values in a balloon
gdb run commands do input and output on the clewn terminal, while vimgdb users must use the gdb 'tty' or 'attach' commands to control the debuged program input/output
support of $cdir in the gdb directory list, allowing vim to access the names of the source files compilation directories as stored with the program debugging information.

There is an ebuild for clewn in the sunrise overlay. You need to emerge gvim with the netbeans USE flag to use it. I wrote an ebuild for the newest version 1.10 and bumped it, hopefully someone will review it and put it to reviewed/ soon.
I also wanted to try the vimGdb patch so I made some changes to the vim.eclass and added gdb USE flags to vim and gvim. The patch applies cleanly among with other vim patches in the gentoo tree.
To use the vimGdb :call gdb("") when you want to do debugging. You might want to put 'set autochdir' in your vimrc so that vim will change to the working directory and find other source files of the program as well. Here is a screenshot:

The source code is from app-misc/slmon which has some problems smiley. There is a breakpoint on the blueline. vim and gvim ebuilds with gdb USE flag are in my overlay if you want to try. Emerge it and do

:help gdb

from within vim to learn how to use it. Happy vimming!

vim script: hints_man3

hawking — 2007-03-14T07:00:09+03:00

I found a new vim script called hints_man3. It shows the prototype of C library functions as you write them. You need to set your cmdheight option to at least 2 for it to work. This can be done by adding:

au BufRead,BufNewFile *.c,*.h set ch=2

to your .vimrc file. Here is a screenshot: