Skip to content
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

Error detected while processing function importjs#Init: #14

Closed
zirho opened this issue Oct 8, 2016 · 12 comments
Closed

Error detected while processing function importjs#Init: #14

zirho opened this issue Oct 8, 2016 · 12 comments
Labels

Comments

@zirho
Copy link

zirho commented Oct 8, 2016

Hello, thanks for the awesome plugin.

I have two osx machines, almost same neovim settings.

Working okay
NVIM 1.4.0
plugin manager: Vundle

Not working
NVIM 1.5.0
plugin manager: vim-plug

I am not sure this is about plugin manager or NVIM version.

below is from the one does not work.
Can you suggest a way to troubleshoot?

Thanks

 ~/.config/nvim   master ●  vi
Error detected while processing function importjs#Init:
line    3:
E117: Unknown function: job_start
E15: Invalid expression: job_start(['importjsd', 'start', '--parent-pid', getpid()], {'exit_cb': 'importjs#JobExit',})
line    7:
E121: Undefined variable: s:job
E116: Invalid arguments for function job_getchannel(s:job)
E15: Invalid expression: job_getchannel(s:job)
Press ENTER or type command to continue
 ~/.config/nvim   master ●  vi -v
NVIM 0.1.5
Build type: RelWithDebInfo
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/build/config -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/src -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/build/src/nvim/auto -I/tmp/neovim-20161007-26331-14gl0zw/neovim-0.1.5/build/include
Compiled by zirho6@MBPro1.local

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.1.5/share/nvim"

 ~/.config/nvim   master ● 

@zirho
Copy link
Author

zirho commented Oct 8, 2016

It turned out it is plugin manager.
junegunn/vim-plug this is actually popular one.
https://github.com/junegunn/vim-plug
Can we consider supporting this?

Thanks!

@lencioni
Copy link
Contributor

lencioni commented Oct 8, 2016

How did you determine that it was the plugin manager causing the problem? From your error message it looks to me like you are using a version of Vim that is too old and doesn't support the Vim features we are using here. What version of Vim are you using?

@tdooner
Copy link
Collaborator

tdooner commented Oct 11, 2016

I don't know if anyone has tested vim-import-js with neovim. Since the job control implementations have diverged, it seems unlikely to work without a little bit of extra work.

@zirho
Copy link
Author

zirho commented Oct 21, 2016

@lencioni I maybe wrong but I have almost same setup with different plugins manager. The one with other than vim-plug seemed working fine.
and as @tdooner said, it can be neovim. I'll put an update on this when I get a chance to look at.

Thank you all.

@brunoti
Copy link

brunoti commented Nov 24, 2016

Same problem here with vim 7.4.898 and neovim 0.1.2, using Vundle.

@hpurmann
Copy link

hpurmann commented Dec 9, 2016

Same problem with nvim 0.1.7 using vim-plug.

@agarrharr
Copy link

Same problem with nvim 0.1.7 using vim-plug.

1 similar comment
@nicklasnygren
Copy link

Same problem with nvim 0.1.7 using vim-plug.

@lencioni lencioni added the bug label Jan 23, 2017
@trotzig
Copy link
Contributor

trotzig commented Feb 16, 2017

Sorry for leaving so many comments unanswered here. It looks like neovim/neovim#5520 is relevant to the issue. Basically, neovim doesn't support the same channel interface as vim 8 does. If anyone is willing to take a stab at making the import-js plugin work for neovim, I'd be delighted to review a PR! If not, I'll try to get to it at a later time.

@agarrharr
Copy link

I read the reddit thread on Neovim API comparison with Vim channels. Do you know how plugins are supposed to work with both Neovim and Vim? Do you have to do a check to see if it's running in Neovim and do one thing, or if it's in Vim, do another thing instead?

@trotzig
Copy link
Contributor

trotzig commented Feb 16, 2017

I don't know to be honest, but it looks like if has('nvim') might do the trick. neovim/neovim#1931

We could also look into some kind of feature detection instead of detecting what editor is running.

Do you have a link to the reddit thread?

@agarrharr
Copy link

https://www.reddit.com/r/neovim/comments/58nrwv/neovim_api_comparison_with_vim_channels/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants