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

Interesting, g:rubycomplete_rails works in my Neovim, but not my Vim. #349

Open
bluz71 opened this Issue Jun 22, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@bluz71

bluz71 commented Jun 22, 2017

Hello support,

This is more a request for information than a "bug-report". Please close immediately.

Particulars:

  • Mac Sierra with Homebrew installed Neovim (0.2) and Vim (8.0, 1-562)
  • Ruby 2.4.1 via ruby-install and chruby

Vim options:

    let g:rubycomplete_buffer_loading       = 1
    let g:rubycomplete_classes_in_global    = 1
    let g:rubycomplete_rails                = 1

Both Vim and Neovim are correctly omni-completing simple Ruby expressions, in my Rails app, such as:

"hello".downc<Ctrl-x Ctrl-o>

However, only Neovim is completing Rails code, for example I have an Album model with a starts_with_letter scope, hence when I do this:

Album.starts_w<Ctrl-x Ctrl-o>
  • Neovim is expanding to the full function starts_with_letter
  • Vim however is saying Pattern not found

I am curious, why is one editor completing and not the other? Am I supposed to set some other option? Am I doing something wrong to break Rails completion in normal Vim?

If Vim was not completing Ruby code that would make more sense since that would indicate a Ruby mismatch between the Ruby Vim was built against vs the Ruby being used; but that theory is shot down since Ruby code is being completed.

Side note, seeing my Rails code completing in Neovim is damn impressive.

Many thanks.

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