From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Francesco =?utf-8?Q?Potort=C3=AC?= Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105295: * lisp/progmodes/etags.el (etags-file-of-tag, etags-tags-table-files) Date: Tue, 02 Aug 2011 10:11:17 +0200 Message-ID: References: NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1312272732 13763 80.91.229.12 (2 Aug 2011 08:12:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 2 Aug 2011 08:12:12 +0000 (UTC) Cc: Sam Steingold , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 02 10:12:08 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QoA5A-0001JH-Km for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2011 10:12:08 +0200 Original-Received: from localhost ([::1]:37838 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoA5A-0001g5-2K for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2011 04:12:08 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoA56-0001fo-M5 for emacs-devel@gnu.org; Tue, 02 Aug 2011 04:12:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoA55-00073A-GU for emacs-devel@gnu.org; Tue, 02 Aug 2011 04:12:04 -0400 Original-Received: from blade3.isti.cnr.it ([194.119.192.19]:58107) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoA55-00072p-8s; Tue, 02 Aug 2011 04:12:03 -0400 Original-Received: from tucano.isti.cnr.it (tucano.isti.cnr.it [146.48.81.102]) by mx.isti.cnr.it (PMDF V6.5-x5 #31826) with ESMTPSA id <01O4DD87LOBWW7Z07B@mx.isti.cnr.it>; Tue, 02 Aug 2011 10:11:16 +0200 (MEST) Original-Received: from pot by tucano.isti.cnr.it with local (Exim 4.76) (envelope-from ) id 1QoA4L-0002R9-9s; Tue, 02 Aug 2011 10:11:17 +0200 In-reply-to: X-INSM-ip-source: 146.48.81.102 Auth Done X-fingerprint: 4B02 6187 5C03 D6B1 2E31 7666 09DF 2DC9 BE21 6115 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 194.119.192.19 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142680 Archived-At: >> * lisp/progmodes/etags.el (etags-file-of-tag, etags-tags-table-files) >> (etags-tags-included-tables): Call `convert-standard-filename' on >> the file names contained in TAGS so that windows Emacs can handle >> TAGS files created by cygwin ctags. > >Is that really right? >I mean, convert-standard-filename should only ever be called on absolute >file names, and we have no guarantee that file names in TAGS are >absolute, do we? No, we do not. On the opposite, relative file names in tag files should never be converted to absolute, and absolute ones never converted to relative. The users choose if they want relative or absolute file names in tags: 33.3.2 Creating Tags Tables --------------------------- ... If you specify the source files with relative file names when you run `etags', the tags file will contain file names relative to the directory where the tags file was initially written. This way, you can move an entire directory tree containing both the tags file and the source files, and the tags file will still refer correctly to the source files. If the tags file is in `/dev', however, the file names are made relative to the current working directory. This is useful, for example, when writing the tags to `/dev/stdout'. When using a relative file name, it should not be a symbolic link pointing to a tags file in a different directory, because this would generally render the file names invalid. If you specify absolute file names as arguments to `etags', then the tags file will contain absolute file names. This way, the tags file will still refer to the same files even if you move it, as long as the source files remain in the same place. Absolute file names start with `/', or with `DEVICE:/' on MS-DOS and MS-Windows.