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

Request to Add Feature for Moving Execution Pointer During Debugging #236815

Closed
maketmimi opened this issue Dec 22, 2024 · 1 comment
Closed

Request to Add Feature for Moving Execution Pointer During Debugging #236815

maketmimi opened this issue Dec 22, 2024 · 1 comment
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code

Comments

@maketmimi
Copy link

Hello VS Code team,

I would like to request a feature for the debugging functionality in Visual Studio Code. Specifically, the ability to move the execution pointer (similar to the yellow arrow in Visual Studio) to a previous or forward line during a debugging session. This feature is extremely useful for developers to re-execute or skip lines of code without restarting the debugging session.

Why this feature is important:
Improves Debugging Efficiency:
Moving the execution pointer allows developers to test specific sections of code multiple times without restarting the application.

Widely Used in Visual Studio:
This feature is available in Visual Studio and has been a significant productivity booster for many developers, especially those working with complex applications.

Use Cases:

Skipping lines that are not relevant to the current debugging session.
Re-executing lines to test changes in program behavior.
Quickly testing alternative paths in code execution without modifying source code.
Suggested Implementation:
Introduce a UI feature in the debugging session (e.g., drag-and-drop the execution pointer in the editor margin).
Provide a shortcut or command in the Command Palette to reset the program counter (e.g., Debug: Move Execution Pointer).
Ensure this functionality works seamlessly with existing debuggers such as GDB, LLDB, and others supported by VS Code.
Thank you for considering this request. Adding this feature will make debugging in VS Code even more powerful and developer-friendly.

Best regards,

@roblourens roblourens added the *out-of-scope Posted issue is not in scope of VS Code label Dec 22, 2024
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

2 participants