this post was submitted on 26 Jun 2023
10 points (100.0% liked)
Programming
17398 readers
244 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That is not the feature I described, though. I'm aware of CTRL + SHIFT + F10, but the feature description is basically a simple way to automate setting the next statement.
Be honest: Is there an issue with the representation of the page or did you skip those parts?
It would be handy if I needed it in a loop that was going to repeat many times.
For most cases, I wonder if setting it up would take more time than hitting the brakepoint and moving the pointer manually.
I already rarely use conditional breakpoints for the same reason.
I feel you. It's annoying how the good stuff for debugging is hidden in some crappy menus in VS and IntelliJ by default.
About detour points: The second and third version shown in my post would be one keystroke. The first one is probably not worth it, unless they could be set in some sort of modal workflow, similar how setting tabbing order works for Windows Forms.
Ah, I see. I didn't see the bit about it being a breakpoint (detour point?). That's what I get for skim reading rather than comprehending it. Visual studio will let you do this, but it's a manual step, by combining a normal breakpoint and an execute next statement, and you'd have to do this each time you hit the breakpoint.
Having it happen automatically? A fairly niche feature, but I can see a few uses for it. The component features are already there, so I don't think it would be difficult to implement in a debugger that already supported execute next statement.