Weird characters in place of terminal escape sequences on Windows Console #474
Comments
BuriedInTheGround
added a commit
to BuriedInTheGround/age
that referenced
this issue
Dec 26, 2022
If possible, we enable virtual terminal processing, which is necessary for using terminal escape sequences on instances of the Windows Console. When enabling virtual terminal processing fails, we completely avoid using escape sequences to prevent weird characters to be printed to the console. Fixes FiloSottile#474
FiloSottile
pushed a commit
to BuriedInTheGround/age
that referenced
this issue
Apr 22, 2023
If possible, we enable virtual terminal processing, which is necessary for using terminal escape sequences on instances of the Windows Console. When enabling virtual terminal processing fails, we completely avoid using escape sequences to prevent weird characters to be printed to the console. Fixes FiloSottile#474
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
What were you trying to do
I was trying to encrypt a file with a passphrase.
What happened
On both Windows PowerShell and cmd.exe, terminal escape sequences do not work by default. As a result, I obtained the following output, containing weird characters on screen.
As a side note, I actually discovered this issue while trying to use the same functions as yours to ask for a passphrase. I strongly believe that this behavior is present since the introduction of escape sequences in 349ed5e. This commit post-dates age version v1.0.0, so it may be the case that not many people have encountered this issue, but I think that it would negatively impact the UX for Windows users from now on (indeed, v1.1.0 and v1.1.1 just came out).
I'm going to make a PR to address this issue as a follow-up.
P.S.: sorry for not disclosing this issue before the v1.1.0 release, I didn't see it coming!
The text was updated successfully, but these errors were encountered: