X-Spam-Check-By: sourceware.org Date: Mon, 30 Jan 2006 11:10:50 -0500 (EST) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Dave Korn cc: cygwin AT cygwin DOT com Subject: RE: Cygwin Bash window disappear?! In-Reply-To: <019501c625b6$a26d8580$a501a8c0@CAM.ARTIMI.COM> Message-ID: References: <019501c625b6$a26d8580$a501a8c0 AT CAM DOT ARTIMI DOT COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 30 Jan 2006, Dave Korn wrote: > On 30 January 2006 15:54, Igor Peshansky wrote: > > > On Mon, 30 Jan 2006, Dave Korn wrote: > > > >> On 28 January 2006 04:19, Daniel mark wrote: > >> > >>> Hello Eric: > >> > >>> ////////////////////////////////////////////// > >>> Cygwin Configuration Diagnostics > >> > >>> Path: C:\Program Files\texmf\miktex\bin > >> > >>> Path = 'C:\Program > >>> Files\texmf\miktex\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\Sys > >>> tem32\Wbem; > >> > >> First thing to try is to get rid of all those clashing > >> win32-versions of *nix apps from your %PATH% and re-run setup. > > > > Huh? Since when does MikTeX conflict with Cygwin? > > I could see the included makeinfo interfering with > /etc/postinstall/update-info-dir.sh. And people are always complaining > about seeming-hangs in setup at the post-texmf.sh script. update-info-dir.sh doesn't use makeinfo. Besides, postinstall scripts should not rely on the path containing /bin -- they should use explicit paths (or else set the PATH themselves). Plus, I believe setup prepends /bin to the PATH before running the scripts. post-texmf.sh regenerates all of the binary LaTeX format files -- it's *supposed* to take a long time, especially with slower disks. Perhaps it should be renamed to "post-texmf-THIS-MAY-TAKE-A-WHILE.sh" (so people at least get a visual clue in setup)? :-) > > We still haven't gotten the exact error message that the OP gets when > > running c:\cygwin\Cygwin.bat from a CMD window. Igor > > Yep, we don't have enough information to diagnose the problem yet, > that suggestion above was only a suggestion for something to try. Well, let's hope this doesn't take the OP off on a tangent and make him forget to actually post some useful output. :-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/