Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect loading order of overrides. #314

Closed
michaelfavia opened this issue Mar 7, 2013 · 3 comments
Closed

Incorrect loading order of overrides. #314

michaelfavia opened this issue Mar 7, 2013 · 3 comments
Labels

Comments

@michaelfavia
Copy link

Im not sure why its happening but my .vimrc.local and .vimrc.bundles.fork seem to be loading before the bundles themselves.

http://www.pastebin.ca/2329442

I am including a few new Bundles in .vimrc.bundles.local:
Bundle 'joonty/vdebug.git'

And i need to override an option or two:
let g:vdebug_options['break_on_open'] = 0
let g:vdebug_features['max_children'] = 128 " this is only available in dev branch

My understanding was that i could do this in either .vimrc.local (which should be the last file parsed) or .vimrc.bundles.fork which is where you seemingly indicate it should be done most cleanly (makes sense).

Both fail with the following message onload:
Error detected while processing /Users/michaelfavia/.vimrc.bundles.fork:
line 4:
E121: Undefined variable: g:vdebug_options
line 5:
E121: Undefined variable: g:vdebug_features
line 8:

Seemingly as a result of the dictionary not being defined yet (e.g. the bundle/plugin not laoded yet). My pastebin from :scriptnames above seems to confirm this.

Am I doing this wrong or is this some sort of odd bug? Im happy to chase it down anyway you need. Thanks, -mf

@artfulrobot
Copy link

Yeah, I have the same two lines, but I noticed that I set the features by assigning a whole dictionary and it was working; but assigning a value to a key in a dictionary as I'd done on the options was not working.

I found that the following (which I have at the bottom of my .vimrc file, after vundle#end and other gubbins) does not error, and that the default dictionary keys/values are still added in fine:

 let g:vdebug_options = {'break_on_open': 0 }
 let g:vdebug_features = {'max_children': 128 }

@bronzehedwick
Copy link
Contributor

@michaelfavia, did the closing of the vdebug issue fix this problem?

@ghost ghost added the needinfo label Aug 12, 2014
@ghost
Copy link

ghost commented Jan 3, 2015

closing for lack of response. reopen if you can you can reproduce with latest spf13-vim

@ghost ghost closed this as completed Jan 3, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants