i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Thu, 12 Mar 2015 17:39:42 +0000time keeping problem: i3status or py3status?https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/Since the change from standard time to daylight savings time (I have `/etc/localtime -> /usr/share/zoneinfo/EST5EDT`) this past weekend, my `i3status` (actually `py3status`) is still reporting standard time rather than DST. In a terminal, the `date` command reads EDT as it should so timekeeping itself handled the change correctly, but my status bar incorrectly shows standard time. My `~/.config/i3/config` reads in part: bar { status_command py3status -c ~/.config/i3status/config } And my `~/.config/i3status/config` reads in part: order += "ipv6" order += "disk /" order += "run_watch DHCP" order += "run_watch VPN" order += "wireless wlan0" order += "ethernet eth0" order += "battery 0" order += "load" order += "tztime local" I'm thinking that this reveals a subtle bug and I'd like to report it to the person whose code the bug resides in, but I'm honestly not sure which code is responsible. Is it `p3status` or part of `i3status` (I see `"tztime local"` in `man i3status`, but not sure if `py3status` is calling that code or if `py3status` reimplemented that code)? Can anyone shed some insight on this so I can file a bug with the project whose code has this problem?Tue, 10 Mar 2015 00:58:00 +0000https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/Answer by Ultrabug for Since the change from standard time to daylight savings time (I have <code>/etc/localtime -> /usr/share/zoneinfo/EST5EDT</code>) this past weekend, my <code>i3status</code> (actually <code>py3status</code>) is still reporting standard time rather than DST. In a terminal, the <code>date</code> command reads EDT as it should so timekeeping itself handled the change correctly, but my status bar incorrectly shows standard time. My <code>~/.config/i3/config</code> reads in part: <pre><code>bar { status_command py3status -c ~/.config/i3status/config } </code></pre> And my <code>~/.config/i3status/config</code> reads in part: <pre><code>order += "ipv6" order += "disk /" order += "run_watch DHCP" order += "run_watch VPN" order += "wireless wlan0" order += "ethernet eth0" order += "battery 0" order += "load" order += "tztime local" </code></pre> I'm thinking that this reveals a subtle bug and I'd like to report it to the person whose code the bug resides in, but I'm honestly not sure which code is responsible. Is it <code>p3status</code> or part of <code>i3status</code> (I see <code>"tztime local"</code> in <code>man i3status</code>, but not sure if <code>py3status</code> is calling that code or if <code>py3status</code> reimplemented that code)? Can anyone shed some insight on this so I can file a bug with the project whose code has this problem? https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?answer=5591#post-id-5591Hi @Gamonics. The bug certainly comes from py3status because it bases itself from the first i3status' time output but then handles it on its side. This is done because py3status needs to preserve a constant time tick when you have a different i3status and py3status interval (which is one of the point of py3status). So this involves some tricky datetime parsing which indeed must be lacking daylight savings time support. Usually an in-place restart of i3 should fix this problem right ? (mod+shift+R) I may have an idea as to how to get this fixed tho. If you have a github account, please open an issue on the py3status repository. Else tell me, I'll do it np. Hope this helps. PS: I'm the one behind py3status and yes it is a different project from i3statusTue, 10 Mar 2015 08:33:27 +0000https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?answer=5591#post-id-5591Comment by Ultrabug for Hi <a href="/users/24800/gamonics/">@Gamonics</a>. The bug certainly comes from py3status because it bases itself from the first i3status' time output but then handles it on its side. This is done because py3status needs to preserve a constant time tick when you have a different i3status and py3status interval (which is one of the point of py3status). So this involves some tricky datetime parsing which indeed must be lacking daylight savings time support. Usually an in-place restart of i3 should fix this problem right ? (mod+shift+R) I may have an idea as to how to get this fixed tho. If you have a github account, please open an issue on the py3status repository. Else tell me, I'll do it np. Hope this helps. PS: I'm the one behind py3status and yes it is a different project from i3status https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5602#comment-5602It's fixed and will be shipped in the next 2.4 release ! https://github.com/ultrabug/py3status/issues/75Thu, 12 Mar 2015 17:39:42 +0000https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5602#comment-5602Comment by Ultrabug for Hi <a href="/users/24800/gamonics/">@Gamonics</a>. The bug certainly comes from py3status because it bases itself from the first i3status' time output but then handles it on its side. This is done because py3status needs to preserve a constant time tick when you have a different i3status and py3status interval (which is one of the point of py3status). So this involves some tricky datetime parsing which indeed must be lacking daylight savings time support. Usually an in-place restart of i3 should fix this problem right ? (mod+shift+R) I may have an idea as to how to get this fixed tho. If you have a github account, please open an issue on the py3status repository. Else tell me, I'll do it np. Hope this helps. PS: I'm the one behind py3status and yes it is a different project from i3status https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5595#comment-5595True @Gamonics, I voted it up, thank you. Issue #75 on py3status github created.Wed, 11 Mar 2015 16:21:36 +0000https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5595#comment-5595Comment by Gamonics for Hi <a href="/users/24800/gamonics/">@Gamonics</a>. The bug certainly comes from py3status because it bases itself from the first i3status' time output but then handles it on its side. This is done because py3status needs to preserve a constant time tick when you have a different i3status and py3status interval (which is one of the point of py3status). So this involves some tricky datetime parsing which indeed must be lacking daylight savings time support. Usually an in-place restart of i3 should fix this problem right ? (mod+shift+R) I may have an idea as to how to get this fixed tho. If you have a github account, please open an issue on the py3status repository. Else tell me, I'll do it np. Hope this helps. PS: I'm the one behind py3status and yes it is a different project from i3status https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5593#comment-5593Probably easier for you to file the issue. Thanks for making py3status and for your quick answer. I didn't want to restart i3 until I could sort out where the bug was. So if it was a good question (revealed a bug), then perhaps consider up-voting my question. Q/A sites don't work unless people vote.Wed, 11 Mar 2015 05:05:45 +0000https://faq.i3wm.org/question/5590/time-keeping-problem-i3status-or-py3status/?comment=5593#comment-5593