aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancesco Potortì2007-05-05 00:36:21 +0000
committerFrancesco Potortì2007-05-05 00:36:21 +0000
commitbdd1961c05a52eddd5c58640f424864111d92c0f (patch)
tree835cfd119d65b6f86b3dd52eec256e0dcc862c3f
parent8224ce18f1f6d7ce205bb33bc1268bc6cf7ae7e5 (diff)
downloademacs-bdd1961c05a52eddd5c58640f424864111d92c0f.tar.gz
emacs-bdd1961c05a52eddd5c58640f424864111d92c0f.zip
(Create Tags Table): Add text about the dangers of
making symbolic links to tags files.
-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
410made relative to the current working directory. This is useful, for 410made relative to the current working directory. This is useful, for
411example, when writing the tags to @file{/dev/stdout}. 411example, when writing the tags to @file{/dev/stdout}.
412 412
413 Notice that, in the usual case of using relative file names, you
414should not use a symbolic link pointing to a tags file in a different
415directory, because this would generally render the file names invalid.
416
413 If you specify absolute file names as arguments to @code{etags}, then 417 If you specify absolute file names as arguments to @code{etags}, then
414the tags file will contain absolute file names. This way, the tags file 418the tags file will contain absolute file names. This way, the tags file
415will still refer to the same files even if you move it, as long as the 419will still refer to the same files even if you move it, as long as the