On Tue, Jul 30, 2013 at 01:52:05PM -0400, Tom Honermann wrote: >On 07/26/2013 01:58 PM, Tom Honermann wrote: >> On 07/26/2013 01:38 PM, Christopher Faylor wrote: >>> On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote: >>>> On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote: >>>>> On 7/25/2013 4:28 AM, Corinna Vinschen wrote: >>>>>> On Jul 24 22:38, Tom Honermann wrote: >>>>>>> My suspicion that this started with 1.7.21 is based on Corinna's >>>>>>> comments in http://cygwin.com/ml/cygwin/2013-07/msg00343.html and >>>>>>> other anecdotal evidence of new problems occurring as of that >>>>>>> release. >>>>>> >>>>>> This is by design now as described in the aforementioned posting. If >>>>>> you want to see the command line of a Cygwin application called by >>>>>> another Cygwin application, see /proc/$pid/cmdline. >>>>> >>>>> Would a patch to restore the previous operation based on a $CYGWIN >>>>> variable setting be acceptable? >>>> >>>> I actually had the same thought and have a patch waiting for Corinna's >>>> comment sitting in my sandbox. >>> >>> This is checked in. The CYGWIN environment variable keyword is >>> 'wincmdln'. >> >> Thank you, that is much appreciated. >> >>> 32 and 64 bit snapshots are uploaded. >>> >>> http://cygwin.com/snapshots/ >> >> I'll test (probably 32-bit only) and report if any problems appear. > >Tests passed, changes look good, thanks again. > >The upgrade guide [1] doesn't list the new keyword. Should I expect it >to be updated when 1.7.23 is released? > >[1]: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
Obviously we're not going to update the web page with a feature that doesn't work in the current release. http://cygwin.com/ml/cygwin-cvs/2013-q3/msg00039.html cgf -- 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
