-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
SSH handler #6656
Comments
I mean it seems a lot easier to just do win+r |
@zadjii-msft except it seems less seamless If Terminal had this capability then it can probably register itself as a protocol handler for Windows as well so if we click on a link that looks like ssh://[email protected] it will start up terminal |
I created a small launcher script and protocol registry entries to do exactly this. https://github.com/vbyrd/windows-terminal-ssh-protocol-handler |
Thanks @vbyrd! Yeah -- in general, I think this is something the community is better-equipped to handle than us. Registering a protocol handler, especially by default like that, is something that I'd like the user to explicitly opt into. At the same time, I'm not liable to put too many ssh-specific features into Terminal itself. If anything, it would be part of the extension that /dup #1280 turns into. |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Description of the new feature/enhancement
I'd like to do something like
WinR
wt [email protected]
Enterand it will start up or open an new tab in an existing Windows Terminal that will perform an SSH connection.
Proposed technical implementation details (optional)
Note this request is NOT to embed SSH itself to Windows Terminal, but provide some sort of generic handler for command lines with a username@host pattern along with ://@:/ pattern the protocol and ports should be defaultable (in my case if I had the configuration I would default to
ssh
since I generally work with that.I was thinking it will be a
profile
that if not hidden will ask for a URL if selected and the "command" allows for extra fields that would be used to pass in the componentsNote I used
uri.
to prefix it so we don't pollute the default namespace.The text was updated successfully, but these errors were encountered: