-
Notifications
You must be signed in to change notification settings - Fork 174
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
Support neovim #77
Support neovim #77
Conversation
This pull request introduces 1 alert and fixes 1 when merging a553b5f into 68c47ed - view on LGTM.com new alerts:
fixed alerts:
|
c5c030a
to
bf2718f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 18 files reviewed, all discussions resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 16 of 18 files at r1, 2 of 2 files at r3, 1 of 1 files at r4.
Reviewable status: complete! all files reviewed, all discussions resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r5.
Reviewable status: complete! all files reviewed, all discussions resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! all files reviewed, all discussions resolved
neovim open debug mode ,watcher can't write |
Fixes #29
bindeval
: Instead, require a send function in the job/channel API, and marshal the arguments through global variables.TODO:
SetUpCommandBuffer
so that the output of the command actually appears in the buffer in neovim. Don't understand why this doesn't work:VimspectorShowOutput <tab complete cetegory>
:Vimspector...
commands discoverable ?:VimspectorEval <tab complete expr>
and:VimspectorWatch <tab complete expr>
:VimscpectorReset
Might decide nvim is "best effort" basis only. If not, will need to:
Known issues:
But, here's vimspector "working" in neovim: