The title text is the supposed moral to this story: if your user interface takes as long to operate as a command line, you may very well be denying your users the chance to get laid.
Disagree with the "in the time that he spends trying to solve the issue" bit. Problem solved, it was the further time taken to write up the documentation (man pages?) that ruined the day(/night).
Also: "if your user interface takes as long to operate as a command line". Inconsistent with the fact that the explanation starts off by assuming it is a command-line script. Also command-lines can be very quick (when not dealing with anything more complex than the stated problem) as long as you know what you want to do, which the given Cueball obviously did. I find that most window-based analogues take far more studying, for something as simple as the original problem. But YMMV on that one. 22.214.171.124 00:45, 22 June 2013 (UTC)
Sounds more like Cueball was still reading the documentation on HOW to script the pointer at the half hour mark. In other words, he was still researching what to do (not solved the problem yet) when she left. We don't know how long it took to actually solve the problem. 126.96.36.199 19:04, 4 September 2013 (UTC)
The actual problem in the strip doesn't require the hack suggested to solve. Instead you can simply use the xset command to disable DPMS and the screensaver: xset -dpms s reset
P.S. I didn't waste time figuring that out because of the strip, I discovered it out of necessity when building a display cluster. --Lokno (talk) 20:04, 9 January 2014 (UTC)
If he was smart he could have used some simple hardware fix. Assuming the wire is too short to just bring the mouse close to you (wireless mouses also have a range) you could use anything that moves a bit/vibrate to solve the issue. A smart guy would use their two phones, putting the mouse over one of the phones and using the second one to call it when the screen turns dark again. This is completely not overkill.Meneldal (talk) 06:31, 11 March 2015 (UTC)meneldal
The title "Command Line Fu" deserves an explanation, re: Google Fu. 188.8.131.52 (talk) (please sign your comments with ~~~~)
Only a hard core geek, would be researching hacks with an already naked date next to him... Mountain Hikes (talk) 04:39, 21 September 2015 (UTC)
I just wanted to mention that in ubuntu, the xdotools package makes mouse and keyboard scripting much easier than the comic depicts.
184.108.40.206 22:28, 11 April 2016 (UTC)
- Yeah, a simple `sh -c "while true; do xdotool mousemove_relative 0 1; sleep 200; done"` will do the trick. 220.127.116.11 18:46, 12 June 2016 (UTC)
Why does this say "The only hitch is that the interface is entirely text-based"? Unfortunately, that's not true. I first installed X on Linux when it was about a dozen raw-written floppies, in 1992. At that time it had nothing but Tiny Window Manager, and so you could argue that it was still text-based only, in a sense. But Nowadays many users stick almost purely to some X-based GUI. I, personally, prefer something like Arch Linux (I used Slackware for many years) running solely on the command line, no X except in extremis. But that's not the norm. — Kazvorpal (talk) 19:45, 10 October 2019 (UTC)