(Create Tags Table): Clean up previous change.
This commit is contained in:
parent
41cf03b018
commit
53441303ea
2 changed files with 8 additions and 4 deletions
|
@ -1,3 +1,7 @@
|
|||
2007-05-06 Richard Stallman <rms@gnu.org>
|
||||
|
||||
* maintaining.texi (Create Tags Table): Clean up previous change.
|
||||
|
||||
2007-05-05 Francesco Potort,Al(B <pot@gnu.org>
|
||||
|
||||
* maintaining.texi (Create Tags Table): Add text about the dangers of
|
||||
|
|
|
@ -409,10 +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}.
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
|
|
Loading…
Add table
Reference in a new issue