So I explain the confusion with the solution I used here on Github based on your example, so thanks for that.
When using this example session URL the password gets special characters encoded (i think is url-encoded)
So what I was originally asking was if entire session could have an option to be URL encoded the same way to avoid the issue. That seemed to cause some misunderstanding about my encoding comment.
Based on your example I made this bash solution to base64 encode the entire
So by doing this I don't get the error in windows terminal and I just base64 decode the output in my bash script.
This is what I wanted from my original comment but your PowerShell example just showed me how I could do it.
So thanks, I hope this clears the confusion and helps anyone else if they need it.
# @command cmd /c start "" %TERMINAL% "%EXTENSION_PATH%" "!U" "!@" "!#" !`bash -c 'base64 -w 0 <<< "!S"'` "!/" "!\" "%CDLOCAL%"
When using this example session URL the password gets special characters encoded (i think is url-encoded)
%241111111111111%40
sftp://username:%241111111111111%40;fingerprint=ssh-ed25519-FAKJn239KJFkj21040kPOKfpk2-094ijfjkIOKsj123@123.123.123.123/
So what I was originally asking was if entire session could have an option to be URL encoded the same way to avoid the issue. That seemed to cause some misunderstanding about my encoding comment.
Based on your example I made this bash solution to base64 encode the entire
!S
string instead of changing ;
to _
!`bash -c 'base64 -w 0 <<< "!S"'`
So by doing this I don't get the error in windows terminal and I just base64 decode the output in my bash script.
This is what I wanted from my original comment but your PowerShell example just showed me how I could do it.
So thanks, I hope this clears the confusion and helps anyone else if they need it.