-
Notifications
You must be signed in to change notification settings - Fork 294
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
Run by line: Run All should stop RBL session #7718
Comments
What happened was expected. The cells weren't running, they were queued to run after you were done using RBL. The error saying keyboard interrupt is also normal. Although you make a good point. It would feel more responsive if clicking run all ends the RBL session and starts running immediately. |
I don't know about that. Why would it be different from the case where a cell is running normally and you click "run all"? |
My answer to that is because this is not only running, its also debugging. But I don't know what would be best, consistent behavior, or more responsiveness. |
I think we should look into what's expected, when user is in rbl can they run cells and vice versa and what the expected behavior. to me Rbl and running cell are the same, we're still executing code. |
Let's do the same thing that we're doing if the user has currently running cells and they try to do run-by-line. We show a messagebox explaining the mode they're in. |
Moving out of October since the workaround is fairly discoverable. Just interrupt executing any of the queued cells. RBL will then be stopped. |
Testing microsoft/vscode#133903
The text was updated successfully, but these errors were encountered: