Open miguno opened 3 months ago
I did find a semi-related issue for wezterm, but as far as I can tell the issue I describe above is different.
Wow. Thanks for the super detailed issue! 🎉 :+1:
I am currently at a loss regarding the origin of this. If Credo can change anything to mitigate this issue, we will 😀
Precheck
Environment
mix credo -v
): 1.7.6-ref.main.a3c8308+uncommittedchangeselixir -v
):zsh
Terminal environment:
My terminal (wezterm) with the font I use (Iosevka) does support the respective arrow Unicode characters:
Lastly, even with a "fresh" wezterm setup of all defaults (via
wezterm -n
) shows the same behavior:credo
output has raw Unicode sequences, whereas other uses of the same Unicode characters (e.g. viaiex
or manually typed) do render correctly.What were you trying to do?
I want to run a basic credo report with
mix credo --strict
and see correctly formatted output.To make it easier to summarize the issue in this discussion, I also include the expected vs. actual output for the following
credo
command line:FWIW it didn't matter whether or not I added
--no-color
to the commands.Expected outcome
I expected that the priority indicator arrows (like → or ↗) would be printed to the terminal, note the left-hand side of the output, right next to where the categories like
[R]
and[D]
are printed.Actual outcome
Instead, the raw Unicode sequence were printed.
Here is more verbose output:
As you can see, the priority-indicating arrows as well as further Unicode sequences are actually printed as
\x{2192}
etc.en_US.utf-8
.Have you come across this before? I have not found any clearly related issue in the open or the closed GH issues.