Open mgedmin opened 14 years ago
well that's what you get for fooling around ;) I'll look into it.
Apparently this happens when there's no pydbgp.py on the path.
I think I ran into this by syncing my .vimrc and .vim from another workstation where I had previously done a full proper vim-debug install. On my other workstation, I had enough to try to run, but I had not installed dbgp.
Ok. I think I understand what's going on.
I am also running into this issue. I am on Snow Leopard and MacVim, I installed both https://github.com/jabapyth/pydbgp and this project using sudo python setup.py install, and now am running exactly mgedmin's problem described above. :py import dbgp seems to work fine though.
Hi Jared,
is there any change with that issue?
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/vim_debug/commands.py", line 44, in debugger_
cmd
cmd['function'](*args)
TypeError: quit() takes exactly 1 argument (2 given)
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/vim_debug/commands.py", line 44, in debugger_
cmd
cmd['function'](*args)
File "/usr/local/lib/python2.7/dist-packages/vim_debug/new_debugger.py", line 186, in quit
self.bend.close()
AttributeError: Debugger instance has no attribute 'bend'
Im also having the same problem, i run debian vim+python and used https://github.com/fisadev/fisa-vim-config
Installed everything successfully, but no change.
pydbgp.py --help
pydbgp -d localhost:9000 script.py [args]
-d hostname:port to debug a script
-k ide_key a IDE key used with proxies
Any Idea? Help would be great.
Thanks, Sebastian
Something more:
the vimrc uses vundler, what i think is not the problem, but it uses a workaround:
" Python and PHP Debugger
Bundle 'fisadev/vim-debug.vim'
The keyboard bindings also look good.
" debugger keyboard shortcuts
map <F5> :Dbg over<CR>
map <F6> :Dbg into<CR>
map <F7> :Dbg out<CR>
map <F8> :Dbg here<CR>
map <F9> :Dbg break<CR>
map <F10> :Dbg watch<CR>
map <F11> :Dbg down<CR>
map <F12> :Dbg up<CR>
Tomorrow i gonna try the manual installation and let you know if it helped.
Greetings, Sebastian
Great, I'll have a closer look at it tomorrow too.
Sebastian Wendel notifications@github.com schrieb:
Something more:
the vimrc uses vundler, what i think is not the problem, but it uses a workaround:
" Python and PHP Debugger Bundle 'fisadev/vim-debug.vim'
The keyboard bindings also look good.
" debugger keyboard shortcuts map <F5> :Dbg over<CR> map <F6> :Dbg into<CR> map <F7> :Dbg out<CR> map <F8> :Dbg here<CR> map <F9> :Dbg break<CR> map <F10> :Dbg watch<CR> map <F11> :Dbg down<CR> map <F12> :Dbg up<CR>
Tomorrow i gonna try the manual installation and let you know if it helped.
Greetings, Sebastian
Reply to this email directly or view it on GitHub: https://github.com/jabapyth/vim-debug/issues/3#issuecomment-10702157
Sent from my Android phone with K-9 Mail.
+1
So, I tried to find out what was happening in the code and looks like pydbgp.py couldn't initialise due a environment variable that it didn't recognised.
After running the following command(e.g. setting the required environment variables), it worked:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
After some fooling around with
:Dbg b (timeout) :Dbg quit :Dbg - (timeout) :Dbg quit :Dbg .
I got an error message that I dismissed by accident without being able to read. Now I cannot :Dbg quit -- I get this traceback:
":Dbg ." now doesn't work either -- prints the usage message -- so there's no obvious way to debug anything without restarting vim.