We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[schwarzgerat](1) $ ./notcurses-tester -tc=Metric -p ../data/ Running with LANG=C Running with TERM=xterm-kitty Detected cell geometry: 132x64 [doctest] doctest version is "2.4.11" [doctest] run with "--help" for options =============================================================================== /home/dank/src/dankamongmen/notcurses/src/tests/metric.cpp:24: TEST CASE: Metric NegativePowersOfTen /home/dank/src/dankamongmen/notcurses/src/tests/metric.cpp:442: FATAL ERROR: REQUIRE( ncqprefix(val, 1000000000000000ull, buf, '\0') ) is NOT correct! values: REQUIRE( nullptr ) =============================================================================== [doctest] test cases: 1 | 0 passed | 1 failed | 45 skipped [doctest] assertions: 581 | 580 passed | 1 failed | [doctest] Status: FAILURE! [schwarzgerat](1) $
this is causing us trouble in pbuilder and should obviously be fixed either way.
pbuilder
The text was updated successfully, but these errors were encountered:
confirmed it works fine with LANG=en_US.UTF-8.
LANG=en_US.UTF-8
Sorry, something went wrong.
as predicted, this has to do with µ being pulled from subprefixes, meaning we're using UTF8_SUBPREFIX rather than ASCII_SUBPREFIX.
subprefixes
UTF8_SUBPREFIX
ASCII_SUBPREFIX
yep we're calling into ncmetric_use_utf8_internal()
ncmetric_use_utf8_internal()
oh christ
fixed, incoming, stupid
73a7190
so we were testing utf rather than *utf8, which was always true, and thus always enabling utf8 for ncmetric.
utf
*utf8
ncmetric
dankamongmen
No branches or pull requests
this is causing us trouble in
pbuilder
and should obviously be fixed either way.The text was updated successfully, but these errors were encountered: