OptionsError: No options have been set about vdebug HOT 8 CLOSED

Hi Fiesh,

I've been looking into this bug and can't reproduce it at all. Not only that, I can't even see how it can happen from the code! However, it is happening, so there's something wrong :)

Is there any pattern to it? For instance, does it happen after starting the debugger with F5, or do you not even need to do that for the problem to occur?

Are there any other Python based plugins that you know you're using?

Thanks

from vdebug.

I just created an empty test user, with the following .vimrc:

set rtp+=~/.vim/bundle/vundle/
call vundle#rc()

Bundle 'gmarik/vundle'
Bundle 'joonty/vdebug.git'

filetype plugin indent on     " required!```

The ~/.vim only contains bundle, which in turn only contains vundle and vdebug.

I open 'vim foo', press F10, and get the exact error from above.  (Also when I just open 'vim' and press F10, the fact that there is no filename isn't really caught nicely, but that's not a big issue.)  But of course it might make sense that vdebug cannot set a breakpoint for a file 'foo', yet this is the easiest way to reproduce this.

I'm using VIM version 7.3.646, which is linked against libpython2.7.so.1.0.

Any other helpful information I can provide?

Thanks for looking into this!

from vdebug.

This is very strange! I copied that vimrc and tried the exact steps that you laid out, but got no error at all. The only difference is that I had to add set nocompatible at the top of the vimrc, otherwise Vundle couldn't start up. Did you not need this also? Could just be a small version difference in Vim.

Could you just dump the output of vim --version?

Also, what version of Vdebug are you using? Is it a packaged one or from this repo? If it's from the repo, it might be worth trying the dev branch if you haven't already.

I'm determined not to let this beat us :)

from vdebug.

Dear Joonty,

Thank you so much for the recommendation with the branch. I can no longer reproduce the error!

So I think you can safely mark this as solved!

Sorry for making so much work for such a trivial fix and thanks for such an amazing vim plugin!

fiesh

from vdebug.

Great, really pleased that worked for you! Also glad you like the plugin :)

from vdebug.

Hey Joonty,

I am still experiencing this issue:

• [ERROR] {Fri 08 2013 10:22:39} An error occured: <class 'vdebug.opts.OptionsError'>
  Traceback (most recent call last):
  File "/Users/brimble/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 31, in run
  self.runner.run()
  File "/Users/brimble/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 160, in run
  self.open()
  File "/Users/brimble/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 43, in open
  vdebug.opts.Options.get('server'),
  File "/Users/brimble/.vim/bundle/vdebug/plugin/python/vdebug/opts.py", line 32, in get
  raise OptionsError("No option with key '%s'" % name)
  OptionsError: No option with key 'server'

In my vim config I think I added these things and that might of been what caused it to start happening. I am not 100% sure though:

let g:vdebug_options = {'break_on_open' : 0}
let g:vdebug_options = {'watch_window_style' : 'compact'}

from vdebug.

@yargy were you able to resolve this issue. I am facing the same issue.

from vdebug.

@zeeshanjan82 Can you paste the relevant lines of your .vimrc? In theory, supplying the whole dictionary should work (and does on my copy), but here's a more foolproof way of setting Vdebug options that may work if that way does not:

if !exists('g:vdebug_options')
    let g:vdebug_options = {}
endif
let g:vdebug_options['break_on_open'] = 0
let g:vdebug_options['watch_window_style'] = 'compact'

That should work reliably if there are some odd loading-order issues involved, as it ensures the dictionary exists, and then sets individual keys.

Also, I doubt this will be of help to @yargy three years later, but their syntax above is incorrect. The break_on_open option will be overwritten, because the second let re-defines the whole dictionary without that key. There are two ways to set vdebug_options: setting individual keys with the bracket notation, as above, or setting the whole dictionary at once. Setting the whole dictionary multiple times will cause unintended behavior.

Note that when defining the whole dictionary, re-sourcing the .vimrc will break Vdebug, as it recreates vdebug_options without the defaults, and Vdebug has no chance to add the defaults as it does at startup.

from vdebug.