X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 16 Jun 2008 19:11:33 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Problem with tags in vim 7.1 Message-ID: <20080616171133.GG731@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <485698AD DOT 9000302 AT ptc DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <485698AD.9000302@ptc.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Jun 16 09:45, Alex Shturm wrote: > Corina, s/Corina/Corinna/ http://cygwin.com/acronyms/#TOFU > Unfortunately generation of tags is beyond my control. They are using Case 1 works if the path is given as POSIX path. Since you have your own environment under control, you shuld simply set the variable to a POSIX path rather than a DOS path. All three cases work when using the latest Cygwin from CVS, but that's not somthing to be used lightly in production ennvironments, so you should better use the above workaround for now. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/