


      CCCCTTTTAAAAGGGGSSSS((((1111))))                    ((((bbbbssssdddd 4444....2222))))                    CCCCTTTTAAAAGGGGSSSS((((1111))))



      NNNNAAAAMMMMEEEE
           ctags - create a tags file

      SSSSYYYYNNNNTTTTAAAAXXXX
           ccccttttaaaaggggssss [[[[----uuuu]]]] [[[[----wwww]]]] [[[[----xxxx]]]] name...

      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
           _C_t_a_g_s makes a tags file for the _e_x(1) editor from the
           specified objects (in this case functions) in a group of
           files. Each line of the tags file contains the function
           name, the file in which it is defined, and a scanning
           pattern used to find the function definition. These are
           given in separate fields on the line, separated by blanks or
           tabs. Using the _t_a_g_s file, _e_x can quickly find these
           function definitions.

           ----xxxx causes _c_t_a_g_s to produce a list of function names, the
           line number and file name on which each is defined, and
           print the text of that line on the standard output. This is
           a simple index which can be printed out as an off-line
           readable function index.

           Files whose names end in ....cccc or ....hhhh are assumed to be C source
           files and are searched for C routines and macro definitions.
           Others are first examined to see if they contain any Pascal
           or FORTRAN routine definitions; if not, they are processed
           again, looking for C definitions.

           Other options are:
           ----wwww   suppressing warning diagnostics

           ----uuuu   causing the specified files to be _u_p_d_a_t_e_d in tags; that
                is, all references to them are deleted, and the new
                values are appended to the file. (Beware: this option
                is implemented in a way that is rather slow. It is
                usually faster to simply rebuild the _t_a_g_s file.)

           The tag _m_a_i_n is treated specially in C programs. The tag
           formed is created by prepending _M to the name of the file,
           with a trailing .c removed, if any, and leading pathname
           components also removed. This makes use of _c_t_a_g_s practical
           in directories with more than one program.

      FFFFIIIILLLLEEEESSSS
           tags             output tags file

      SSSSEEEEEEEE AAAALLLLSSSSOOOO
           ex(1), vi(1)

      BBBBUUUUGGGGSSSS
           Recognition of ffffuuuunnnnccccttttiiiioooonnnnssss,,,, ssssuuuubbbbrrrroooouuuuttttiiiinnnneeeessss,,,, and pppprrrroooocccceeeedddduuuurrrreeeessss for
           FORTRAN and Pascal is done in a simpleminded way.  No



      Page 1                                                   (9010-E)






      CCCCTTTTAAAAGGGGSSSS((((1111))))                    ((((bbbbssssdddd 4444....2222))))                    CCCCTTTTAAAAGGGGSSSS((((1111))))



           attempt is made to deal with block structure; if you have
           two Pascal procedures in different blocks with the same
           name, ctags doesn't see it.




















































      Page 2                                                   (9010-E)



