Skip to content
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

Choose debugger binary editor #236105

Closed
adrianstephens opened this issue Dec 13, 2024 · 2 comments
Closed

Choose debugger binary editor #236105

adrianstephens opened this issue Dec 13, 2024 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@adrianstephens
Copy link
Contributor

Currently the debugger is hard-coded to require the ms-vscode.hexeditor extension to view binary data. I would like to select a different one.

I have found that it's possible to re-register the command 'workbench.debug.viewlet.action.viewMemory' to bypass the hard-coded checks, but this feels like a hack, requires knowing the undocumented parameters this command is sent, and, for some reason, doesn't work for the watch pane.

My request is just for a setting somewhere that lets a different command to be chosen, and passed documented parameters; but what I think would be nicer is allowing any extension to add commands to entries in the local and watch panels in the same way as they can for other views, and removing the hard-coded 'View binary data' button (which ms-vscode.hexeditor can contribute). This would open up the possibility of arbitrary data visualisations in custom editors.

@roblourens roblourens assigned connor4312 and unassigned roblourens Dec 14, 2024
@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 14, 2024
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2024
@connor4312
Copy link
Member

#197287

@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Jan 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants