You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We previously removed almost all references to the jupyter interactive window sessions from positron. However, there are still many references to jupyter interactive window sessions in settings
Given that these come from the Jupyter adapter and we don't fork that extension, I am not sure whether it's possible to suppress these settings like we did with the UI elements, but it could be worth considering.
In particular, I'm concerned about the shift + enter keyboard shortcut setting. If the user enables that setting, and then hits shift + enter, it will open a Jupyter interactive window session
The text was updated successfully, but these errors were encountered:
#2788 only stopped the configuration properties from showing up in the settings, but if you add "jupyter.interactiveWindow.textEditor.executeSelection": true to your settings.json, and hit Shift+Enter in a Python file, you can still open the interactive window. Will make a follow-up PR.
Check that no irrelevant Jupyter settings show in the settings UI.
Manually add the setting "jupyter.interactiveWindow.textEditor.executeSelection": true to your settings.json file, open a Python file and press Shift+Enter. It should not open an "Interactive Window" tab.
We previously removed almost all references to the jupyter interactive window sessions from positron. However, there are still many references to jupyter interactive window sessions in settings
Given that these come from the Jupyter adapter and we don't fork that extension, I am not sure whether it's possible to suppress these settings like we did with the UI elements, but it could be worth considering.
In particular, I'm concerned about the shift + enter keyboard shortcut setting. If the user enables that setting, and then hits shift + enter, it will open a Jupyter interactive window session
The text was updated successfully, but these errors were encountered: