Option 'omnifunc' not set on Linux

Question

Option 'omnifunc' not set on Linux

spencerwi opened this issue 10 years ago · 24 comments

Launching Vim and editing an FSharp file with this plugin installed launches a background fsautocomplete process, which is to be expected.

Subsequently exiting vim leaves the fsautocomplete process still running, which is not to be expected.

The net result is that if I follow a common loop of "edit->:wq->test, edit->:wq->test" I could wind up with many background fsautocomplete processes hanging around chewing up system resources.

Answer 1 · 2016-03-31T06:18:04.000Z

Hi,

I can't reproduce this on OSX. Can you provide some more detail on the environment you are using?

Because the first parse is so slow I wouldn't recommend a workflow with transient vim sessions. I tend to have a split screen setup with vim left open.

Thanks

Answer 2 · 2016-03-31T12:05:52.000Z

Well, admittedly, after updating I can no longer reproduce it on my linux box, but now I'm also not getting any autocomplete; none of the "FSharp...." commands are defined and Ctrl-X Ctrl-O (triggering omnicomplete) just says Option 'omnifunc' not set!

I don't see any errors on startup. I'm using Neovim on ubuntu 15.10 (with python support available/installed), with the plugin installed via Vim-Plug, and up until I did an update (PlugUpdate) everything worked fine, minus the runaway processes.

Answer 3 · 2016-03-31T12:08:13.000Z

how are you installing it?

On Thu, 31 Mar 2016 at 13:05 Spencer Williams notifications@github.com
wrote:

Well, admittedly, after updating I can no longer reproduce it on my linux
box, but now I'm also not getting any autocomplete; none of the
"FSharp...." commands are defined and Ctrl-X Ctrl-O (triggering
omnicomplete) just says Option 'omnifunc' not set!

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#42 (comment)

Answer 4 · 2016-03-31T12:17:57.000Z

Ah yes fsharpbinding leftovers have caused very weird issues in the past.
:)

On Thu, 31 Mar 2016 at 13:17 Spencer Williams notifications@github.com
wrote:

Aaaand I purged it and reinstalled it and now it works. I did have a
leftover fsharpbinding/ folder in bundle/, which looks from other issues
like it can cause problems.

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#42 (comment)

Answer 5 · 2016-03-31T12:19:03.000Z

Whoops, sorry, deleted last comment by mistake; it was:

And I purged and reinstalled and now it works. I did have a leftover fsharpbinding/ folder in bundle/, which I've read in other issues can cause problems.

Answer 6 · 2016-03-31T12:21:08.000Z

Looks like I spoke too soon:

https://asciinema.org/a/5he42yb79h8ve6tke5u4c4i32

Not sure why I had an intermittent case where it worked once after purge/reinstall, and hasn't worked again. (probably worth noting: vim is aliased to nvim in my terminal)

Answer 7 · 2016-03-31T12:24:10.000Z

Sorry. Not sure what it is that isn't working on that video.

On Thu, 31 Mar 2016 at 13:21 Spencer Williams notifications@github.com
wrote:

Looks like I spoke too soon:

https://asciinema.org/a/5he42yb79h8ve6tke5u4c4i32

Not sure why I had an intermittent case where it worked once after
purge/reinstall, and hasn't worked again.

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#42 (comment)

Answer 8 · 2016-03-31T12:25:34.000Z

I open an FSharp source file, and trigger omnicomplete. Nothing happens except Option 'omnifunc' is not set.

Answer 9 · 2016-03-31T12:33:18.000Z

did you run make install after the re-install? I take it yo are using plain
pathogen and none of the other bundlers?

On Thu, 31 Mar 2016 at 13:25 Spencer Williams notifications@github.com
wrote:

I open an FSharp source file, and trigger omnicomplete. Nothing happens
except Option 'omnifunc' is not set.

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#42 (comment)

Answer 10 · 2016-03-31T12:42:03.000Z

I'm using Vim-Plug, and have it configured as per the README here, but I figured a make install is worth a shot.

https://asciinema.org/a/8f08a88c61y1qtt4997vnbbhk

Still no luck (notice the vim statusbar stating Option 'omnifunc' not set).

Even though I haven't been able to get it working yet, I do appreciate your help. I recognize that at this point we're bordering on "user support" territory, so I really appreciate you taking the time.

Answer 11 · 2016-03-31T12:50:54.000Z

ah - ok so it seems like the fake script is broken - I don't use that
myself and I am not sure what it is doing. the current strategy is to just
git clone vim-fsharp to the bundle directory and run 'make'.

On Thu, 31 Mar 2016 at 13:42 Spencer Williams notifications@github.com
wrote:

I'm using Vim-Plug, and have it configured as per the README here, but I
figured a make install is worth a shot.

https://asciinema.org/a/8f08a88c61y1qtt4997vnbbhk

Still no luck (notice the vim statusbar stating Option 'omnifunc' not set
).

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#42 (comment)

Answer 12 · 2016-03-31T13:05:57.000Z

Still not working for me. Bummer. Not sure what changed, but hopefully it'll work again in the future.

Thanks for your help.

Answer 13 · 2016-03-31T13:20:25.000Z

when did you last update? - very little has changed in the last few months.

On Thu, 31 Mar 2016 at 14:05 Spencer Williams notifications@github.com
wrote:

Still not working for me. Bummer. Not sure what changed, but hopefully
it'll work again in the future.

Thanks for your help.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#42 (comment)

Answer 14 · 2016-03-31T13:36:56.000Z

Prior to the update (yesterday) that triggered my current set of
remove-reinstall-check cycles, I'd only had vim-fsharp installed for about
two months. I did, however, also update Vim-Plug, so it's possible that the
fault lies there instead.

On Thu, Mar 31, 2016 at 9:20 AM Karl Nilsson notifications@github.com
wrote:

when did you last update? - very little has changed in the last few months.

On Thu, 31 Mar 2016 at 14:05 Spencer Williams notifications@github.com
wrote:

Still not working for me. Bummer. Not sure what changed, but hopefully
it'll work again in the future.

Thanks for your help.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#42 (comment)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#42 (comment)

Answer 15 · 2016-04-27T12:07:19.000Z

Okay, I've figured out why it worked briefly and then stopped again.

Something about the plugin seems to be very path-dependent; it works when I launch vim from inside of my $HOME/.vim directory, but outside of that it doesn't do anything.

I setting let g:fsharpbinding_debug = 1 in my .vimrc, but the debug log files never appeared in /tmp/.

Answer 16 · 2016-04-27T12:29:36.000Z

Nope, I was wrong -- the issue is not with running it from inside $HOME/.vim, but with how I load the file.

If I open vim and then :e /the/full/path/to/my/file.fsx, then fsharp-vim works (omnicomplete is set, the various commands are registered).
If I open vim from inside /the/full/path/to/my/ and then :e file.fsx, then fsharp-vim works.
If I open vim by running vim /the/full/path/to/my/file.fsx from the command-line, then fsharp-vim doesn't work (omnicomplete not set, no commands registered).
If I open vim from inside /the/full/path/to/my by running vim file.fsx, then fsharp-vim doesn't work.

Answer 17 · 2016-04-27T12:49:49.000Z

Ah ok - so there is a genuine issue there - I can't replicate it on osx
however - which version of vim are you on?

On Wed, 27 Apr 2016 at 13:29 Spencer Williams notifications@github.com
wrote:

Nope, I was wrong -- the issue is not with running it from inside
$HOME/.vim, but with how I load the file.

If I open vim and then :e /the/full/path/to/my/file.fsx, then
fsharp-vim works (omnicomplete is set, the various commands are registered).

If I open vim from inside /the/full/path/to/my/ and then :e file.fsx,
then fsharp-vim works.

If I open vim by running vim /the/full/path/to/my/file.fsx from the
command-line, then fsharp-vim doesn't work (omnicomplete not set, no
commands registered).

If I open vim from inside /the/full/path/to/my by running vim
file.fsx, then fsharp-vim doesn't work.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#42 (comment)

Answer 18 · 2016-04-27T13:10:48.000Z

I've tried it with current NeoVim and with vanilla Vim 7.4.712, both on Ubuntu 15.10 (wily)

Answer 19 · 2016-04-27T13:26:57.000Z

i'm on 7.4 as well and can do vim test.fsx quite nicely without any issues

I wonder what is different.

On Wed, 27 Apr 2016 at 14:10 Spencer Williams notifications@github.com
wrote:

I've tried it with current NeoVim and with vanilla Vim 7.4.712, both on
Ubuntu 15.10 (wily)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#42 (comment)

Answer 20 · 2016-10-27T00:30:33.000Z

Just to chime in, running Arch I don't see this issue on NeoVim 0.1.5 or Vim 7.4.

Answer 21 · 2016-11-03T11:59:52.000Z

@spencerwi do we need to keep this open?

Answer 22 · 2016-11-03T12:04:37.000Z

I still have trouble with it at times, but since it seems like others are not hitting the issue, I'm leaning towards an issue with my own system. No need to keep this open, then.

Answer 23 · 2016-11-03T12:04:55.000Z

Also, I just connected the dots that I've talked to you on the FP slack. Hi again!

Answer 24 · 2016-11-03T12:05:09.000Z

Hi, and thanks!