-
Notifications
You must be signed in to change notification settings - Fork 290
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
Consider renaming "Connect to Your Own Jupyter Server" #10675
Labels
bug
Issue identified by VS Code Team member as probable bug
notebook-remote
Applies to remote Jupyter Servers
verified
Verification succeeded
Milestone
Comments
greazer
added
notebook-remote
Applies to remote Jupyter Servers
vscode-web
and removed
triage-needed
Issue needs to be triaged
labels
Jul 7, 2022
I think I'd rather wait for customer feedback. Or more than one opinion. We should discuss at standup. |
Most of the other options say 'Connect' as the first word. Maybe just 'Connect to a Remote Jupyter Server'? |
Suggestions:
|
26 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Issue identified by VS Code Team member as probable bug
notebook-remote
Applies to remote Jupyter Servers
verified
Verification succeeded
Using the most recent Insiders bits from July 1st.
The kernel picker now shows an option: "Connect To Your Own Jupyter Server". This seems a bit odd to me. It might not be MY Jupyer server, just A Jupyter server. So consider something like "Use Kernel On Existing Jupyter Server", instead.
The text was updated successfully, but these errors were encountered: