search

dccsillag / magma-nvim

Interact with Jupyter from NeoVim.
GNU General Public License v3.0
988 stars 50 forks source link

[Bug] Cannot start MagmaInit #32

Closed statquant closed 2 years ago

statquant commented 2 years ago

Hello, this is not a bug but I cannot use the plugin at all. Installation went smoothly and :checkhealth appears fine but I simply cannot fire the plugin using :MagmaInit, it is like the plugin was not installed. I am probably doing something very stupid

:checkhealth image

:version image

~/.init.vim is empty image

Describe the bug E492: Not an editor command: Magma

To Reproduce Simply type :MagmaInit

Screenshots image

Desktop (please complete the following information):

dccsillag commented 2 years ago

Did you run :UpdateRemotePlugins?

(The installation should do that for you, but who knows...)

dccsillag commented 2 years ago

If you run :UpdateRemotePlugins, it should show something like this:

remote/host: python3 host registered plugins ['test.py', 'magma']
remote/host: generated rplugin manifest: /home/daniel/.local/share/nvim/rplugin.vim

(Note how it shows that it is registering magma.)

statquant commented 2 years ago

Plug did run it, I did it again manually and see something that makes sense image

dccsillag commented 2 years ago

Hmm, yeah, that seems correct. And :MagmaInit still doesn't work?

statquant commented 2 years ago

I'll be damned it now does, I had to get out of tmux though... I'm very sorry for the bother. I am not sure why Plug did not execute the hook correctly.

dccsillag commented 2 years ago

Phew! Don't worry, it's no bother.

I also have no idea why vim-plug didn't execute that. I'll take a look into it; maybe my installation instructions for it are incorrect.

LifeWorks commented 2 years ago

I have the same problem. No MagamaInit command found.

LifeWorks commented 2 years ago

OK. Solved. Sorry for the confusion.

wjdhamilton commented 2 years ago

I had the same problem. Exiting tmux seemed to be the cure.

richardguinness commented 1 year ago

FWIW I found having tmux running made no difference. I experienced the same issue having loaded the plugin with both packer and vim-plug in two separate environments: in both cases running :UpdateRemotePlugins manually was necessary.