Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: 28 Sep 2001 13:10:10 -0000 Message-Id: Mime-Version: 1.0 Content-Type: text/plain Content-Disposition: inline From: danny AT ishiboo DOT com (Danny Dulai) To: cygwin AT cygwin DOT com Subject: strange behavior regarding new cygwin 1.3.3 and cmd.exe X-Mailer: Liam [version 0.7] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id f8S6AsN05113 I've been using a make replacement called Jam for a long long time under cygwin. I recently upgraded to everything bleeding edge as of tonight. Now when i type jam, i get each instantiation of CL.EXE (the vc++ cmdline compiler) and LINK.EXE (the vc++ linker) run with all its output in a brand new cmd.exe window. each CL.EXE and LINK.EXE invokation pops up a new cmd.exe window and when the cmd stops executing, it closes that new window it just popped up. I'm using the cygiwn xfree xterm + exceed as my X server. yesterday and before, when i typed jam, the CL.EXE and LINK.EXE output just came to the xterm and it worked as expected. now this output to the cmd.exe window makes looking at compiler errors impossible, and the effect just overall very annoying since windows are popping up and dying very quickly. below is the output from cygcheck -r -s -v thanks for any help. oh yah, since cygwin upgraded to vim6, ctags is gone. its no longer included in the vim pkg. could ctags be added to the apps in conjunction with vim6? -- _________________ danny AT ishiboo DOT com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/