You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
I wanted to be able to pass parameters to a Debuggable (just like I'd do in CLI after cargo run --). But I didn't find any way to do that without editing rust-tools sources.
Did I miss something, or is this feature not available ?
If it's not, could it be possible to discuss how you'd want such a feature to behave, so I can add it to rust-tools ?
FYI I already have this implemented locally, but obviously it's kinda dirty since I'm not very experienced in LUA (helpers copy-pasted from SO).
The text was updated successfully, but these errors were encountered:
I got same problem recently. I think it is great that use a cmd to set parameters so that we can reuse args when we next debug.
I had implemented this feature too with just nvim-dap in other language.
I try to add feature for rust-tools but it maybe need edit sources.
I got same problem recently. I think it is great that use a cmd to set parameters so that we can reuse args when we next debug. I had implemented this feature too with just nvim-dap in other language. I try to add feature for rust-tools but it maybe need edit sources.
how did you configure it like this mine seems to be working but when I go to into function it goes into some assembly and then gives out of buffer. it works OK with the continue command
this is the debugger part of rust-tools setup in my config ; using neovim 0.9
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I wanted to be able to pass parameters to a Debuggable (just like I'd do in CLI after
cargo run --
). But I didn't find any way to do that without editing rust-tools sources.Did I miss something, or is this feature not available ?
If it's not, could it be possible to discuss how you'd want such a feature to behave, so I can add it to rust-tools ?
FYI I already have this implemented locally, but obviously it's kinda dirty since I'm not very experienced in LUA (helpers copy-pasted from SO).
The text was updated successfully, but these errors were encountered: