-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Date formatted value doesn't work #1039
Comments
just curious, do they have same locale values like time zone, etc? isn't one's LC_TYPE=C and the other one's LC_TYPE=utf-8 or sth? |
I use Windows PowerShell, I understand that it is an environment variable, but I don't have it set on either computer, should I do it? Or can a lsd configuration level be solved? |
I think this problem might be related to how ‘lsd‘ creates the date time string using each user's locale, because from what i understand not all locales have am or pm (some might just have an empty string). And since your two computer was set up identically I was wondering if those env variables (windows language? Location? Windows version? Etc) were different by any chance. I'm not affiliated with this project at all but since I got curious I'll take a look. And it is highly likely that it has nothing to do with locale lol. |
Different implementations and libraries of C also might have undefined behavior regarding %P so make sure that the source and the version of your C is also same? Tho i don't think the problem would lie this deep |
Thanks for the interest, I check the region settings and they both have the same: I have also noticed in my screenshots that one shows some file different color such as README and LICENSE (where the date is not shown well) when it should be white |
lsd --version
: 1.1.2echo $TERM
: nothingecho $LS_COLORS
: no configuredActual behavior
I have installed in two pc's (same lsd version, same powershell version, same fonts, same configs, etc.), with the same date string config
date: "+%d-%m-%Y %I:%M %P"
in one return13-03-2024 12:13 pm
(I want) and in the other13-03-2024 12:13
(without pm or am)PC 1 (correct)
PC 2 (incorrect)
Expected behavior
Same date in two outputs.
The text was updated successfully, but these errors were encountered: