rubyblock depends on matchit.vim #6

Open
nelstrom opened this Issue Dec 28, 2010 · 3 comments

Comments

Projects
None yet
2 participants
@nelstrom
Owner

nelstrom commented Dec 28, 2010

If matchit.vim is not enabled, then rubyblock will fail.

Remove this dependency.

@docwhat

This comment has been minimized.

Show comment Hide comment
@docwhat

docwhat Oct 20, 2012

Don't you mean it depends on ruby matchit? Since matchit is included in vim since version 6.0...

docwhat commented Oct 20, 2012

Don't you mean it depends on ruby matchit? Since matchit is included in vim since version 6.0...

@nelstrom

This comment has been minimized.

Show comment Hide comment
@nelstrom

nelstrom Oct 20, 2012

Owner

matchit.vim is included in the default Vim distro, but it's not enabled. Rubyblock depends on matchit.vim being enabled.

Also, matchit.vim is now able to jump between ruby keywords. Presumably, this wasn't the case when ruby-matchit was authored, but now that matchit.vim supports this functionality, I see no reason to use ruby matchit.

Owner

nelstrom commented Oct 20, 2012

matchit.vim is included in the default Vim distro, but it's not enabled. Rubyblock depends on matchit.vim being enabled.

Also, matchit.vim is now able to jump between ruby keywords. Presumably, this wasn't the case when ruby-matchit was authored, but now that matchit.vim supports this functionality, I see no reason to use ruby matchit.

@docwhat

This comment has been minimized.

Show comment Hide comment
@docwhat

docwhat Oct 22, 2012

Huh. I have vim 7.3.692 but your vim plugin required the ruby-matchit to work. vir was only selecting the end statement, not the whole block, without ruby-matchit. I take it that was a bug and I should file that separately?

docwhat commented Oct 22, 2012

Huh. I have vim 7.3.692 but your vim plugin required the ruby-matchit to work. vir was only selecting the end statement, not the whole block, without ruby-matchit. I take it that was a bug and I should file that separately?

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