Fix Cucumber::Undefined #415

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
7 participants
@bvicenzo

Hi, I and my team friends were having problems with cucumber syntax checker.
'Cause it always showed warns about errors and the command line showed "Cucumber::Undefined".

I believe that I fixed it.

Congratz for this excelent plugin!

Tanks,
Bruno Vicenzo.

@dbarnett

This comment has been minimized.

Show comment
Hide comment
@dbarnett

dbarnett Dec 1, 2012

This just always evaluates to let makeprg = 0 because + isn't made to work on strings. I think you meant to use . instead. Did you see the cucumber checker working correctly after you made this change somehow?

Is there no case where someone might have "bundle" installed but want to not use it for cucumber?

This just always evaluates to let makeprg = 0 because + isn't made to work on strings. I think you meant to use . instead. Did you see the cucumber checker working correctly after you made this change somehow?

Is there no case where someone might have "bundle" installed but want to not use it for cucumber?

This comment has been minimized.

Show comment
Hide comment
@scrooloose

scrooloose Dec 3, 2012

additionally, you should change BundleExec() to s:BundleExec()

additionally, you should change BundleExec() to s:BundleExec()

@duhanebel

This comment has been minimized.

Show comment
Hide comment
@duhanebel

duhanebel Feb 19, 2013

I'm not sure it's directly related, but looking at cucumber's documentation seems that --dry-run can't be use for proper syntax check:
-d : Invokes formatters without executing the steps. This also omits the loading of your support/env.rb file if it exists.
Which means it will always complain for any step defined on a gem or locally to the project.

I'm not sure it's directly related, but looking at cucumber's documentation seems that --dry-run can't be use for proper syntax check:
-d : Invokes formatters without executing the steps. This also omits the loading of your support/env.rb file if it exists.
Which means it will always complain for any step defined on a gem or locally to the project.

@sequethin

This comment has been minimized.

Show comment
Hide comment
@sequethin

sequethin May 5, 2013

duhanebel is right, --dry-run produces warnings every time for me, removing it works fine.

duhanebel is right, --dry-run produces warnings every time for me, removing it works fine.

@duhanebel

This comment has been minimized.

Show comment
Hide comment
@duhanebel

duhanebel May 6, 2013

That way you run the full tests, which is kind of impractical for long ones.

/FAb

On 5 May 2013, at 20:43, Michael Hernandez notifications@github.com wrote:

duhanebel is right, --dry-run produces warnings every time for me, removing
it works fine.


Reply to this email directly or view it on
GitHubhttps://github.com/scrooloose/syntastic/pull/415#issuecomment-17457679
.

That way you run the full tests, which is kind of impractical for long ones.

/FAb

On 5 May 2013, at 20:43, Michael Hernandez notifications@github.com wrote:

duhanebel is right, --dry-run produces warnings every time for me, removing
it works fine.


Reply to this email directly or view it on
GitHubhttps://github.com/scrooloose/syntastic/pull/415#issuecomment-17457679
.

@lcd047 lcd047 closed this Jun 8, 2013

@jondkinney jondkinney referenced this pull request in tpope/vim-cucumber Oct 30, 2014

Closed

Step reported as Cucumber::Undefined but can be jumped to #30

@jondkinney

This comment has been minimized.

Show comment
Hide comment
@jondkinney

jondkinney Oct 30, 2014

I think this is a -r features issue for config/cucumber.yml. See my comment here: tpope/vim-cucumber#30

I think this is a -r features issue for config/cucumber.yml. See my comment here: tpope/vim-cucumber#30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment