Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro References: <3F1EC726.5040609@cygwin.com> From: jeff.rancier@softechnics.com (Jeffery B. Rancier) Date: Wed, 23 Jul 2003 15:14:27 -0400 In-Reply-To: <3F1EC726.5040609@cygwin.com> (Larry Hall's message of "Wed, 23 Jul 2003 13:34:30 -0400") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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. -- 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/