comparison man/maintaining.texi @ 68927:1ccf0b1b5b01

(Create Tags Table): Explain why the exception when etags writes to files under the /dev tree.
author Francesco Potortì <pot@gnu.org>
date Wed, 15 Feb 2006 13:30:19 +0000
parents 63d1645b9198
children 91970b147f39 9e490faa9f6b
comparison
equal deleted inserted replaced
68926:749818038c46 68927:1ccf0b1b5b01
402 @code{etags}, the tags file will contain file names relative to the 402 @code{etags}, the tags file will contain file names relative to the
403 directory where the tags file was initially written. This way, you can 403 directory where the tags file was initially written. This way, you can
404 move an entire directory tree containing both the tags file and the 404 move an entire directory tree containing both the tags file and the
405 source files, and the tags file will still refer correctly to the source 405 source files, and the tags file will still refer correctly to the source
406 files. If the tags file is in @file{/dev}, however, the file names are 406 files. If the tags file is in @file{/dev}, however, the file names are
407 made relative to the current working directory. 407 made relative to the current working directory. This is useful, for
408 example, when writing the tags to @file{/dev/stdout}.
408 409
409 If you specify absolute file names as arguments to @code{etags}, then 410 If you specify absolute file names as arguments to @code{etags}, then
410 the tags file will contain absolute file names. This way, the tags file 411 the tags file will contain absolute file names. This way, the tags file
411 will still refer to the same files even if you move it, as long as the 412 will still refer to the same files even if you move it, as long as the
412 source files remain in the same place. Absolute file names start with 413 source files remain in the same place. Absolute file names start with