Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Never return results of omni completion #85

Open
hitsumabushi opened this Issue · 2 comments

2 participants

@hitsumabushi

I have a problem about omni completion of ruby code.

I upload my vimrc & bugreport.txt and sample file for reproducing this problem.
Please see https://github.com/k-sakai/freeze-vim-setting.


Problem:

  • Freeze rubycomplete#Complete (Never return any result).

Reproducing:

  1. At first, enable filetype plugin. For example, "filetype plugin on" in your vimrc.
  2. In ruby file, type the for completion of specific object's method. See below example.

Example:

test.rb

example = gets.foo
example.(type <C-x> <C-o> here)

What happen:

  • omni completion never retrun any result
  • and just desplay searching message.

I think right behavior in this case is

  • returning the completion list or
  • finishing search and display the message "Pattern not found".
@segfault
Owner

At first glance this looks to be due to the ruby being completed. The current version of omnicompletion loads/runs the buffer inside of vim. So it's attempting to run gets inside of vim, which leads to "weird" behavior.

@hitsumabushi

segfault

At first I think so too.
However, when I just write "gets", omnicompletion behave usual.
For example,

bar = gets
bar.(type <C-x><C-o> here)

Is it right behavior?
It is strange for me there is a deference between writing "gets" and "gets.foo"(or "gets.to_s").

@segfault segfault was assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.