Marc Chamberlin said the following on 02/11/2011 12:56 AM:
..... an editor that failed to properly warn a user about embedded non-printing characters, a parser somewhere in autofs that failed to properly warn a user about embedded non-printing characters in a configuration file, a mount process that failed to tell the user that it could not perform it's task because it encountered those same non-printing characters, .....
Well, you were using a GUI. The command line version has STDIN, STDOUT an STDERROR streams Applications do complain - to the STDERROR stream that has no counterpart when you are using a GUI. Unless of course the GUI designer chooses to make the GUI very heavy and monitor all the error codes. But then perhaps the GUI designer chose not to write a wrapper around the CLI and instead, being a programmer, wrote it all in C, and found that checking all the return codes and interpreting the results and writing all the handlers and branching code was just too tedious and boring. Marc, you say you are a programmer. Do you ALWAYS check the return codes when subroutine and procedures are called, do you ALWAYS write the branching code and handlers for the results for each and every one at each and every level? By using the CLI and seeing the errors I learnt quickly. Of course you could have monitored the various files in /var/log -- Getting into a patent battle with IBM is right up there with starting a land war in Asia -- http://slashdot.org/~Don+Negro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org