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
When in debugger, any action in console changes active document #9918
Comments
|
I'm pretty sure this is a reasonable recent regression, and it's super annoying when debugging. |
|
The debugger does this intentionally in many cases; e.g. if you use a stepping command then it switches you back to the source window so you can see where the instruction pointer has moved. However, it shouldn't be doing it for any statement you run. |
|
Ah makes sense! |
Verified FixedVerified that in the case outlined above, the focus now remains on the new document and does not return to the source file after typing into the console and pressing enter. |
|
This is also happening in and it is really annoying. Thanks, |
|
@jcrodriguez1989; the situation should be improved in the latest daily builds. Would you be willing to test and report back? |
Gentlemens, I use a full-fledged docker layer roker/r studio:4.1.1, respectively, I would like to know when the official release will be released? Because using R with such a debugger is a very big pain( |
|
Just got a new computer and have been experiencing this same issue. Is there a more formalized workaround besides the daily builds? |
|
This should already be resolved in the latest release (2022.02.1). If you're still having trouble, please file an issue with more details. |
|
For re-testing:
|
System details
Steps to reproduce the problem
Add the following code to a file, save it, and source it:
Open a new document.
Type 1 in the console and press enter.
The active tab moves away from the new document and back to the source file
Describe the problem in detail
Describe the behavior you expected
Running code in the console shouldn't change the active tab
The text was updated successfully, but these errors were encountered: