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

Default SessionId #120

Open
mvoidex opened this issue Nov 21, 2016 · 2 comments
Open

Default SessionId #120

mvoidex opened this issue Nov 21, 2016 · 2 comments

Comments

@mvoidex
Copy link

mvoidex commented Nov 21, 2016

Thanks for this module.

Wouldn't it be useful to have 0 as default SessionId for most of cmdlets?

@darkoperator
Copy link
Owner

It is something I have thought about based on used by users, The module is not meant for use in a interactive shell but for automation of SSH tasks but it seems many people use it interactively.

On Nov 21, 2016, at 10:38 AM, Alexandr Ruchkin notifications@github.com wrote:

Thanks for this module.

Wouldn't it be useful to have 0 as default SessionId for most of cmdlets?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #120, or mute the thread https://github.com/notifications/unsubscribe-auth/AAf0Hmi-L9pnm7qhdLXkTdMxA5pNAC9mks5rAazMgaJpZM4K4Rdc.

@darkoperator
Copy link
Owner

I would need to do some major refactoring after playing with one of the cmdlets, so the option would not mandatory, it would need to check if we have one or more sessions, select the first one from the list since 0 may be not there and provide a proper error if there are more than one, if there are none, a verbose print saying which one was select. All of this for compiled cmdlets in C# and PowerShell. it would be a nice PR ;)

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