1
- ===================================================================
2
- Proposal for extended Vi tags file format
3
- ===================================================================
4
-
5
- .. note ::
6
-
7
- The contents of next section is a copy of FORMAT file in exuberant
8
- ctags source code in its subversion repository at sourceforge.net.
9
-
10
- We have made some modifications:
11
-
12
- * Exceptions introduced in Universal-ctags are explained with
13
- "EXCEPTION" marker.
1
+ .. _tags(5) :
2
+
3
+ ==============================================================
4
+ tags
5
+ ==============================================================
6
+ --------------------------------------------------------------
7
+ Vi tags file format extended in ctags projects
8
+ --------------------------------------------------------------
9
+ :Version: 2+
10
+ :Manual group: Universal-ctags
11
+ :Manual section: 5
12
+
13
+ DESCRIPTION
14
+ -----------
14
15
15
- * `Exceptions in Universal-ctags `_ subsction summarizes the exceptions.
16
+ The contents of next section is a copy of FORMAT file in exuberant
17
+ ctags source code in its subversion repository at sourceforge.net.
16
18
17
- .. contents :: `Table of contents`
18
- :depth: 3
19
- :local:
19
+ Exceptions introduced in Universal-ctags are explained inline with
20
+ "EXCEPTION" marker.
20
21
21
22
----
22
23
23
- :Version: 0.06 DRAFT
24
- :Date: 1998 Feb 8
25
- :Author: Bram Moolenaar <Bram at vim.org> and Darren Hiebert <dhiebert at users.sourceforge.net>
24
+ Proposal for extended Vi tags file format
25
+ -----------------------------------------
26
26
27
+ | Version: 0.06 DRAFT
28
+ | Date: 1998 Feb 8
29
+ | Author: Bram Moolenaar <Bram at vim.org> and Darren Hiebert <dhiebert at users.sourceforge.net>
27
30
28
31
Introduction
29
- ---------------------------------------------------------------------
32
+ ~~~~~~~~~~~~
30
33
31
34
The file format for the "tags" file, as used by Vi and many of its
32
35
descendants, has limited capabilities.
@@ -48,7 +51,7 @@ This additional functionality is desired:
48
51
49
52
50
53
From proposal to standard
51
- -------------------------------------------------------------------------
54
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
52
55
53
56
To make this proposal into a standard for tags files, it needs to be supported
54
57
by most people working on versions of Vi, ctags, etc.. Currently this
88
91
89
92
90
93
Backwards compatibility
91
- ---------------------------------------------------------------------------
94
+ ~~~~~~~~~~~~~~~~~~~~~~~
92
95
93
96
A tags file that is generated in the new format should still be usable by Vi.
94
97
This makes it possible to distribute tags files that are usable by all
@@ -148,7 +151,7 @@ from this.
148
151
149
152
150
153
Security
151
- ------------------------------------------------------------------
154
+ ~~~~~~~~
152
155
153
156
Vi allows the use of any Ex command in a tags file. This has the potential of
154
157
a trojan horse security leak.
@@ -194,7 +197,7 @@ position the cursor in a certain column.
194
197
195
198
196
199
Goals
197
- --------
200
+ ~~~~~
198
201
199
202
Now the usage of the comment text has to be defined. The following is aimed
200
203
at:
217
220
* It should be possible to treat a tags file like any normal text file.
218
221
219
222
Proposal
220
- -----------
223
+ ~~~~~~~~
221
224
222
225
Use a comment after the {tagaddress} field. The format would be::
223
226
@@ -470,14 +473,14 @@ file, and provided solely for documentation purposes::
470
473
!_TAG_PROGRAM_VERSION {version-id} /optional comment/
471
474
472
475
Exceptions in Universal-ctags
473
- --------------------------------
476
+ --------------------------------------------
474
477
475
478
Universal-ctags supports this proposal with some
476
479
exceptions.
477
480
478
481
479
482
Exceptions
480
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
483
+ ~~~~~~~~~~~
481
484
482
485
#. {tagname} in tags file generated by Universal-ctags may contain
483
486
spaces and several escape sequences. Parsers for documents like Tex and
@@ -494,7 +497,7 @@ Exceptions
494
497
.. _compat-output:
495
498
496
499
Compatible output and weakness
497
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
500
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
498
501
499
502
.. NOT REVIEWED YET
500
503
@@ -505,3 +508,7 @@ format as Exuberant-ctags. However, ``--output-format=e-ctags`` throws
505
508
away a tag entry which name includes a space or a tab
506
509
character. ``TAG_OUTPUT_MODE `` pseudo tag tells which format is
507
510
used when ctags generating tags file.
511
+
512
+ SEE ALSO
513
+ --------
514
+ ctags(1), ctags-incompatibilities(7)
0 commit comments