You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened: When using a type "display" module and setting a custom format including {3} (refresh rate), the refresh rate is printed with full precision while preciseRefreshRate is set to false.
What should happen: The refresh rate should take into account preciseRefreshRate and round to the nearest integer like normal even when a custom format is set.
Fastfetch version used: 2.20.0
Did it work in an older version: no
Where did you get the binary: installed via NixOS
Does this issue still occur in the latest dev build? Afaik yes, because the issue is with this line, which takes the refresh rate value directly and passes it into a formatter:
I suppose this wouldn't really be an issue if it were possible to specify the decimal place precision in the format directly, but fastfetch -h format only provides options for truncating strings, which isn't practical as the whole number parts of refresh rates can be 2 or 3 digits long. I've tried a few other format codes I know from other languages but they have not worked.
Screenshot:
The content of the configuration file you use (if any):
General description of bug:
{3}
(refresh rate), the refresh rate is printed with full precision while preciseRefreshRate is set to false.fastfetch/src/modules/display/display.c
Line 146 in 788cad3
I suppose this wouldn't really be an issue if it were possible to specify the decimal place precision in the format directly, but
fastfetch -h format
only provides options for truncating strings, which isn't practical as the whole number parts of refresh rates can be 2 or 3 digits long. I've tried a few other format codes I know from other languages but they have not worked.Screenshot:
The content of the configuration file you use (if any):
Output of
fastfetch --list-features
:The text was updated successfully, but these errors were encountered: