Originally created by @swebra on GitHub (Mar 3, 2025).
Eligibility
Individual Commercial Use License
Suggestion
As a dev, having quick reference of UTC is nice when dealing with UTC-based data. For someone working in a different timezone, having quick reference of local company time may also be useful.
A timezone field on the date/time bar widgets would be a nice QOL improvement for these use-cases, for example allowing the addition of a second non-local-timezone time to the bar.
Alternatives Considered
Not implementing and leaving the functionality for other bars.
IMO this request still fits under the "simplicity threshold" of the built-in bar, especially in comparison to features like the date CustomModifier.
Originally created by @swebra on GitHub (Mar 3, 2025).
### Eligibility
Individual Commercial Use License
### Suggestion
As a dev, having quick reference of UTC is nice when dealing with UTC-based data. For someone working in a different timezone, having quick reference of local company time may also be useful.
A timezone field on the date/time bar widgets would be a nice QOL improvement for these use-cases, for example allowing the addition of a second non-local-timezone time to the bar.
### Alternatives Considered
Not implementing and leaving the functionality for other bars.
IMO this request still fits under the "simplicity threshold" of the built-in bar, especially in comparison to features like the date `CustomModifier`.
This issue has been automatically closed until one of those pre-requisites can be validated.
@github-actions[bot] commented on GitHub (Mar 3, 2025):
Feature requests on this repository are only open to current [GitHub sponsors](https://github.com/sponsors/LGUG2Z) on the $5/month tier and above, people with a valid [individual commercial use license](https://lgug2z.com/software/komorebi), and approved contributors.
This issue has been automatically closed until one of those pre-requisites can be validated.
I think this should be possible by adding an optional timezone configuration option and trying to match a timezone using from_str_insensitive + https://crates.io/crates/chrono-tz, falling back to the local time if a valid tz can't be parsed from the config.
@LGUG2Z commented on GitHub (Mar 3, 2025):
I think this should be possible by adding an optional timezone configuration option and trying to match a timezone using `from_str_insensitive` + https://crates.io/crates/chrono-tz, falling back to the local time if a valid tz can't be parsed from the config.
I will also add some sort of suffix on the time widget, as it would be useful. 10:35 UTC or something like this
@CtByte commented on GitHub (Mar 3, 2025):
I will also add some sort of suffix on the time widget, as it would be useful. `10:35 UTC` or something like this
I think it makes a lot more sense use a formatting string instead of DayDateMonthYear and TwentyFourHour ... where did these come from??
@bilogic commented on GitHub (Aug 10, 2025):
I think it makes a lot more sense use a formatting string instead of `DayDateMonthYear` and `TwentyFourHour` ... where did these come from??
I think it's for users who do not want to play around with formats. Also, if you click on the clock, you can cycle between different presets.
These options are just different preset formats anyway.
@CtByte commented on GitHub (Aug 10, 2025):
I think it's for users who do not want to play around with formats. Also, if you click on the clock, you can cycle between different presets.
These options are just different preset formats anyway.
I think it's for users who do not want to play around with formats. Also, if you click on the clock, you can cycle between different presets.
Yea, but non of it let's me indicate timezone
@bilogic commented on GitHub (Aug 10, 2025):
> I think it's for users who do not want to play around with formats. Also, if you click on the clock, you can cycle between different presets.
Yea, but non of it let's me indicate timezone
@CtByte commented on GitHub (Aug 11, 2025):
It is true that the presets do not indicate timezone (they are in your local timezone). I would consider showing that to be for advanced users.
This is how it can be done if anyone interested:
```json
{
"Time": {
"enable": true,
"format": { "Custom": "%H:%M %Z" },
"label_prefix": "Icon",
"changing_icon": true,
"timezone": "US/Pacific"
}
},
{
"Time": {
"enable": true,
"format": { "Custom": "%H:%M %Z" },
"label_prefix": "Icon",
"changing_icon": true,
"timezone": "UTC"
}
},
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @swebra on GitHub (Mar 3, 2025).
Eligibility
Individual Commercial Use License
Suggestion
As a dev, having quick reference of UTC is nice when dealing with UTC-based data. For someone working in a different timezone, having quick reference of local company time may also be useful.
A timezone field on the date/time bar widgets would be a nice QOL improvement for these use-cases, for example allowing the addition of a second non-local-timezone time to the bar.
Alternatives Considered
Not implementing and leaving the functionality for other bars.
IMO this request still fits under the "simplicity threshold" of the built-in bar, especially in comparison to features like the date
CustomModifier.@github-actions[bot] commented on GitHub (Mar 3, 2025):
Feature requests on this repository are only open to current GitHub sponsors on the $5/month tier and above, people with a valid individual commercial use license, and approved contributors.
This issue has been automatically closed until one of those pre-requisites can be validated.
@LGUG2Z commented on GitHub (Mar 3, 2025):
I think this should be possible by adding an optional timezone configuration option and trying to match a timezone using
from_str_insensitive+ https://crates.io/crates/chrono-tz, falling back to the local time if a valid tz can't be parsed from the config.@CtByte commented on GitHub (Mar 3, 2025):
I will also add some sort of suffix on the time widget, as it would be useful.
10:35 UTCor something like this@bilogic commented on GitHub (Aug 10, 2025):
I think it makes a lot more sense use a formatting string instead of
DayDateMonthYearandTwentyFourHour... where did these come from??@CtByte commented on GitHub (Aug 10, 2025):
I think it's for users who do not want to play around with formats. Also, if you click on the clock, you can cycle between different presets.
These options are just different preset formats anyway.
@bilogic commented on GitHub (Aug 10, 2025):
Yea, but non of it let's me indicate timezone
@CtByte commented on GitHub (Aug 11, 2025):
It is true that the presets do not indicate timezone (they are in your local timezone). I would consider showing that to be for advanced users.
This is how it can be done if anyone interested:
@bilogic commented on GitHub (Aug 11, 2025):
@CtByte thanks that totally worked!