At Sat, 9 Jul 2011 02:55:32 +0800 CentOS mailing list centos@centos.org wrote:
On 7/9/11, John R Pierce pierce@hogranch.com wrote:
On 07/08/11 10:20 AM, Emmanuel Noobadmin wrote:
...does[n't] stop him from doing development, it shouldn't stop him from doing something like copy and paste.
A couple weeks ago, on a technical support IRC forum (I forget if it was #solaris or #postgres or what), some guy came on and wanted us to look at an error.... which he posted as a YOUTUBE VIDEO. it was a simple 2-3 line text error message. apparently it was easier for him to use his fondleslab[1] to video capture the error off his screen than to paste or type the text. talk about bandwidth bloat.
On a similar note, I regularly request users to copy the error message they get in order to troubleshoot. There's this group of customers who, despite repeated instructions, will do a screenshot and email a .BMP to me. I'm undecided if that's better or worse than their previous method of printing out said screenshot, then scanning it via their copier's scan to email function before emailing the now crap quality monochrome final product to me as a PDF.
But neither beats that youtube for bloat :D
I don't believe it is possible to copy and paste the text from many error message popups (I am pretty certain you can't from a standard MS-Windows error popup, but I am not sure about error popups from various Linux GUI toolkits -- *some* of them don't allow it -- the base widgets used don't provide a copyable text field). So the only way to *litterally* 'copy and paste' the error message (and some people understand the 'error message' to be the error popup window, not the *text* of the message) is to litterally do a screenshot of the popup window and send that. I guess far too many people have been trained away from textual interactions with a computer -- they only understand *graphical* interaction with a computer.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos