summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorFrancesco Potortì <pot@gnu.org>2007-05-05 00:36:21 +0000
committerFrancesco Potortì <pot@gnu.org>2007-05-05 00:36:21 +0000
commitbdd1961c05a52eddd5c58640f424864111d92c0f (patch)
tree835cfd119d65b6f86b3dd52eec256e0dcc862c3f /man
parent8224ce18f1f6d7ce205bb33bc1268bc6cf7ae7e5 (diff)
downloademacs-bdd1961c05a52eddd5c58640f424864111d92c0f.tar.gz
(Create Tags Table): Add text about the dangers of
making symbolic links to tags files.
Diffstat (limited to 'man')
-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..ab98dccd350 100644
--- a/man/maintaining.texi
+++ b/man/maintaining.texi
@@ -410,6 +410,10 @@ 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}.
+ Notice that, in the usual case of using relative file names, you
+should not use 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
will still refer to the same files even if you move it, as long as the