René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature Request] Add options for handling errors encountered during debugging","articleBody":"Hello,\n\nWhile debugging, I encountered an \"undefined variable\" error.  \nHowever, my attention was focused on the editor area, and the spelling error notification happened to be obscured by the line highlight where my cursor was.  \nAs a result, I didn't notice that Pylance had already reported the error.\n\nWould it be possible for the Python debugger to check for Pylance-detected errors before starting a debug session,  \nand instead jump directly to the PROBLEMS panel instead of launching the debugger?  \nJust like how VSCode behaves with JavaScript.\n![Image](https://github.com/user-attachments/assets/ab1262a4-99d2-41bc-9f09-b7a53bb0ef80)\n\nAlthough this may only save a few seconds, it can significantly reduce wasted attention and improve productivity, especially for beginners who go through a lot of trial and error.\n\nThank you very much for your help!\n\nVSCode version: 1.100.2  \nPython Debugger version: 2025.9.2025052001  \nPylance version: 2025.5.1","author":{"url":"https://github.com/tzengshinfu","@type":"Person","name":"tzengshinfu"},"datePublished":"2025-05-21T08:49:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/714/vscode-python-debugger/issues/714"}