-
Notifications
You must be signed in to change notification settings - Fork 131
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
tty-clock is late #40
Comments
|
for the record:
i'll send a pr to fix this. :) with the patch, the display is more consistent with xclock and friends. |
anarcat
added a commit
to anarcat/tty-clock
that referenced
this issue
Jan 13, 2017
the way this was working before, we would populate the ttyclock->lt field *after* fetching the ttyclock->tm structure, which means that would get the `localtime` of the *previous* iteration. this created a one second delay in the clock display that was, I believe, unintentional. this accounts for part of the 2s delay when compared to other clocks like vtclock or xclock. Closes: xorg62#40
|
should be fixed in #41 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When compared with other software, tty-clock seems actually to run one or two seconds late.
In the above screenshot, 4 clocks are running, from top to bottom:
xclock -d -update 1vtclock -v -3(nothing special about those flags, just a nicer font)tty-clock -sNote that we don't see it in the screenshot, but xmobar is actually lagging a little behind the other two clocks, say about 500ms. Here's a screencast that shows the behavior more precisely.
I find it mind-boggling that 4 clocks can't agree on the time on my computer, this gotta have some profound meaning involving long hair and swiss patent offices, but i am not certain... ;)
The text was updated successfully, but these errors were encountered: