This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
It's not nonsense. It's 100% accurate. What in my statement above is not the truth?This is nonsense and you know it.There was an error message that cmd showed that bash did not. To me that's suppression.
Right, that's makes it the implementors problem, plumbing and mechanics are implementation details - not the users...Plumbing and mechanics is the way to solve the problem.It's not that the OS generates an error message and cmd lets it slip through while Cygwin (or bash) "suppress" it. It's the CreateProcess call which generates an error code ERROR_SXS_CANT_GEN_ACTCTX and cmd printing the connected error message, just like bash gets an error code EACCES and prints the connected error message "Permission denied".Plumbing and mechanics aside, I'm just saying the user should be told the underlying problem. If ERROR_SXS_CANT_GEN_ACTCTX is the error code could ya at least print that as a string? It would give the user a fighting change and finding a solution...
"We" are not finding a solution. "You" might be. "I'm" just reporting the problem. Now, does everybody have their roles straight? ;-)If you don't want to leave the user-only perspective, we will have a hard time to find a solution.
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |