diff options
| author | Francesco Potortì | 2002-07-02 11:54:32 +0000 |
|---|---|---|
| committer | Francesco Potortì | 2002-07-02 11:54:32 +0000 |
| commit | 1038941db1cf4c2345a7b2e5e1f6a182615bfa1a (patch) | |
| tree | 69684192984fd5d40a38bce579ed7212708faa84 | |
| parent | 005e1610198130bdca78577a3e9608716a4aac06 (diff) | |
| download | emacs-1038941db1cf4c2345a7b2e5e1f6a182615bfa1a.tar.gz emacs-1038941db1cf4c2345a7b2e5e1f6a182615bfa1a.zip | |
Back to the old explanation, which was more concise, with just the first
two lines changed.
| -rw-r--r-- | etc/ETAGS.EBNF | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/etc/ETAGS.EBNF b/etc/ETAGS.EBNF index d2f8b68297e..195eba67325 100644 --- a/etc/ETAGS.EBNF +++ b/etc/ETAGS.EBNF | |||
| @@ -1,7 +1,9 @@ | |||
| 1 | -*- indented-text -*- | ||
| 2 | |||
| 1 | This file contains two sections: | 3 | This file contains two sections: |
| 2 | 4 | ||
| 3 | 1) An EBNF (Extended Backus Normal Form) description of the format of | 5 | 1) An EBNF (Extended Backus Normal Form) description of the format of |
| 4 | the tags file created by etags.c and interpreted by etags.el | 6 | the tags file created by etags.c and interpreted by etags.el |
| 5 | 2) A discussion of tag names and implicit tag names | 7 | 2) A discussion of tag names and implicit tag names |
| 6 | 8 | ||
| 7 | ======================= EBNF tag file description ======================= | 9 | ======================= EBNF tag file description ======================= |
| @@ -56,7 +58,7 @@ realposition ::= "," unsint | unsint "," | unsint "," unsint | |||
| 56 | 58 | ||
| 57 | 59 | ||
| 58 | 60 | ||
| 59 | ======================== discussion on tag names ========================= | 61 | ======================== discussion of tag names ========================= |
| 60 | 62 | ||
| 61 | - What are tag names | 63 | - What are tag names |
| 62 | Tag lines in a tags file are usually made from the above defined pattern | 64 | Tag lines in a tags file are usually made from the above defined pattern |
| @@ -72,16 +74,14 @@ Emacs can find a tag faster and more accurately. These tag names are | |||
| 72 | part of tag lines in the tags file, so we call them "explicit". | 74 | part of tag lines in the tags file, so we call them "explicit". |
| 73 | 75 | ||
| 74 | - Why implicit tag names are even better | 76 | - Why implicit tag names are even better |
| 75 | Often tag names are redundant; this happens when the name of a tag is an | 77 | When a tag line has no name, but a name can be deduced from the pattern, |
| 76 | easily guessable substring of the tag pattern. We define a set of rules | 78 | we say that the tag line has an implicit tag name. etags.c uses |
| 77 | to decide whether it is possible to deduce the tag name from the pattern, | 79 | implicit tag names when possible, in order to reduce the number of |
| 78 | and make an unnamed tag in those cases. The name deduced from the | 80 | explicit tag names in a tags file, thus reducing the size of the tags |
| 79 | pattern of an unnamed tag is the implicit name of that tag. The use of | 81 | file. When the user looks for a tag, and Emacs founds no explicit tag |
| 80 | implicit tag names reduces the size of the tags file. When the user | 82 | names that match it, Emacs then tries to match the tag with an implicit |
| 81 | looks for a tag, and Emacs founds no explicit tag names that match it, | 83 | tag name. Such a match occurs when the tag matches a pattern, subject |
| 82 | Emacs then tries to match the tag with an implicit tag name. Such a | 84 | to the satisfaction of all the following four rules: |
| 83 | match occurs when the tag matches a pattern, subject to the satisfaction | ||
| 84 | of all the following four rules: | ||
| 85 | 85 | ||
| 86 | NONAM=" \f\t\n\r()=,;"; | 86 | NONAM=" \f\t\n\r()=,;"; |
| 87 | 1. the tag does not contain any of the characters in NONAM; | 87 | 1. the tag does not contain any of the characters in NONAM; |