allow spawning a shell after kitten ssh exit first step - #8807
allow spawning a shell after kitten ssh exit first step#8807barr-israel wants to merge 1 commit into
Conversation
|
You need to add it to options_spec() in kitty/launch.py and implement it in the _launch() function |
|
Once you are happy with your implementation please squash it down to one commit and force push, then I will review. |
|
it was already implemented in _launch when you made that comment, but i have now added it to options_spec and LaunchKwds and the build still fails, Ill keep investigating |
|
You need two blank lines before --ssh-spawn-shell |
|
Thanks, it seems to be working now. |
|
No, this functionality is pretty simple, it shouldnt need tests.
|
f6693d1 to
ca2232e
Compare
|
…itten ssh disconnection new option to the launch command, the new shell will be in the directory that launched kitten ssh
ca2232e to
55c51aa
Compare
|
fixed a ruff lint error |
|
merged. |
|
Great, thanks for all the help |
I have successfully gotten the behavior I wanted in #8806 , but I am having trouble adding a flag for it, this fork currently does not build due to
After adding
ssh_spawn_shellto the launch.pyprotocol_spec.I have also added it to
clone_safe_optsexpecting it to be necessary.Additionally, there is a little parameter drilling here from
launchtomodify_argv_for_launch_with_cwdthat im not sure if I can avoid.When this is resolved I will add the same flag to new_windows and its variants
Any help would be appreciated