Gvim and key bindings about vdebug HOT 8 CLOSED

Hi, sorry about the long delay in responding!

That's interesting, I use Gvim too but haven't come across this problem yet. Have you tried turning debug on and looking at the logs? Set this:

let g:vdebug_options = {
\    "debug_file_level" : 2,
\    "debug_file" : "path/to/file.log"
\}

Start up Gvim and attempt to start the debugger. Then check the logs (paste the whole lot if you don't see anything).

Sorry it's very generic advice, but I have no idea what's happening so far!

from vdebug.

looks like vdebug totally not involved when I press any function key
(F2,F3,F4 etc). debug_file is not created at all

I attached to this email my .vim directory with all plugins as well as
config files. would you be so kind to try it on your environement?

thanks for your plugin. it is awesome!

On Mon, Nov 5, 2012 at 1:59 PM, Jonathan Cairns [email protected]:

Hi, sorry about the long delay in responding!

That's interesting, I use Gvim too but haven't come across this problem
yet. Have you tried turning debug on and looking at the logs? Set this:

let g:vdebug_options = {
\ "debug_file_level" : 2,
\ "debug_file" : "path/to/file.log"
}

Start up Gvim and attempt to start the debugger. Then check the logs
(paste the whole lot if you don't see anything).

Sorry it's very generic advice, but I have no idea what's happening so far!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-10068048.

Yours sincerely, Ivan Kuznetsov aka Kuzma
mailto: [email protected]

from vdebug.

looks like github do not attach files when you reply via email. here is my attachment: http://narod.ru/disk/63349698001.3cf74b99b9469ff4f70a99f992f97aa9/vdebug%20debug.tar.gz.html

from vdebug.

Hi, I think I've found what it is: you need to add

set nocompatible

to the top of your vimrc file. I actually couldn't get your config working on both Gvim and normal Vim until I added that. After adding that, I just sourced vdebug.vim and was able to start the debugger. Let me know how you get on.

from vdebug.

Unfortunately it doesn't help. I even tried to disable all other plugins —
no luck.

The issue seems to be somewhere in gvim configuration cause when I press
F10 I see dropdown — http://i.imagebanana.com/img/h0op5tdd/Selection_129.png

:version

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 25 2012 21:17:53)
Included patches: 1-409
Modified by Gentoo-7.3.409
Compiled by kuzma@kuzma-laptop
Huge version with GTK2 GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +conceal +cryptv -cscope +cursorbind +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 -lua +menu +mksession +modify_fname +mouse +mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg
+path_extra -perl
+persistent_undo +postscript +printer +profile -python -python3 +quickfix
+reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff
+startuptime +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
system vimrc file: "/etc/vim/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "/etc/vim/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H
-DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0
-I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pan
go-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15
-I/usr/include/libdrm -march=core2 -msse4.1 -O2 -pipe -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1
Linking: x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -L/usr/local/lib
-Wl,--as-needed -o gvim -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo
-lpango-1.0 -lfreetyp
e -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0 -lSM -lICE
-lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lelf -lcurses -lacl -lattr -lgpm
-ldl

On Mon, Nov 5, 2012 at 4:11 PM, Jonathan Cairns [email protected]:

Hi, I think I've found what it is: you need to add

set nocompatible

to the top of your vimrc file. I actually couldn't get your config working
on both Gvim and normal Vim until I added that. After adding that, I just
sourced vdebug.vim and was able to start the debugger. Let me know how you
get on.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-10071597.

Yours sincerely, Ivan Kuznetsov aka Kuzma
mailto: [email protected]

from vdebug.

Good call on printing the version!

It looks like your problem is that Python is not included in your Gvim config (it says -python -python3, whereas I have +python -python3). Your Vim might well work because it was compiled separately, at a guess.

So it looks like recompiling Gvim is the answer!

from vdebug.

bingo!

vim and gvim are separate packages in my gentoo. recompiling with python
use flag done the trick.

Thanks!

On Mon, Nov 5, 2012 at 5:10 PM, Jonathan Cairns [email protected]:

Good call on printing the version!

It looks like your problem is that Python is not included in your Gvim
config (it says -python -python3, whereas I have +python -python3). Your
Vim might well work because it was compiled separately, at a guess.

So it looks like recompiling Gvim is the answer!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-10073824.

Yours sincerely, Ivan Kuznetsov aka Kuzma
mailto: [email protected]

from vdebug.

Great! No problem, happy to help.

Glad you enjoy the plugin :)

from vdebug.