Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
500c43ed
Commit
500c43ed
authored
May 06, 2007
by
Richard M. Stallman
Browse files
(Create Tags Table): Add text about the dangers of
making symbolic links to tags files. (Clarified by RMS.)
parent
facc74f7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
man/maintaining.texi
man/maintaining.texi
+4
-0
No files found.
man/maintaining.texi
View file @
500c43ed
...
@@ -409,6 +409,10 @@ source files, and the tags file will still refer correctly to the source
...
@@ -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
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
made relative to the current working directory. This is useful, for
example, when writing the tags to @file{/dev/stdout}.
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
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
the tags file will contain absolute file names. This way, the tags file
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment