When relative file names are given as argument,

make them relative to the current working dir, rather than
relative to the output tags file, if the latter is in /dev.
This commit is contained in:
Francesco Potortì 2004-09-13 19:56:12 +00:00
parent e057dc50eb
commit 83a885869f
2 changed files with 5 additions and 2 deletions

View file

@ -58,7 +58,9 @@ table (defaults: \fBTAGS\fP for \fBetags\fP, \fBtags\fP for
\fBctags\fP) in the current working directory.
Files specified with relative file names will be recorded in the tag
table with file names relative to the directory where the tag table
resides. Files specified with absolute file names will be recorded
resides. If the tag table is in /dev, however, the file names are made
relative to the working directory. Files specified with absolute file
names will be recorded
with absolute file names. Files generated from a source file\-\-like
a C file generated from a source Cweb file\-\-will be recorded with
the name of the source file.

View file

@ -445,7 +445,8 @@ well as the files it directly contains.
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.
files. If the tags file is in /dev, however, the file names are made
relative to the current working directory.
If you specify absolute file names as arguments to @code{etags}, then
the tags file will contain absolute file names. This way, the tags file