I'm definitely not the guy to answer either windoze or emacs questions, but if you're desperate, here are some things I'd try were I in your shoes:

  1. Give the documentation another thorough read to see if you might have missed anything.
  2. I'm not seeing any relevant ENVIRONMENT section in the etags manpage; that's the traditional place to discuss env vars that affect behavior (LANG comes to mind).  That doesn't rule out environment differences causing problems, just reduces the likelihood.
  3. Try specifying absolute paths, to ensure you're getting the files you want.  I wouldn't know how to do that in windoze, but on linux it would be something like "/bin/more /tmp/filelist.txt | /usr/local/bin/ctags -e -L -"
  4. Perhaps the input fed to ctags isn't what you think it is; inject a tee into your pipeline to confirm it's exactly what you expect: "more filelist.txt | tee landing.txt | ctags -e -L -".  Compare the landing.txt against one generated on linux.
  5. I'm not immediately seeing why you're using a pager to feed to content to ctags; seems "cat filelist.txt | ctags -e -L -" or, even better, "ctags -e -L filelist.txt" is a better fit

Good luck.  If you run across a solution, please post it.



On 07/10/12 04:14 AM, David Chappaz wrote:

Recently there seem to some signs of life on the mailing list….

So I’m trying my chance again…. Could anyone please have a look, explain and/or solve the problem ?


Cheers !!



From: David Chappaz [mailto:david.chappaz@free.fr]
Sent: 11 February 2012 11:26
To: ctags-users@lists.sourceforge.net
Subject: Re: [Ctags] Ctags generates absolute instead of relative paths


Any suggestion, anyone ?
It would be nice to get to the bottom of this.

On 18/01/12 09:51, David Chappaz wrote:

Hi all,


I have a problem when generating TAGS from Gnu Emacs 23.3, but the problem only occurs on Windows and not on linux.

Although I use the “
” option and even the explicit “
“ option, the TAGS file that is generated contains absolute paths instead of relative paths.


The details of this problem can be found here:



I originally thought this problem was related to emacs, not to ctags itself, because it only occurs when the shell command used to build the TAGS file is issued from within emacs, not from a plain windows shell.

However I now have doubts, and I’m wondering if ctags is not to blame after all.


To reproduce the problem, simply follow the steps at the end of this post:



Can anyone reproduce it ? Does anyone have a guess as to what the problem is ?

Is ctags sensitive to any environment variables (as opposed to command line arguments) which can explain that behaviour ?


Many thanks in advance