On 2019-08-30 21:58, Brian Inglis wrote: > Not being in the same Cygwin process group and lacking the appropriate > interface > info indicates that the invoker was not Cygwin.
Should I interpret this to mean the "winshell" parameter is not an accurate statement of what I thought it was for and because there is no way to reliably determine if the calling process was from Cygwin or not, behavior like I suggest is actually impossible? -- 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
