On Sat 29 Jul 2017 at 07:57:49 (-0700), Patrick Bartek wrote: > On Fri, 28 Jul 2017 22:08:41 -0500 David Wright > <deb...@lionunicorn.co.uk> wrote: > > > On Thu 27 Jul 2017 at 14:18:47 (-0700), Patrick Bartek wrote: > > > > On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote: > > > > > Or do what I did: dispense with a screensaver entirely. Haven't > > > > > used one in years. Waste of CPU cycles. Besides modern > > > > > computer screens don't even need them anymore. They aren't > > > > > prone to image burning like tube-type monitors were. I just > > > > > use xset or a power management utility, if installed, to > > > > > "sleep" the monitor display after a set time of system > > > > > idleness. Works great. > > > > […] > > > > > I lock my screen manually, too. Much of my work involves studying > > > what's on the screen without any input. It's an annoyance when it > > > "blanks" and I have to log back in disrupting my train of thought. > > > > As you use xset, can't you just define a key to set a really long > > timeout like xset dpms 9000 9000 9000 ; xset s 9000 9000 > > to prevent it blanking? (And one to revert if you feel the need.) > > I set xset for 20 minutes . . . 12000.
(That's 200 minutes.) > Works well 98% of the > time. Never looked at the s option. That could be your problem then. > But it looks like it's for > overridding a screensaver which I don't use or even have installed. I believe X has a screensaver built in. From man xset s The s option lets you set the screen saver parameters. You can check it out by typing xset s 5 5 > I > still prefer to lock the screen manually though, if I'm going to be > away for a while. Same here; I use vlock -a in a VC. Cheers, David.
