dccsillag / magma-nvim

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

Add LAzyVim config options to README and sign it #94

Open elliottgreen opened 1 year ago

elliottgreen commented 1 year ago

I tried this a couple hours ago, but I signed it with the wrong key. Closed that pull-request, did the same thing, but signed it properly this time.

WhiteBlackGoose commented 1 year ago

The upstream is sadly dead, so I merge some PRs into my fork.

lumpsoid commented 1 year ago

@elliottgreen run = "UpdateRemotePlugins" is an unavailable option in lazy.nvim, so it doesn't have any effect on the configuration.

Therefore, it is not essential for the configuration to function correctly.

If you have used the run command in a similar way to packer.nvim, where it can be a string, function, or table, serving as a post-update/install hook, in lazy.nvim, the equivalent option would be build.

The build option is executed when a plugin is installed or updated. If it is a string, it will be run as a shell command. When prefixed with :, it is treated as a Neovim command. Additionally, you can specify a list to execute multiple build commands.

However, even without using the build option, it is not necessary for the configuration to work. It seems that the keys option is sufficient to achieve the desired behavior.

WhiteBlackGoose commented 1 year ago

I can now merge PRs. @lumpsoid could you propose changes to the PR so I could merge the correct version?

lumpsoid commented 1 year ago

@WhiteBlackGoose The last time I came here to check the config again, it didn't work for me, and since I couldn't figure out what the problem was quickly, it was all put aside.

Now I tried it again and was able to figure out what the problem was. I reinstalled the system, so I ran into this problem again with this plugin not wanting to run in LazyVim

What are the steps to check to get the plugin working: 1) if you are using virtual env for development, check that you have activated it before going into neovim. 2) check that you have pynvim pip install pynvim. 3) check that you have jupyter notebook 4) once you have installed pynvim then close the existing console and open a new one, where try to open neovim again and run magam using <leader>mi if you are using this config.

buck-ross commented 5 months ago

I tried this config, and ended up getting the error "Not an editor comand" for :UpdateRemotePlugins. This seems to be related to neovim#13267. However, after trying the recommended workaround (:let g:loaded_remote_plugins = 0, followed by :call remote#host#UpdateRemotePlugins()), I can't get NeoVim to load any of the :Magma* editor commands provided by this plugin, no matter what config tweaks I try.


EDIT I managed to resolve this on my own - see this comment for details.