Remove cucumber specific lines from vimrc #101

Closed
gylaz opened this Issue Feb 13, 2013 · 4 comments

Comments

Projects
None yet
4 participants
Owner

gylaz commented Feb 13, 2013

As a company we're moving away from Cucumber. It may make sense to remove these lines from vimrc:

" Cucumber navigation commands
autocmd User Rails Rnavcommand step features/step_definitions -glob=**/* -suffix=_steps.rb
" :Cuc my text (no quotes) -> runs cucumber scenarios containing "my text"
command! -nargs=+ Cuc :!ack --no-heading --no-break <q-args> | cut -d':' -f1,2 | xargs bundle exec cucumber --no-color
Owner

jferris commented Feb 13, 2013

@croaky submitted #55 for this a few months ago and I rejected it because we still had active projects using cucumber.

I worry about getting rid of stuff like this because of projects we take over. I deleted a ton of shoulda/test-unit stuff from my dotfiles that wasn't hurting anything and ended up wishing I still had it when I did some work on LevelUp.

Does this stuff get in your way somehow, or is it just a "I don't want to cook in a messy kitchen" kind of thing?

Owner

croaky commented Feb 13, 2013

I used this alias on Clearance yesterday. I think we still have some OSS that uses Cucumber+Aruba.

Contributor

geoffharcourt commented Sep 15, 2013

As for the two Rnavcommand lines, that functionality has been removed in the current version of vim-rails, so the Cucumber navigation lines lines for "config" and "step" are non-functional at the moment. If you run ``:Estep` you get this error:

:Rnavcommand has been removed.  See :help rails-projections

If this functionality is desired, it would be easy to add in a projections file. The current master doesn't have a set place to put them. I'm happy to write the projections, but want to do it in a way that makes it easy to merge. In any event, I think the two offending lines can be removed at this point in time.

Owner

gylaz commented Jan 20, 2014

Going to close this, since we're keeping Cucumber stuff for now.

gylaz closed this Jan 20, 2014

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