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: #40reverse-branch
parent
516afbf9f9
commit
59f358fd0f
1 changed files with 1 additions and 1 deletions
Loading…
Reference in new issue