-
Notifications
You must be signed in to change notification settings - Fork 3
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
Debug Integration #34
Comments
Hi, coc-ansible is an extension to the LSP client plugin called coc.nvim. Unfortunately, coc.nvim does not directly support DAP. I am not using anything DAP related and will do some research and testing when I get interested. I would also like to find time to try your PR of vscode-ansible. ansible/vscode-ansible#1006 |
No worries, I wasn't really sure about the nvim landscape here but good information to know. I might try out a very bare bones example using |
@jborean93 I use AstroNvim if you need to test something, but I don't really use the debugger there. Might figure it out if needed, though. |
I just came across ansibug and tried it out with nvim-dap. Turns out nvim-dap wasn't fully spec compliant, but now it's working with this configuration: https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#ansible nice work |
That is awesome, I'll definitely be trying it out this week! |
Are you interested in potentially adding debug support in this plugin? I'm working on ansibug which is a Debug Adapter Protocol implementation. Currently I have a workable fork using this with the VSCode Ansible extension but I'm interested to see how well it adapts for other DAP compatible clients. I know nvim has a DAP client plugin called nvim-dap but my understanding of the vim/nvim ecosystem is quite rudimentary so I can't really help too much. If you are interested please let me know what you might need from me to test it out, otherwise feel free to close the issue :)
The text was updated successfully, but these errors were encountered: