-
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
[Feature Request]: Ability to programmatically set the DAP communication port. #97
Comments
Looking at it, it's possible without code changes:
A quick test suggests that works. |
I admit, of course, that For the record, it accepts a dictionary mapping variables to values. There's also a special key |
Ok, I'll give it a shot. In the long term would you prefer |
Oh it should be public/documented. That’s why I’m leaving this open. |
I've confirmed it works exactly as described. |
This is useful enough to be made public. Closes #97.
This is useful enough to be made public. Closes #97.
This is useful enough to be made public. Closes #97.
Is your feature request related to a problem? Please describe.
I'd like to be able to take the communication port number result of the
vscode.java.startDebugSession
command and pass it to vimspector when starting it.#3 (comment)
Describe the solution you'd like
I think what I'm looking for is a function in the vimspector public API which takes the DAP communication port as an argument. It would be callable from viml.
Describe alternatives you've considered
I haven't considered any alternatives though I'm open to anything to streamline the process of using a random DAP communication port and getting that information seamlessly passed to vimspector.
Additional context
See this ticket #3 (comment) for additional context.
The text was updated successfully, but these errors were encountered: