Skip to content
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

Cmder console 'hijacked' after running 'start-ssh-agent' #2050

Closed
1 of 3 tasks
pixelbrad opened this issue Feb 27, 2019 · 3 comments
Closed
1 of 3 tasks

Cmder console 'hijacked' after running 'start-ssh-agent' #2050

pixelbrad opened this issue Feb 27, 2019 · 3 comments

Comments

@pixelbrad
Copy link

Purpose of the issue

  • Bug report (encountered problems/errors)
  • Feature request (request for new functionality)
  • Question

Description of the issue

Hello, not quite sure where to post my concerns, so I'm sorry if this is the wrong place. Just need a little guidance.

Whenever I execute start-ssh-agent in Cmder, it seems like the console gets 'hijacked' by another console. Here's an example of my situation:

C:\Users\Brad
λ start-ssh-agent
Found ssh-agent at 6752
Found ssh-agent socket at /tmp/ssh-GYaVEG9e6nDE/agent.18340
Microsoft Windows [Version 10.0.17134.556]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Brad>

Prior to executing start-ssh-agent, I'd be entering commands beside the lambda symbol (one line under my CWD), and my CWD is a nice green colour. After executing start-ssh-agent, all of my commands are entered after C:\Users\Brad> on the same line, and all my console text is the same colour.

I can get out of this by simply executing exit, and them I'm brought back to the standard Cmder console, complete with colours. I can add my SSH keys in either situation, but I much prefer using the default Cmder console. Example of coming back to the standard Cmder console:

C:\Users\Brad
λ start-ssh-agent
Found ssh-agent at 6752
Found ssh-agent socket at /tmp/ssh-GYaVEG9e6nDE/agent.18340
Microsoft Windows [Version 10.0.17134.556]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Brad>exit

C:\Users\Brad
λ

Ultimately this isn't a game-breaking issue or anything like that. Just a matter of preference I guess? Can someone help me determine what exactly is going on here?

To answer some questions I'm confident I'll be asked:

  • I'm using Windows 10 Enterprise, build 1809.
  • I do not have Microsoft's OpenSSH client installed (Settings app -> Apps & Features -> Manage optional features)

Please let me know if any additional information is required. I appreciate any help with this concern!

@daxgames
Copy link
Member

daxgames commented Mar 1, 2019

Have a look at #1807 and #1781

@daxgames daxgames closed this as completed Mar 1, 2019
@pixelbrad
Copy link
Author

Thank you

@daxgames
Copy link
Member

daxgames commented Mar 1, 2019

or call "%GIT_INSTALL_ROOT%/cmd/start-ssh-agent.cmd" /k exit is what current versions of cmder has in user_profile.cmd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants