unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: shell-command causes problems with absolute/relative paths in TAGS
Date: Fri, 06 Jan 2012 13:34:39 +0200	[thread overview]
Message-ID: <83r4zdnjxs.fsf@gnu.org> (raw)
In-Reply-To: <AA798C0D220E44E5B798734A70C4CF93@EUROPE.ROOT.PRI>

> From: "David Chappaz" <david.chappaz@free.fr>
> Date: Wed, 4 Jan 2012 16:05:13 -0000
> 
> Now, I generate my TAGS file from a plain windows shell, with the following
> command:
> 
> more filelist.txt | ctags -e -L -
> 
> This works fine, and, as expected, the paths to the source files in the TAGS
> file are relative, so the entire "test" folder and the TAGS file can be
> moved to a different location.
> 
> I'm developing a small emacs package to provide some sort of IDE. So now I'm
> trying to do the same from within emacs. If I do:
> 
> M-x shell-command
> more filelist.txt | ctags -e -L -
> 
> ...then the result is different, and now paths in the TAGS file become
> absolute. Even using the explicit option --tag-relative=yes does not change
> anything.

FWIW, I cannot reproduce this on MS-Windows with Emacs 23.3.  I don't
have Exuberant CTags, but using the etags program provided with
Emacs.  I get relative file names with either method.

Can you reproduce the problem in "emacs -Q"?  If not, there's some
customization of yours that causes this, or maybe it is a problem with
Exuberant on Windows.



      parent reply	other threads:[~2012-01-06 11:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 22:33 M-x mystery Silvio Levy
2012-01-02 23:25 ` Drew Adams
2012-01-04 16:05   ` shell-command causes problems with absolute/relative paths in TAGS David Chappaz
2012-01-04 16:15     ` Vladimir Murzin
2012-01-04 16:27       ` David Chappaz
2012-01-05  5:41     ` Bob Proulx
2012-01-05 12:20       ` David Chappaz
2012-01-05 16:53         ` Unknown
2012-01-05 22:20         ` Bob Proulx
2012-01-06 11:12           ` David Chappaz
2012-01-06 11:38             ` Eli Zaretskii
2012-01-06 13:04               ` David Chappaz
2012-01-06 15:42                 ` Eli Zaretskii
2012-01-06 16:03                   ` David Chappaz
2012-01-06 16:12                     ` David Chappaz
2012-01-06 18:46                     ` Eli Zaretskii
2012-01-06 11:25     ` Eli Zaretskii
2012-01-06 14:04       ` David Chappaz
2012-01-06 15:12         ` Eli Zaretskii
2012-01-06 15:52           ` Juanma Barranquero
2012-01-06 11:34     ` Eli Zaretskii [this message]

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=83r4zdnjxs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).