X-Spam-Check-By: sourceware.org Message-ID: <2fc802c00602070224p75fcd880nd63eb35928a04a06@mail.gmail.com> Date: Tue, 7 Feb 2006 10:24:26 +0000 From: David Picton To: Igor Peshansky Subject: Re: strange cygstart bug with current Cygwin versions Cc: cygwin AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <2fc802c00602031305p7574f255g5e67e44cd8b754e AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k19GPqc1018912 On 2/3/06, Igor Peshansky wrote: > On Fri, 3 Feb 2006, David Picton wrote: > > > I have encountered a strange bug when starting Microsoft Word when it is > > started by the cygstart command, e.g. "cygstart Index.doc", with the > > current version of the Cygwin dll. > > > > The symptoms are as follows: [snip] > > 3. Attempting to save the file gets no response. The only way to close > > the window is to exit without saving! I have now tested 'cygstart cmd' on the three computers I use, and in every case I see the same problem with the TEMP and TMP environment variables - they retain the Cygwin pathname (regardless of whether this actually causes a problem with Word). For now, I've caused TEMP and TMP to be set to a Windows pathname within Cygwin. I don't see the bug if I run an older version of Cygwin (pre-2006 versions of the Cygwin DLL). TEMP and TMP used to be translated correctly in processes invoked by cygstart. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/