Mercurial > emacs
changeset 57090:297e3051e6ac
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.
| author | Francesco Potortì <pot@gnu.org> |
|---|---|
| date | Mon, 13 Sep 2004 19:56:12 +0000 |
| parents | e3616b62370a |
| children | a02f327b4165 |
| files | etc/etags.1 man/maintaining.texi |
| diffstat | 2 files changed, 5 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/etc/etags.1 Mon Sep 13 19:50:40 2004 +0000 +++ b/etc/etags.1 Mon Sep 13 19:56:12 2004 +0000 @@ -58,7 +58,9 @@ \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.
--- a/man/maintaining.texi Mon Sep 13 19:50:40 2004 +0000 +++ b/man/maintaining.texi Mon Sep 13 19:56:12 2004 +0000 @@ -445,7 +445,8 @@ 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