Posts Tagged ‘Vim’

In this post, we will explore how to set different TAB settings while editing C/C++ and Python code. For C/C++, we want 2 spaces for indendation, while for Python, we will stick to PEP 8 recommendations (4 spaces for indendation, 8 spaces for TAB, 4 spaces for expandtab). Vim being such a powerful and versatile editor, there are many ways to achieve this. We will explore the most portable way – with changes just to the .vimrc.

" Python options
let python_highlight_all = 1
function! s:set_python_settings()
  set tabstop=8
  set softtabstop=4
  set shiftwidth=4
function! s:unset_python_settings()
  set tabstop=2
  set softtabstop=2
  set shiftwidth=2
autocmd BufNewFile,BufEnter *.{py} call set_python_settings()
autocmd BufLeave *.{py} call unset_python_settings()

What we are doing here is define two functions, set_python_settings() which will change tab settings as per PEP 8 recommendations and unset_python_settings() which will default to our C/C++ settings. Autocmd upon entering a new buffer (BufEnter) or a new file is opened (BufNewFile) of type *py, we call set_python_settings() to set tab settings for Python. When we leave a buffer (BufLeave) of type *.py, we get back to original settings by calling unset_python_settings().

Exuberant ctags is a pretty nifty utility for source code browsing. Especially since it integrates so well with vim. Also exuberant ctags can understand many languages (41 as per the official website). So this is relevant not only for C/C++ or Python but for all 41 languages supported (and future ones too). In this post, we explore yet another popular plugin using exuberant ctags – TagList.

TagList is capable of showing a list of functions/global variables/class/struct towards one side of the vim. This is similar to some IDEs or event editors like Notepad++. This makes browsing and navigation pretty easy. Our aim will be to be able to navigate current file using TagList window and to always display current function name in the status line.

Screenshot of TagList plugin showing current function name in status line

For this, we will need:

TagList will work only with exuberant ctags and not with any other ctags (specifically GNU ctags). Install exuberant ctags if required. Also ensure that ctags command should actually invoke exuberant ctags.

Install TagList plugin (see elaborate steps in the link). Typically vim plugins are installed by simply copying to $HOME/.vim/plugin directory. If any documentation is there, copy that to $HOME/.vim/doc and re-index vim help by giving “:helptags $HOME/.vim/doc” command in vim.

Now we need to customize the TagList plugin options to get what we want.

" TagList options
let Tlist_Close_On_Select = 1 "close taglist window once we selected something
let Tlist_Exit_OnlyWindow = 1 "if taglist window is the only window left, exit vim
let Tlist_Show_Menu = 1 "show Tags menu in gvim
let Tlist_Show_One_File = 1 "show tags of only one file
let Tlist_GainFocus_On_ToggleOpen = 1 "automatically switch to taglist window
let Tlist_Highlight_Tag_On_BufEnter = 1 "highlight current tag in taglist window
let Tlist_Process_File_Always = 1 "even without taglist window, create tags file, required for displaying tag in statusline
let Tlist_Use_Right_Window = 1 "display taglist window on the right
let Tlist_Display_Prototype = 1 "display full prototype instead of just function name
"let Tlist_Ctags_Cmd = /path/to/exuberant/ctags

nnoremap <F5> :TlistToggle
nnoremap <F6> :TlistShowPrototype

set statusline=[%n]\ %<%f\ %([%1*%M%*%R%Y]%)\ \ \ [%{Tlist_Get_Tagname_By_Line()}]\ %=%-19(\LINE\ [%l/%L]\ COL\ [%02c%03V]%)\ %P

Notice the call to Tlist_Get_Tagname_By_Line() within the statuline. This is what displays the current function name (actually tag which can be class name or struct name or any tag) in the status line. With the above settings, pressing F6 will show the prototype of current function at the bottom.

