Closed jeremy-p-mann closed 3 years ago
I'm actually not that familiar with vim plugins or anything, but my guess is that the error is actually not with vim, but with the way jupyter ascending is set up (because we haven't even really officially launched it, partly because of how annoying it is to set up correctly right now!)
All the vim plugin does is call a command line program with some particular arguments, so the best way to debug this is to make sure that the command line call succeeds. Try running this from the same working directory as your vim process and using whatever python will be active for that vim process (replacing the $absolute_file_path
and $line_number
variables)
python -m jupyter_ascending.requests.execute --filename $absolute_file_path --linenumber $line_number
You can (and should) enable debugging on both the client and server by setting these environment variables:
# client
JUPYTER_ASCENDING_LOG_LEVEL=DEBUG JUPYTER_ASCENDING_SHOW_TO_STDOUT=1 JUPYTER_ASCENDING_IS_LOGGING_ENABLED=1 python -m jupyter_ascending.requests.execute --filename $absolute_file_path --linenumber $line_number
# server--launch jupyter notebook like this instead of however you normally do:
JUPYTER_ASCENDING_LOG_LEVEL=DEBUG JUPYTER_ASCENDING_SHOW_TO_STDOUT=1 JUPYTER_ASCENDING_IS_LOGGING_ENABLED=1 jupyter notebook
Opened a PR for this.
The jupyter_ascending
and jupyter_ascending.vim
docs where not aligned and the vim plugin matched on synced
and not sync
if match(file_name, g:jupyter_ascending_match_pattern) < 0 return endif
Ahh, that makes sense. Thanks for fixing!
I merged the PR, so lmk if it still doesn't work for some reason.
Thanks for closing.
I am using jupyter-notebook 6.1.5 and neovim 0.4.4