Great stuff! This integration with vimspector makes my vim setup much closer to what I have in CLion. One thing that I noticed and couldn't replicate, that maybe you could tell me what I'm missing: When I enable codeLens, and set up the rust-analyzer configurations, I can only trigger coc-codelens-action (for Run and Debug) from the function declaration line. While, in the video, you can trigger it from anywhere within the scope of the executable function. Is there an option to enable this that I missed? (Yes, I have been 👀 your dotfiles repo trying to find it! 😅) Thanks for the video!
can this plugin debug multi-threaded rust applications? or how do you debug multi processes spawned from rust ? or how do you debug subproceses spawned from rust ?
Thanks a ton! This will be incredibly useful to me! Also, please replace your fire alarm battery so that you don't die in a fire.
I swear I did...
Thank you. That was a fantastic tutorial!
I was using rust-gdb for quite a long time, but when I started to build applications with async functions, the "step into" won't work as I expected.
Good job man!
Great stuff! This integration with vimspector makes my vim setup much closer to what I have in CLion.
One thing that I noticed and couldn't replicate, that maybe you could tell me what I'm missing:
When I enable codeLens, and set up the rust-analyzer configurations, I can only trigger coc-codelens-action (for Run and Debug) from the function declaration line. While, in the video, you can trigger it from anywhere within the scope of the executable function. Is there an option to enable this that I missed? (Yes, I have been 👀 your dotfiles repo trying to find it! 😅)
Thanks for the video!
Did you tried nvim-dap plugin? It's a neovim-only plugin for the DebugAdapterProtocol (similar to vimspector)
I took a lot at it a bit in the past. I just currently like my setup
can this plugin debug multi-threaded rust applications?
or how do you debug multi processes spawned from rust ?
or how do you debug subproceses spawned from rust ?
SUper awesome.
Can you publish your configuration files somewhere so that others can recreate your setup more easily?
Here you go: github.com/KarlWithK/dotfiles
Could you please share your neovim configs?
How to call out the run and debug boxes?
I call it use coc-actions.
btw. very nice color scheme.
what is your colorscheme?
Update to this, but I have this in
`~/.config/nvim/after/rust.lua `
```lua
vim.g.termdubgger = "rust-gdb"
vim.opt.shell = "/opt/homebrew/bin/fish"
local map = vim.api.nvim_buf_set_keymap
local options = { silent = true}
map(0, 'n', '=', ":w:term rustc =expand('%') && ./=expand('%:r')", {noremap = true})
map(0, 'n', '9', ':CocCommand rust-analyzer.run', {noremap = true})
map(0, 'n', 'dd', ':CocCommand rust-analyzer.debug', {noremap = true})
map(0, 'n', 'dc', 'VimspectorContinue', options)
map(0, 'n', 'di', 'VimspectorStepInto', options)
map(0, 'n', 'do', 'VimspectorStepOver', options)
map(0, 'n', 'da', 'VimspectorStepOut', options)
map(0, 'n', 'ds', 'VimspectorStop', options)
map(0, 'n', 'db', 'VimspectorToggleBreakpoint', options)
map(0, 'n', 'de', 'VimspectorBalloonEval', {})
map(0, 'x', 'de', 'VimspectorBalloonEval', {})
```
CocCommand rust-analyzer.debug allows you to pick what function to debug!
compared to visual studio, this is10x less ergonomic