41–50 of 52 posts
Implementation for Linux: #!/bin/bash set -e while true; do sleep 20m xlock -allowaccess& pid=$! sleep 20s kill $pid done Check the manpage for xlock and choose a screensaver that won't keep you looking at the monitor.
There is also a Chrome App called Eye Care. It has slightly more flexibility and runs on Win/Mac/Linux https://chrome.google.com/webstore/detail/eye-care/ingonfahm... +1 for f.lux
On the topic of eye strain. For anyone not familiar with f.lux, highly recommend you check it out. Everyone that I have recommended it to so far loves it. https://justgetflux.com
I recommend f.lux too. The only problems I've encountered with it are: - doesn't take into account wacky sun hours in nordic countries during winter, I get around this by setting my location to be somewhere else - isn't able to automatically detect when I'm playing a fullscreen videogame, when I would prefer it automatically switch off
On the topic of eye strain. For anyone not familiar with f.lux, highly recommend you check it out. Everyone that I have recommended it to so far loves it. https://justgetflux.com
Is anyhthing known about the internals of it, i.e. what code does it use? Something like SetDeviceGammaRamp on Windows? Or does it talk directly to the video card driver (if that is even possible in a generic way)? Or the monitor? Does it still work reasonably if I already have set my display to low brightness etc? edit also wondering: it cannot know if I'm sitting in a completely dark room, a sunlit room or a room a…
Earlier quoted context omitted.
I hate HN lately. Now you can get downvoted for your personal experience. Take my upvote.
He probably got downvoted for messing up the technical terms as castell and geococcyxc pointed.
Implementation for Linux: #!/bin/bash set -e while true; do sleep 20m xlock -allowaccess& pid=$! sleep 20s kill $pid done Check the manpage for xlock and choose a screensaver that won't keep you looking at the monitor.
Implementation for Linux: #!/bin/bash set -e while true; do sleep 20m xlock -allowaccess& pid=$! sleep 20s kill $pid done Check the manpage for xlock and choose a screensaver that won't keep you looking at the monitor.
#!/usr/bin/env bash
set -e
while true; do
sleep 20m
xscreensaver-command -activate
sleep 20s
xscreensaver-command -deactivate
done
Is this even usable as a developer? Seems it'll be annoying for something to break my concentration every 20 minutes, losing my flow all the time.
Implementation for Linux: #!/bin/bash set -e while true; do sleep 20m xlock -allowaccess& pid=$! sleep 20s kill $pid done Check the manpage for xlock and choose a screensaver that won't keep you looking at the monitor.
I accidentally did something similar quite a few years ago when I stupidly set up a grep to run updatedb every two hours. There was several months lag as well between when I did that and my computer started locking up every two hours for a few minutes. And embarrassingly, it took me a week or two to put it together.