Difference between revisions of "Talk:196: Command Line Fu"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
Line 10: Line 10:
 
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.[[User:Meneldal|Meneldal]] ([[User talk:Meneldal|talk]]) 06:31, 11 March 2015 (UTC)meneldal
 
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.[[User:Meneldal|Meneldal]] ([[User talk:Meneldal|talk]]) 06:31, 11 March 2015 (UTC)meneldal
  
The title "Command Line Fu" deserves an explanation, re: Google Fu.
+
The title "Command Line Fu" deserves an explanation, re: Google Fu. {{unsigned ip|108.162.219.250}}

Revision as of 04:50, 29 August 2015

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. 178.98.31.27 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. 67.110.158.162 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. 108.162.219.250 (talk) (please sign your comments with ~~~~)