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

In Shell-Mode: Use the connection as active context per default and add ability to switch contexts #44

Closed
gitseti opened this issue Aug 23, 2019 · 0 comments
Assignees
Labels
feature New feature

Comments

@gitseti
Copy link
Contributor

gitseti commented Aug 23, 2019

After connection in the shell mode the user should be act in the current context per default

Input
sh>con -h myHost.com -p 1884
Result

  • client is connected and the prompt is working with that client as the active context:
    sh-ClientID@host>

The user should be able to switch between contextes and leave a context (without disconnect)
Input
sh-ClientID@host> switch_context -i 'other-id' -h 'other host'
sh-ClientID2@host2>

Input
sh-ClientID@host> leave_context
sh>

If working in a specific context

  • the pub and sub command should not be extended from connect and use always the connection of the active context.
    (naming pub / sub should be the same )
  • during active context another conn command should not possible
@gitseti gitseti added the feature New feature label Aug 23, 2019
@gitseti gitseti self-assigned this Aug 23, 2019
@ahelmbr ahelmbr changed the title In Shell-Mode: the last connected client should be used by default for following commands In Shell-Mode: Use the connection as active context per default and add ability to switch contexts Aug 26, 2019
@gitseti gitseti closed this as completed Sep 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

1 participant