unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Francesco Potorti` <pot@gnu.org>
To: bug-gnu-emacs@gnu.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: bug#735: Bug in etags ".." code
Date: Sun, 17 Aug 2008 02:19:48 +0200	[thread overview]
Message-ID: <E1KUVzo-0000tw-Iq@tucano.isti.cnr.it> (raw)
In-Reply-To: <handler.32.D32.12120923322183.ackdone@emacsbugs.donarmstrong.com>

Ok, it has been quite some time since you reported this bug, but at last
I managed to look at it during my vacations...

> I ran etags like this:
> 
> etags ./eval.c -o $(pwd)//.retags.d/Q
> 
> Note the double "/".
> 
> The resulting tags file contains this line:
> 
> ../../eval.c,567
> 
> But this is wrong, there should be only a single "..".

Thank you for the patch for collapsing multiple consecutive slashes in
file names.  I generalised it by canonicalising all file names as soon
as they are read into etags.  I just installed the change into the
trunk.

I did not install it into the pretest branch yet.
Since this is a bug, it probably should go into the pretest branch too.

What do people think?  I am unsure whether this is serious enough to
grant a patch to the pretest branch,

P.S.
Please put me in Cc, as I discovered that I am no more subscribed to the
list, and a new subscription is in progress.







  reply	other threads:[~2008-08-17  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvr6bkampj.fsf-monnier+emacsbugreports@gnu.org>
2008-03-03  0:02 ` Bug in etags ".." code Tom Tromey
2008-03-05 20:57   ` Chong Yidong
2008-05-29 20:25   ` bug#32: marked as done (Bug in etags ".." code) Emacs bug Tracking System
2008-08-17  0:19     ` Francesco Potorti` [this message]
2008-08-20 22:35       ` bug#735: " Emacs bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1KUVzo-0000tw-Iq@tucano.isti.cnr.it \
    --to=pot@gnu.org \
    --cc=735@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).