no test lib set

[bitboxer]

Just updated to the latest version, but somehow I did something wrong. I get a No test lib set when using rspec. The ftdetect somehow fails to insert the the test lib. When I add it manually via :call neoterm#test#libs#add('rspec'), it works

What did I do wrong? What can I do to pinpoint the problem?

[kassio]

@bitboxer strange. Could you do a :echo g:neoterm_test_libs? It should return a list like this: ['rspec'].

[bitboxer]

It returns []

[kassio]

Did you opened a spec file, or just vim?

[kassio]

Could you give me a more detailed step-by-step to reproduce it here?

[bitboxer]

Of course.

I am using vundle to install the plugins, the latest master is in my bundle dir. When I open a _spec file either by nvim path/to/file/test_spec.rb or via NERDtree, i can't run the tests because it always says "No test lib set".

Maybe the ftdetect rule is not loaded correctly? How can I check for that?

[bitboxer]

Okay, I now switched from vundle to vim-plug and it works. Somehow I have either misconfigured my vundle or it has problems with your plugin.

[kassio]

@bitboxer, I'll try to add a buffer variable to set the lib by buffer. This way you will be able to use more than one lib by "project".

[kassio]

@bitboxer not you'll not need this function in your vimrc anymore. :smile:

[bitboxer]

What you you mean by that?

[kassio]

@bitboxer, sorry the message should be: now, you'll not need this function in your vimrc anymore. I added a buffer variable that is set with the lib. So the neoterm will now, by buffer, which test lib use. :smiley:

[kassio]

the vundle problem I'll see on #7.

[kassio]

the vundle problem I'll see on #7.