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

Validation of configuration files (and VRL) on windows returns borderline unreadable output #22346

Open
nomalord opened this issue Feb 2, 2025 · 1 comment
Labels
platform: windows Anything `windows` platform related

Comments

@nomalord
Copy link

nomalord commented Feb 2, 2025

I noticed there is very heavy usage of BOM to make validation errors very clear and precise (and when it works it looks incredible), however, on windows, since BOM is not supported by default it's interpreted as garbage which makes the output errors is pretty unreadable...
I don't ask that you change how you output validations, however, I do ask that you specify in the docs how to overcome such hurdles:

Using any Linux terminals in windows, such as mingw
the jetbrains IDE terminal
(I believe) the windows terminal (the newest edition)

Places it doesn't work:
CMD
PowerShell console
Notepad
Notepad++
Jetbrains txt file interpretation

thanks in advance

P.S
I'm not currently near my PC, when I get home I'll add a few screenshots of the phenomenon 😁

@nomalord
Copy link
Author

nomalord commented Feb 3, 2025

found a screenshot i took
it's the same command for the same VRL, but in terminal it outputs he correct text, and in good old CMD it does not :(

Image

@pront pront added the platform: windows Anything `windows` platform related label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: windows Anything `windows` platform related
Projects
None yet
Development

No branches or pull requests

2 participants