> aah. this is because /bin/sh returns 127 If the command is not found. it looks > like ld.so also exist with 127 if shared lib linking doesn't work - so we have > no way to really knwo exactly what the error was - other than there was an > error runinbg the application. the message was based on the sh return of the > command not being found. i don't think we are likely to catch and log/parse > the > stdout/stderror of all programs launched to try figure out the errors (not to > mention parsing them is nigh impossible as the errors will get translated > based > on locale - so we need different parsers based on each translation locale for > the system... not going to happen. even if we just capture and log (up to the > first N lines of output - whihc we can actually do how with fork & pipe (we > need to be able top handle stderror though... that could be a useful addition) > we could just display whatever the process spweds out in a dialog - but even > then it may not make a lot of sense...). >
then, just patch message: Enlightenment was unable TO run OR LINK the program ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
