Comment 5 for bug 702314

Revision history for this message
Tim Camper (twcamper) wrote :

I tried vim-gnome (7.3.429 from the debian package maintainers), and the behavior is the same.

Built vim from source (7.3.672 from Bram himself) and the behavior is the same.

My build procedure:

1) $ sudo aptitude purge vim.gtk vim-gui-common vim-runtume vim
2) $ cd /tmp
3) $ hg clone https://vim.googlecode.com/hg/ vim # installed mercurial first
4) $ cd vim/src
5) $ ./configure CFLAGS="-I/usr/include/gtk-2.0 -L/usr/lib/x86_64-linux-gnu/gtk-2.0"
  important!! this line should be in the 'configure' output:
   checking for GTK - version >= 2.2.0... yes; found version 2.24.10
                (no "found version" means no gui gets built, silently)

All this proves is that the bug was not introduced into the Vim code by the
debian people. It could be a Bram bug or a GTK+ bug introduced by
either the debian maintainers or the GTK+ people.

FWIW I also tried vim-athena, but I didn't find it to be a usable option because I couldn't find a way to reset the font size. I doesn't have the F10 problem though, because the menus only respond to mouse clicks, no hot or arrow keys.