summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2007-05-06 17:49:19 +0000
committerRichard M. Stallman <rms@gnu.org>2007-05-06 17:49:19 +0000
commit500c43ed9fdcd056d5e01c946a536cf949b58850 (patch)
tree7805a5be17e5bd98eeaed439574c54b6fcf5a67a
parentfacc74f786206772329ddf7a1e2a97677863596e (diff)
downloademacs-500c43ed9fdcd056d5e01c946a536cf949b58850.tar.gz
(Create Tags Table): Add text about the dangers of
making symbolic links to tags files. (Clarified by RMS.)
-rw-r--r--man/maintaining.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/man/maintaining.texi b/man/maintaining.texi
index 52d404f8a08..c9e77ede2a1 100644
--- a/man/maintaining.texi
+++ b/man/maintaining.texi
@@ -409,6 +409,10 @@ source files, and the tags file will still refer correctly to the source
files. If the tags file is in @file{/dev}, however, the file names are
made relative to the current working directory. This is useful, for
example, when writing the tags to @file{/dev/stdout}.
+
+ When using a a relative file name, it should not be a symbolic link
+pointing to a tags file in a different directory, because this would
+generally render the file names invalid.
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