Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 23 Jul 2003 18:40:38 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Jeffery B. Rancier" cc: cygwin AT cygwin DOT com Subject: Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro In-Reply-To: Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 23 Jul 2003, Jeffery B. Rancier wrote: > Larry Hall writes: > > > It's not a bug, unless you consider a Windows program not being able to > > understand Cygwin symbolic links a bug. I don't think there is much > > chance of changing Windows to permit all applications a proper understanding > > though. > > I see. Why does it work at all, then? I renamed my emacs version of > etags to ensure that I was running cygwin's. > > > I'm surprised you don't see this all of the time when invoked in NTEmacs. > > Regardless, it would never work, even if it doesn't complain. Use > > Cygwin's emacs, ctags directly, or some emacs lisp wizardry to resolve > > this issue. > > First time I've ever seen it is three years. What you could do is create an "etags.bat" that runs 'bash -c etags "%1" "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"', put it in your PATH, and you should be able to call that from NTEmacs. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/