-
Notifications
You must be signed in to change notification settings - Fork 132
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
Adding milliseconds #64
base: master
Are you sure you want to change the base?
Conversation
ttyclock -s -m will show with milliseconds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this work at all? how fast is the refresh rate in ncurses anyways? can we really get ~10ms updates that do something here? it's not like humans can distinguish one milisecond to the next either. 10ms, maybe, but even that's a stretch...
not convinced this is worth it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, and i think you forgot to update the manpage. :)
Is there any problem here? |
https://stackoverflow.com/questions/3808626/ncurses-refresh this seems pretty helpful, ngl I would love milliseconds for maximum hackerman vibes lol |
yes, i have unanswered questions, see above. terminal latency is typically in the range of 10ms and up, and that's on a good day. i strongly doubt that we can show milisecond resolution, let alone have humans actually tell them apart. chronometers typically only show two significant digits after the second, and the second one flashes by so fast that you can rarely tell it apart. i'd say keep that to tenth of a second, and even then... i'm not sure i see the point. |
Very useful branch that should be merged into master. I used it to test the latency on a camera by recording the terminal and the streamed video. |
ttyclock -s -m will show with milliseconds