You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Connect-Keeper in PowerShell on Linux: if your input is longer than the length of the terminal, the line is echoed back per character you enter (see image).
The main problem is when it asks for the SSO Token, which is 576 (?) characters. Pasting it in will cause a lot of echoing, which locks the terminal for a 5-10 seconds while it processes the output.
Screencast.from.2024-06-30.18-19-58.mp4
Specs
OS: RHEL 7 and Fedora 40
Terminal: Gnome terminal, Kitty, Putty and the terminal in Visual Studio Code
Powershell version: 7.3.12 and 7.4.3
PowerCommander: 0.9.10 and 0.9.11
This is not a problem on Windows, as far as I can tell.
The text was updated successfully, but these errors were encountered:
PSReadLine is installed by default in the PowerShell Core version of Powershell.
I'm not sure what you mean that PowerCommander uses PSReadLine to read the input, as PSReadLine doesn't have any functions that mimic "Read-Host". PSReadLine is designed to provide shell-like editing on the CLI, and MS hasn't implemented a way to use it to read input.
Well, it does have one, but it adds everything it reads into the shell history, which doesn't seem very secure.
When using Connect-Keeper in PowerShell on Linux: if your input is longer than the length of the terminal, the line is echoed back per character you enter (see image).
The main problem is when it asks for the SSO Token, which is 576 (?) characters. Pasting it in will cause a lot of echoing, which locks the terminal for a 5-10 seconds while it processes the output.
Screencast.from.2024-06-30.18-19-58.mp4
Specs
OS: RHEL 7 and Fedora 40
Terminal: Gnome terminal, Kitty, Putty and the terminal in Visual Studio Code
Powershell version: 7.3.12 and 7.4.3
PowerCommander: 0.9.10 and 0.9.11
This is not a problem on Windows, as far as I can tell.
The text was updated successfully, but these errors were encountered: