Yeah, I came across it a while ago, and figured I'd post it here when I ran watch today and viddy came up because I had aliased it when I came across it. I'm not sure how I haven't used watch since then but here we are.
It's been a while since I watched the movie, but in "A Clockwork Orange" IIRC they were a hallucinogenic (probably acid) to enhance the horror of what he was being forced to watch, to further traumatize him against the images of ultraviolence in a negative way. so that when he had the desire to carry out acts of ultraviolence after the 'treatment' he had flashbacks to the horrific visions he was subjected to. And being in eyedrops had the dual purpose of not letting his eyes dry out while he was unable to blink due to his eyelids being clamped open (this was a treatment, not a torture...)
I'd suggest logging to sqlite to provide later replays and speed estimations at keypoints. It might be nice to also add some cascading signature of the timestamps for tamper evidence (ex: merkle tree)
Usecase: storing timestamped proof of execution, automating metrics history
User story: "after feature X got implemented, deployment became twice as slow as we can see from the viddy logs".
For zsh you can create a global alias $=" " (I use $ because it is unlikely to be used anywhere but you can use anything and then just do watch $ myalias.
That used to be a lot easier when there was not that many tools out there. How many watch alternatives are there by now and how would you name them? watch, watchng, watch2?
The awesome go-cli package makes it trivial to generate man pages [1] based on the commands/flags. This can be easily added to CI to avoid having to maintain a separate man page.
Funny viddy came up here today. I created this note about watch in my dotfiles just yesterday (edit: probably not watch's fault! oops..):
> # TODO: this is ugly, doesn't print colours, is there a modern version?
I couldn't get watch to print colours and styles, with the -c switch and forcing colour output on the "inner" command.
Viddy just works and I've immediately created an alias to watch, and substituted all my scripted watch usage. The history feature looks interesting and potentially super-useful, and I'll hopefully remember that exists when I have need for such a thing. Thank you, and keep up the great work!
I didn't actually look for colour output for systemctl (yeah.. bad debugging, kinda lazy, but it wasn't very important so I didn't give it too much time). I thought I'd try to reproduce for you and thought I should have a quick look at colour output for systemctl, and came up with:
The lfs example still does not; I suspect it's probably ignoring the color arg depending on its environment (I wonder if watch changes the env?- not to imply it would be wrong to do so if so).
I feel a bit bad for making it look like this was watch's fault, when it probably isn't. I'll dig into the lfs thing later.
31 comments
[ 3.3 ms ] story [ 76.3 ms ] threadI see its in nixpkgs - think I'll alias it to watch right now
It's not on-par with `watch` feature-wise. (-e and -g are not implemented)
Cool tool btw.
Looks like a golang gopher getting eye drops while being injected with syringes.
Usecase: storing timestamped proof of execution, automating metrics history
User story: "after feature X got implemented, deployment became twice as slow as we can see from the viddy logs".
Would be an interesting feature to see here for recording, and can then be played back/analysed by various other tools.
[1] https://en.wikipedia.org/wiki/Ttyrec
Thank you!
IIRC this doesn't work in bash.
I'm a bit annoyed at the trend of not having man pages though.
That used to be a lot easier when there was not that many tools out there. How many watch alternatives are there by now and how would you name them? watch, watchng, watch2?
[1]: https://pkg.go.dev/github.com/urfave/cli/v2#App.ToManWithSec...
I've been busy and haven't been very active, but I'm trying to resume maintenance. If you have any requests, please mention them in GitHub Issues.
> # TODO: this is ugly, doesn't print colours, is there a modern version?
I couldn't get watch to print colours and styles, with the -c switch and forcing colour output on the "inner" command.
Viddy just works and I've immediately created an alias to watch, and substituted all my scripted watch usage. The history feature looks interesting and potentially super-useful, and I'll hopefully remember that exists when I have need for such a thing. Thank you, and keep up the great work!
> watch -c -n 1 -- systemctl --user --state=failed
> watch -c -n 1 -- lfs --color yes -c +inodes_use_percent
I didn't actually look for colour output for systemctl (yeah.. bad debugging, kinda lazy, but it wasn't very important so I didn't give it too much time). I thought I'd try to reproduce for you and thought I should have a quick look at colour output for systemctl, and came up with:
> watch -c -n 1 -- SYSTEMD_COLORS=1 systemctl --user --state=failed
which works well.
The lfs example still does not; I suspect it's probably ignoring the color arg depending on its environment (I wonder if watch changes the env?- not to imply it would be wrong to do so if so).
I feel a bit bad for making it look like this was watch's fault, when it probably isn't. I'll dig into the lfs thing later.