Allow users to choose which editor to use for editing variable binary data
See original GitHub issueThere has been a new feature introduced to view and edit binary data of variables:
https://code.visualstudio.com/updates/v1_64#_viewing-and-editing-binary-data
This is a powerful feature and has the potential to expose fine-grained workflows such as disassembly views.
However, it enforces the user installs and uses the Hex Editor ms-vscode.hexeditor
extension:
Can a setting be exposed to allow the user to override this behaviour and choose a different extension for inspecting variables?
Issue Analytics
- State:
- Created a year ago
- Reactions:34
- Comments:15 (12 by maintainers)
Top Results From Across the Web
010 Editor Manual - Editing Variables with Scripts
This is the manual for 010 Editor, a professional hex editor and text editor. Use 010 Editor to edit the individual bytes of...
Read more >Binary Editor (C++) - Microsoft Learn
The Binary Editor allows you to edit any resource at the binary level in either ... Right-click the resource and select Open Binary...
Read more >Creating an editor for binary files - Stack Overflow
I've got a fairly simple binary file format I wish to create an editor for: Able to load the files; Able to save...
Read more >EDIT—edit a data set - IBM
You can use EDIT to edit workstation files on the host and host data sets on the workstation. This function is called distributed...
Read more >Editing Table Data - DbVisualizer 12.0 Users Guide
Editing Data in the Grid ... To edit a column value: ... You can also use the Set Selected Cells drop down menu...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s something we discussed, and decided to take a similar approach to the one we use flame chart where we install it on the fly. For a feature that a very small percentage of VS Code users are likely to see, we didn’t want to increase our overall footprint for it.
I think it could be marked experimental after non-continuous memory is available (and when a few questions are sorted https://github.com/microsoft/debug-adapter-protocol/issues/239 https://github.com/microsoft/debug-adapter-protocol/issues/238).
Just pinging again. @connor4312 do you know what I can do to help? I know the HexEditor made some progress but it still falls short in terms of life-cycle management.
Also, with my extension, we don’t need VSCode proper to do any memory reads itself or worry about refreshes and life-cycle management. No need for a virtual file system either. This may need a second option on who manages the data model (actual reads/writes, binding to debug sessions, etc.) We can do a much better job and is not a one size fits all mechanism, because we are tailored for debugging. Not file editing.