Pressing F5 will open up the TagList window which will show the list of functions/classes/structs/define etc. The focus is automatically switched to the list window and we can quickly jump to the function/class/struct definition we want to. Upon selecting an entry, the list window is automatically closed.shrink the window back to default size.

Screenshot of TagList window

Now with the full prototype display, it is not very easy to read the actual function name. TagList has a zoom feature to overcome this. Press “x” and the TagList window will enlarge, occupying almost the complete vim screen. Selection of an entry or pressing F5 again will close the window. Pressing x again will shrink the window back to default size.

Screenshot of TagList window zoomed using "x" key

TagList generates its own tags file and does not require the user to provide a tags file. This file is generated every time we switch to a buffer. The tags file is created somewhere in /tmp/ folder. TagList cannot work with a user generated tags file.

Omni Completion in Vim

Posted: August 26, 2010 in C/C++, Programming, Vim
Tags: , , ,

Vim 7 onwards, we have Omni Complete feature. This feature is similar to IntelliSense in Visual Studio or other IDEs. It can show a pop up menu displaying the structure, class or scope context. Here is a screenshot of Omni Complete displaying the class scope in CCCC code base .

OmniCppComplete screen shot in CCCC code.

As you can see, it can show all methods and variables including its original context like type, prototype (in case of method), documentation (if documented), private/protected/public, file defined in etc.

For getting Vim to work like this, you will need

Install all 4 by whatever means (apt-get, yum, build from source). OmniCppComplete and SuperTab are Vim scripts, detailed installation steps are given in the respective links. GNU has a version of ctags. But what we need is exuberant ctags which is different from GNU ctags. Most popular Linux distros bundle GNU ctags, but exuberant ctags should be available from the repository.

Vim is an excellent editor, but does not understand C/C++ natively. This is where ctags comes in to the picture. Ctags will generate a “tags” file which is like an index of the project source code. This tags file is used by Vim and OmniCppComplete script to provide contextual data in a pop-up menu.

To build a ctags tags file, give the command from the top directory of the project. This can be done from any subdirectory too (for even more focused tags file).

ctags -R --languages=C,C++ --c++-kinds=+p --fields=+iaS --extra=+q ./

Run vim from the same directory. By default, Vim will search for tags file beginning from current directory to all parent directories. First tags file found will be used. For better usability of OmniCppComplete, put these in your .vimrc file.

if v:version >= 600
  filetype plugin on
  filetype indent on
  filetype on

if v:version >= 700
  set omnifunc=syntaxcomplete#Complete " override built-in C omnicomplete with C++ OmniCppComplete plugin
  let OmniCpp_GlobalScopeSearch   = 1
  let OmniCpp_DisplayMode         = 1
  let OmniCpp_ShowScopeInAbbr     = 0 "do not show namespace in pop-up
  let OmniCpp_ShowPrototypeInAbbr = 1 "show prototype in pop-up
  let OmniCpp_ShowAccess          = 1 "show access in pop-up
  let OmniCpp_SelectFirstItem     = 1 "select first item in pop-up
  set completeopt=menuone,menu,longest

The default key mapping for invoking Omni Completion is C-X C-O. SuperTab plugin can help us invoke Omni Complete when we press TAB key. Also in the default color scheme, vim pop-up menu is in pink. Let’s change that to green.

if version >= 700
  let g:SuperTabDefaultCompletionType = "<C-X><C-O>"
  highlight   clear
  highlight   Pmenu         ctermfg=0 ctermbg=2
  highlight   PmenuSel      ctermfg=0 ctermbg=7
  highlight   PmenuSbar     ctermfg=7 ctermbg=0
  highlight   PmenuThumb    ctermfg=0 ctermbg=7

As we edit code, newer types get defined, but vim continues to use the same tags file. So we need to regularly update our tags file. We can add a shortcut map (say pressing F4) in our .vimrc for the same.

function! UpdateTags()
  execute ":!ctags -R --languages=C++ --c++-kinds=+p --fields=+iaS --extra=+q ./"
  echohl StatusLine | echo "C/C++ tag updated" | echohl None
nnoremap <F4> :call UpdateTags()

Vim is all about customizing it to your tastes. You can never get the perfect .vimrc file or plugin collection and settings from anywhere. The trick is to collect cool stuff for your .vimrc and plugins. Vim tips wiki in wikia is a good place for a lot of info. Play around with them. Find what suits best for you. And never forget to share. Happy coding 🙂

Building Gvim from source

Posted: August 15, 2010 in Vim
Tags: , ,

I recently stumbled upon this very interesting vim plugin – OmniCppComplete. It promised to solve one of the problems that has been nagging me. While editing C/C++ code in vim, I have always wished if it could behave like Visual Studio and show structure/class members when we give object. or object->.

I wanted to try it out right away. But now comes the problem. It works only on vim 7 and above. It seems vim 7 onwards, OmniComplete feature is added which allows such stuff. At my workplace, the Debian server where I write code, has vim 6. Tough luck. Plus, I share the server with another 12 users, and do not have root powers. So next option is to build gvim from source. It wasn’t as easy, so this post explains the step I took to get it working.

Before we begin, a brief introduction about building stuff from source in Linux.

Step 0 – Brief introduction to building from source in Linux

Linux being open source, most software for Linux is open source too. That means you have full access to the source code. A bit of googling should get you what you are looking for. Traditionally, make is the utility used to build software for Unix like (and hence Linux) OSes. Linux has its own version of make called GNU make. It should be already installed on you Linux distro. Make depends upon a makefiles which describe what need to be done to build source code. To take care of the variations in Linux distros, GNU came up with  Autoconf and Automake which can generate makefiles based upon your particular Linux distro. Typically there will be an executable file “configure” which tells Autoconf/Automake how to generate make files.

So the typical steps to build something from source in Linux is

tar -xzvf source.tgz # untar source code
tar -zjvf source.tar.bz2 # same as above, different compression algo
cd source # move to source code directory
./configure # Autoconf/Automake will generate makefiles
make # make will build the binaries
make install # make install will copy binaries to /usr/bin \
             # or /usr/local/bin (may require root permissions)

Now if you have root permissions, you can follow the above steps. But there are times when you don’t have root permissions, or you do not want to install the binaries in the usual location, we can do this easily while invoking configure. Almost all configure scripts will take “–prefix” as an option. Here you can specify an alternate path where the binaries should be installed to when make install is given.

While compiling, I ran into some issues where configure picked my architecture to be 64 bit. But I wanted a 32 bit application. So I gave “–build” and “–host” options as i386-linux to specify a 32 bit compilation.

pkg-config is a neat utility that can help autoconf in finding the path of the required version of dependent packages. pkg-config will search the path in the same order specified by the environment variable PKG_CONFIG_PATH.

We are going to install gvim and the other stuff into /home/username/usr/bin since we do not have root permissions. So the typical commands that we are going to use are

export PREFIX=$HOME/usr
export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig
export HOST=1686-linux
export BUILD=i686-linux
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install

Also we will keep all source code in /home/username/usr/src. So

mkdir -p ~/usr/src
cd ~/usr/src

Now we are all set. Let’s begin.

Step 1 – Get the source code of course 🙂


The latest version of gvim is 7.3 when I am writing this blog. But I got gvim setup a couple of weeks back, so still have 7.2. There is no separate code for gvim. The code for vim has the code for gvim as well. Gvim depends upon some graphical toolkit like GTK+ (GTK 1.2 from Gnome), GTK2 (current latest GTK from Gnome), Motif (from IBM’s CDE), Athena (from MIT) etc.

Step 2 – Untar it and try compiling

tar -xjvf vim-7.2.tar.bz2
cd vim72
./configure --prefix $HOME/usr --host=i386-linux --build=i386-linux

Wait a minute. Configure could not find any graphical front ends, so skipping gvim. Bad :(. We want to get gvim 7.2 and vim 7.2 is not enough. Typical Linux distributions rarely contain the “devel” packages required for compiling dependent package. Vim could not find the header files of GTK+/GTK2/Motif/Athena (usually found in “devel” package) required to build gvim. Since we do not have root powers, we cannot just do apt-get install.

Step 3 – Get GTK+ and its dependencies’ source code

Well this is not as easy as it sounds. GTK has its own dependencies. I went through the compilation of each source package to list down all the dependencies. Here is the compiled list.


Since I also use gvim for some coding in Python, I also got Python source code so that gvim was compiled with Python support (+python).


Step 4 – Untar all the stuff including GTK+ and Python

tar -xjvf glib-2.24.0.tar.bz2
tar -xzvf libxml2-2.7.1.tar.gz
tar -xzvf libpng-1.4.3.tar.gz
tar -xjvf atk-1.30.0.tar.bz2
tar -xjvf freetype-2.4.2.tar.bz2
tar -xzvf fontconfig-2.8.0.tar.gz
tar -xzvf pixman-0.18.2.tar.gz
tar -xzvf cairo-1.8.10.tar.gz
tar -xzvf pango-1.28.0.tar.gz
tar -xzvf gtk+-1.2.10.tar.gz
tar -xjvf Python-2.7.tar.bz2

Notice that we used ‘j’ switch for tar.bz2 archives and ‘z’ switch for tar.gz archives.

Setp 5 – Build them

export PREFIX=$HOME/usr
export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig
export HOST=i686-linux
export BUILD=1686-linux
cd glib-2.24.0
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../libxml2-2.7.1
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../libpng-1.4.3/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../atk-1.30.0/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../freetype-2.4.2/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../fontconfig-2.8.0/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../pixman-0.18.2/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../cairo-1.8.10/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../pango-1.28.0/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../gtk+-1.2.10/
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install
cd ../Python-2.7
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD
make install

All the dependencies are met. Now we are all set to build gvim. That leads us to

Step 6 – Build gvim

cd ../vim72
./configure --prefix=$PREFIX --host=$HOST --build=$BUILD \
  --enable-mzschemeinterp --enable-pythoninterp --enable-tclinterp \
  --enable-cscope --enable-fontset \
make install

Ta-da. Gvim is ready. Well almost. If you try to run gvim it will throw this error.

file $PREFIX/bin/gvim
/home/aufather/usr/bin/gvim: symbolic link to `vim'
/home/aufather/usr/bin/gvim --version
/home/aufather/usr/bin/gvim: error while loading shared libraries: \ cannot open shared object file: \
No such file or directory

Well this is because gvim could not find the shared libraries it requires to run. They are in $PREFIX/lib, but we have to tell that to bash. We do this by setting the LD_LIBRARY_PATH environment variable.

export LD_LIBRARY_PATH=$HOME/usr/lib
~/usr/bin/gvim --version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Aug 16 2010 01:37:22)
Compiled by aufather
Normal version with GTK GUI.  Features included (+) or not (-):
-arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui
+diff +digraphs +dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search
-farsi +file_in_path +find_in_path +float +folding -footer +fork()
-gettext -hangul_input -iconv +insert_expand +jumplist -keymap
-langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
+mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm
-mouse_jsbterm -mouse_netterm -mouse_sysmouse +mouse_xterm -multi_byte
+multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl
+postscript +printer -profile +python +quickfix +reltime -rightleft
-ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop
+syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo
+termresponse +textobjects +title +toolbar +user_commands +vertsplit
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu +windows +writebackup +X11 +xfontset +xim
+xsmp_interact +xterm_clipboard -xterm_save

You can put these lines in your ~/.bashrc

export LD_LIBRARY_PATH=/home/username/usr/lib
alias vim='/home/username/usr/bin/vim'
alias gvim='/home/username/usr/bin/gvim'

That’s it. vim and gvim 7.2 is ready on your machine. Take it out for a spin 🙂