-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
History is full of "nothing has changed" entries #41
Comments
Same problem |
Hi, @TonyStark @leapfog If you guys can provide a gif/video or some steps to reproduce. I'm giving an example and tell me if it's correct. When I watch |
however i left that project which i used viddy to watch data. |
@coolabhays yes that's exactly my usecase. Or a perfect example for my problem. I want to know what and when changed. But when the delay is to small, the history is full of "$timestamp +0 -0" (and only one or two really interesting "real" changes, which then are difficult to scroll to) and when the delay is huge, I cannot see when changes really happened. So I'd prefer just not to add entries to the history unless there really was a change in the output. |
You can check out https://github.com/blacknon/hwatch. It's less polished than |
Has anyone tried sending a PR? |
I've commited the initial change. I am also noticing the occasional flickering issue. It's possible that I may have to do more changes in the source code compared to what I would've liked. Anyways, test this, and see if this is the intended behavior. I'll try to fix it more (if possibly needed) when I'll get some time again |
I'll probably get back to it, but just in case I don't, avamsi@c62b260 seems to be working okay (i.e., the keyboard shortcuts and all) but there seems to be an off by one selection bug (on history update). |
Thanks for fixing this. |
I'm watching long running processes that change their output at not foreseeable times. So my History is filled with lots of "$timestamp +0 -0" entries. Can viddy be configured to not create these "nothing has changed" entries?
The text was updated successfully, but these errors were encountered: