[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A syntax table specifies the syntactic textual function of each character. This information is used by the parsing functions, the complex movement commands, and others to determine where words, symbols, and other syntactic constructs begin and end. The current syntax table controls the meaning of the word motion functions (see section Motion by Words) and the list motion functions (see section Moving over Balanced Expressions), as well as the functions in this chapter.
35.1 Syntax Table Concepts | Basic concepts of syntax tables. | |
35.2 Syntax Descriptors | How characters are classified. | |
35.3 Syntax Table Functions | How to create, examine and alter syntax tables. | |
35.4 Syntax Properties | Overriding syntax with text properties. | |
35.5 Motion and Syntax | Moving over characters with certain syntaxes. | |
35.6 Parsing Balanced Expressions | Parsing balanced expressions using the syntax table. | |
35.7 Some Standard Syntax Tables | Syntax tables used by various major modes. | |
35.8 Syntax Table Internals | How syntax table information is stored. | |
35.9 Categories | Another way of classifying character syntax. |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A syntax table provides Emacs with the information that determines the syntactic use of each character in a buffer. This information is used by the parsing commands, the complex movement commands, and others to determine where words, symbols, and other syntactic constructs begin and end. The current syntax table controls the meaning of the word motion functions (see section Motion by Words) and the list motion functions (see section Moving over Balanced Expressions) as well as the functions in this chapter.
A syntax table is a char-table (see section Char-Tables). The element at index c describes the character with code c. The element’s value should be a list that encodes the syntax of the character in question.
Syntax tables are used only for moving across text, not for the Emacs Lisp reader. Emacs Lisp uses built-in syntactic rules when reading Lisp expressions, and these rules cannot be changed. (Some Lisp systems provide ways to redefine the read syntax, but we decided to leave this feature out of Emacs Lisp for simplicity.)
Each buffer has its own major mode, and each major mode has its own idea of the syntactic class of various characters. For example, in Lisp mode, the character ‘;’ begins a comment, but in C mode, it terminates a statement. To support these variations, Emacs makes the choice of syntax table local to each buffer. Typically, each major mode has its own syntax table and installs that table in each buffer that uses that mode. Changing this table alters the syntax in all those buffers as well as in any buffers subsequently put in that mode. Occasionally several similar modes share one syntax table. See section Major Mode Examples, for an example of how to set up a syntax table.
A syntax table can inherit the data for some characters from the standard syntax table, while specifying other characters itself. The “inherit” syntax class means “inherit this character’s syntax from the standard syntax table.” Just changing the standard syntax for a character affects all syntax tables that inherit from it.
This function returns t
if object is a syntax table.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes the syntax classes and flags that denote the
syntax of a character, and how they are represented as a syntax
descriptor, which is a Lisp string that you pass to
modify-syntax-entry
to specify the syntax you want.
The syntax table specifies a syntax class for each character. There is no necessary relationship between the class of a character in one syntax table and its class in any other table.
Each class is designated by a mnemonic character, which serves as the name of the class when you need to specify a class. Usually the designator character is one that is often assigned that class; however, its meaning as a designator is unvarying and independent of what syntax that character currently has. Thus, ‘\’ as a designator character always gives “escape character” syntax, regardless of what syntax ‘\’ currently has.
A syntax descriptor is a Lisp string that specifies a syntax class, a matching character (used only for the parenthesis classes) and flags. The first character is the designator for a syntax class. The second character is the character to match; if it is unused, put a space there. Then come the characters for any desired flags. If no matching character or flags are needed, one character is sufficient.
For example, the syntax descriptor for the character ‘*’ in C mode is ‘. 23’ (i.e., punctuation, matching character slot unused, second character of a comment-starter, first character of a comment-ender), and the entry for ‘/’ is ‘. 14’ (i.e., punctuation, matching character slot unused, first character of a comment-starter, second character of a comment-ender).
35.2.1 Table of Syntax Classes | Table of syntax classes. | |
35.2.2 Syntax Flags | Additional flags each character can have. |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Here is a table of syntax classes, the characters that stand for them, their meanings, and examples of their use.
Whitespace characters (designated by ‘ ’ or ‘-’) separate symbols and words from each other. Typically, whitespace characters have no other syntactic significance, and multiple whitespace characters are syntactically equivalent to a single one. Space, tab, newline and formfeed are classified as whitespace in almost all major modes.
Word constituents (designated by ‘w’) are parts of normal English words and are typically used in variable and command names in programs. All upper- and lower-case letters, and the digits, are typically word constituents.
Symbol constituents (designated by ‘_’) are the extra characters that are used in variable and command names along with word constituents. For example, the symbol constituents class is used in Lisp mode to indicate that certain characters may be part of symbol names even though they are not part of English words. These characters are ‘$&*+-_<>’. In standard C, the only non-word-constituent character that is valid in symbols is underscore (‘_’).
Punctuation characters (designated by ‘.’) are those characters that are used as punctuation in English, or are used in some way in a programming language to separate symbols from one another. Most programming language modes, including Emacs Lisp mode, have no characters in this class since the few characters that are not symbol or word constituents all have other uses.
Open and close parenthesis characters are characters used in dissimilar pairs to surround sentences or expressions. Such a grouping is begun with an open parenthesis character and terminated with a close. Each open parenthesis character matches a particular close parenthesis character, and vice versa. Normally, Emacs indicates momentarily the matching open parenthesis when you insert a close parenthesis. See section Blinking Parentheses.
The class of open parentheses is designated by ‘(’, and that of close parentheses by ‘)’.
In English text, and in C code, the parenthesis pairs are ‘()’, ‘[]’, and ‘{}’. In Emacs Lisp, the delimiters for lists and vectors (‘()’ and ‘[]’) are classified as parenthesis characters.
String quote characters (designated by ‘"’) are used in many languages, including Lisp and C, to delimit string constants. The same string quote character appears at the beginning and the end of a string. Such quoted strings do not nest.
The parsing facilities of Emacs consider a string as a single token. The usual syntactic meanings of the characters in the string are suppressed.
The Lisp modes have two string quote characters: double-quote (‘"’) and vertical bar (‘|’). ‘|’ is not used in Emacs Lisp, but it is used in Common Lisp. C also has two string quote characters: double-quote for strings, and single-quote (‘'’) for character constants.
English text has no string quote characters because English is not a programming language. Although quotation marks are used in English, we do not want them to turn off the usual syntactic properties of other characters in the quotation.
An escape character (designated by ‘\’) starts an escape sequence such as is used in C string and character constants. The character ‘\’ belongs to this class in both C and Lisp. (In C, it is used thus only inside strings, but it turns out to cause no trouble to treat it this way throughout C code.)
Characters in this class count as part of words if
words-include-escapes
is non-nil
. See section Motion by Words.
A character quote character (designated by ‘/’) quotes the following character so that it loses its normal syntactic meaning. This differs from an escape character in that only the character immediately following is ever affected.
Characters in this class count as part of words if
words-include-escapes
is non-nil
. See section Motion by Words.
This class is used for backslash in TeX mode.
Paired delimiter characters (designated by ‘$’) are like string quote characters except that the syntactic properties of the characters between the delimiters are not suppressed. Only TeX mode uses a paired delimiter presently—the ‘$’ that both enters and leaves math mode.
An expression prefix operator (designated by ‘'’) is used for syntactic operators that are considered as part of an expression if they appear next to one. In Lisp modes, these characters include the apostrophe, ‘'’ (used for quoting), the comma, ‘,’ (used in macros), and ‘#’ (used in the read syntax for certain data types).
The comment starter and comment ender characters are used in various languages to delimit comments. These classes are designated by ‘<’ and ‘>’, respectively.
English text has no comment characters. In Lisp, the semicolon (‘;’) starts a comment and a newline or formfeed ends one.
This syntax class does not specify a particular syntax. It says to look in the standard syntax table to find the syntax of this character. The designator for this syntax code is ‘@’.
A generic comment delimiter (designated by ‘!’) starts or ends a special kind of comment. Any generic comment delimiter matches any generic comment delimiter, but they cannot match a comment starter or comment ender; generic comment delimiters can only match each other.
This syntax class is primarily meant for use with the
syntax-table
text property (see section Syntax Properties). You can
mark any range of characters as forming a comment, by giving the first
and last characters of the range syntax-table
properties
identifying them as generic comment delimiters.
A generic string delimiter (designated by ‘|’) starts or ends a string. This class differs from the string quote class in that any generic string delimiter can match any other generic string delimiter; but they do not match ordinary string quote characters.
This syntax class is primarily meant for use with the
syntax-table
text property (see section Syntax Properties). You can
mark any range of characters as forming a string constant, by giving the
first and last characters of the range syntax-table
properties
identifying them as generic string delimiters.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In addition to the classes, entries for characters in a syntax table can specify flags. There are seven possible flags, represented by the characters ‘1’, ‘2’, ‘3’, ‘4’, ‘b’, ‘n’, and ‘p’.
All the flags except ‘n’ and ‘p’ are used to describe multi-character comment delimiters. The digit flags indicate that a character can also be part of a comment sequence, in addition to the syntactic properties associated with its character class. The flags are independent of the class and each other for the sake of characters such as ‘*’ in C mode, which is a punctuation character, and the second character of a start-of-comment sequence (‘/*’), and the first character of an end-of-comment sequence (‘*/’).
Here is a table of the possible flags for a character c, and what they mean:
Emacs supports two comment styles simultaneously in any one syntax table. This is for the sake of C++. Each style of comment syntax has its own comment-start sequence and its own comment-end sequence. Each comment must stick to one style or the other; thus, if it starts with the comment-start sequence of style “b”, it must also end with the comment-end sequence of style “b”.
The two comment-start sequences must begin with the same character; only the second character may differ. Mark the second character of the “b”-style comment-start sequence with the ‘b’ flag.
A comment-end sequence (one or two characters) applies to the “b” style if its first character has the ‘b’ flag set; otherwise, it applies to the “a” style.
The appropriate comment syntax settings for C++ are as follows:
‘124b’
‘23’
‘>b’
This defines four comment-delimiting sequences:
This is a comment-start sequence for “a” style because the second character, ‘*’, does not have the ‘b’ flag.
This is a comment-start sequence for “b” style because the second character, ‘/’, does have the ‘b’ flag.
This is a comment-end sequence for “a” style because the first character, ‘*’, does not have the ‘b’ flag.
This is a comment-end sequence for “b” style, because the newline character has the ‘b’ flag.
The function backward-prefix-chars
moves back over these
characters, as well as over characters whose primary syntax class is
prefix (‘'’). See section Motion and Syntax.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In this section we describe functions for creating, accessing and altering syntax tables.
This function creates a new syntax table. It inherits the syntax for letters and control characters from the standard syntax table. For other characters, the syntax is copied from the standard syntax table.
Most major mode syntax tables are created in this way.
This function constructs a copy of table and returns it. If
table is not supplied (or is nil
), it returns a copy of the
current syntax table. Otherwise, an error is signaled if table is
not a syntax table.
This function sets the syntax entry for char according to syntax-descriptor. The syntax is changed only for table, which defaults to the current buffer’s syntax table, and not in any other syntax table. The argument syntax-descriptor specifies the desired syntax; this is a string beginning with a class designator character, and optionally containing a matching character and flags as well. See section Syntax Descriptors.
This function always returns nil
. The old syntax information in
the table for this character is discarded.
An error is signaled if the first character of the syntax descriptor is not one of the twelve syntax class designator characters. An error is also signaled if char is not a character.
Examples: ;; Put the space character in class whitespace. (modify-syntax-entry ?\ " ") ⇒ nil ;; Make ‘$’ an open parenthesis character, ;; with ‘^’ as its matching close. (modify-syntax-entry ?$ "(^") ⇒ nil ;; Make ‘^’ a close parenthesis character, ;; with ‘$’ as its matching open. (modify-syntax-entry ?^ ")$") ⇒ nil ;; Make ‘/’ a punctuation character, ;; the first character of a start-comment sequence, ;; and the second character of an end-comment sequence. ;; This is used in C mode. (modify-syntax-entry ?/ ". 14") ⇒ nil |
This function returns the syntax class of character, represented by its mnemonic designator character. This returns only the class, not any matching parenthesis or flags.
An error is signaled if char is not a character.
The following examples apply to C mode. The first example shows that the syntax class of space is whitespace (represented by a space). The second example shows that the syntax of ‘/’ is punctuation. This does not show the fact that it is also part of comment-start and -end sequences. The third example shows that open parenthesis is in the class of open parentheses. This does not show the fact that it has a matching character, ‘)’.
(string (char-syntax ?\ )) ⇒ " " (string (char-syntax ?/)) ⇒ "." (string (char-syntax ?\()) ⇒ "(" |
We use string
to make it easier to see the character returned by
char-syntax
.
This function makes table the syntax table for the current buffer. It returns table.
This function returns the current syntax table, which is the table for the current buffer.
This macro executes body using table as the current syntax table. It returns the value of the last form in body, after restoring the old current syntax table.
Since each buffer has its own current syntax table, we should make that
more precise: with-syntax-table
temporarily alters the current
syntax table of whichever buffer is current at the time the macro
execution starts. Other buffers are not affected.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When the syntax table is not flexible enough to specify the syntax of a
language, you can use syntax-table
text properties to override
the syntax table for specific character occurrences in the buffer.
See section Text Properties.
The valid values of syntax-table
text property are:
If the property value is a syntax table, that table is used instead of the current buffer’s syntax table to determine the syntax for this occurrence of the character.
(syntax-code . matching-char)
A cons cell of this format specifies the syntax for this occurrence of the character. (see section Syntax Table Internals)
nil
If the property is nil
, the character’s syntax is determined from
the current syntax table in the usual way.
If this is non-nil
, the syntax scanning functions pay attention
to syntax text properties. Otherwise they use only the current syntax
table.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes functions for moving across characters that have certain syntax classes.
This function moves point forward across characters having syntax classes mentioned in syntaxes. It stops when it encounters the end of the buffer, or position limit (if specified), or a character it is not supposed to skip.
If syntaxes starts with ‘^’, then the function skips characters whose syntax is not in syntaxes.
The return value is the distance traveled, which is a nonnegative integer.
This function moves point backward across characters whose syntax classes are mentioned in syntaxes. It stops when it encounters the beginning of the buffer, or position limit (if specified), or a character it is not supposed to skip.
If syntaxes starts with ‘^’, then the function skips characters whose syntax is not in syntaxes.
The return value indicates the distance traveled. It is an integer that is zero or less.
This function moves point backward over any number of characters with expression prefix syntax. This includes both characters in the expression prefix syntax class, and characters with the ‘p’ flag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Here are several functions for parsing and scanning balanced expressions, also known as sexps, in which parentheses match in pairs. The syntax table controls the interpretation of characters, so these functions can be used for Lisp expressions when in Lisp mode and for C expressions when in C mode. See section Moving over Balanced Expressions, for convenient higher-level functions for moving over balanced expressions.
This function parses a sexp in the current buffer starting at start, not scanning past limit. It stops at position limit or when certain criteria described below are met, and sets point to the location where parsing stops. It returns a value describing the status of the parse at the point where it stops.
If state is nil
, start is assumed to be at the top
level of parenthesis structure, such as the beginning of a function
definition. Alternatively, you might wish to resume parsing in the
middle of the structure. To do this, you must provide a state
argument that describes the initial status of parsing.
If the third argument target-depth is non-nil
, parsing
stops if the depth in parentheses becomes equal to target-depth.
The depth starts at 0, or at whatever is given in state.
If the fourth argument stop-before is non-nil
, parsing
stops when it comes to any character that starts a sexp. If
stop-comment is non-nil
, parsing stops when it comes to the
start of a comment. If stop-comment is the symbol
syntax-table
, parsing stops after the start of a comment or a
string, or the end of a comment or a string, whichever comes first.
The fifth argument state is a nine-element list of the same form
as the value of this function, described below. (It is OK to omit the
last element of the nine.) The return value of one call may be used to
initialize the state of the parse on another call to
parse-partial-sexp
.
The result is a list of nine elements describing the final state of the parse:
nil
if none.
nil
if none.
nil
if inside a string. More precisely, this is the
character that will terminate the string, or t
if a generic
string delimiter character should terminate it.
t
if inside a comment (of either style),
or the comment nesting level if inside a kind of comment
that can be nested.
t
if point is just after a quote character.
nil
for a comment of style “a”,
t
for a comment of style “b”, and syntax-table
for
a comment that should be ended by a generic comment delimiter character.
nil
.
Elements 0, 3, 4, 5 and 7 are significant in the argument state.
This function is most often used to compute indentation for languages that have nested parentheses.
This function scans forward count balanced parenthetical groupings from position from. It returns the position where the scan stops. If count is negative, the scan moves backwards.
If depth is nonzero, parenthesis depth counting begins from that
value. The only candidates for stopping are places where the depth in
parentheses becomes zero; scan-lists
counts count such
places and then stops. Thus, a positive value for depth means go
out depth levels of parenthesis.
Scanning ignores comments if parse-sexp-ignore-comments
is
non-nil
.
If the scan reaches the beginning or end of the buffer (or its
accessible portion), and the depth is not zero, an error is signaled.
If the depth is zero but the count is not used up, nil
is
returned.
This function scans forward count sexps from position from. It returns the position where the scan stops. If count is negative, the scan moves backwards.
Scanning ignores comments if parse-sexp-ignore-comments
is
non-nil
.
If the scan reaches the beginning or end of (the accessible part of) the
buffer while in the middle of a parenthetical grouping, an error is
signaled. If it reaches the beginning or end between groupings but
before count is used up, nil
is returned.
If this variable is non-nil
, scan-sexps
treats all
non-ASCII characters as symbol constituents regardless
of what the syntax table says about them. (However, text properties
can still override the syntax.)
If the value is non-nil
, then comments are treated as
whitespace by the functions in this section and by forward-sexp
.
In older Emacs versions, this feature worked only when the comment
terminator is something like ‘*/’, and appears only to end a
comment. In languages where newlines terminate comments, it was
necessary make this variable nil
, since not every newline is the
end of a comment. This limitation no longer exists.
You can use forward-comment
to move forward or backward over
one comment or several comments.
This function moves point forward across count comments (backward, if count is negative). If it finds anything other than a comment or whitespace, it stops, leaving point at the place where it stopped. It also stops after satisfying count.
To move forward over all comments and whitespace following point, use
(forward-comment (buffer-size))
. (buffer-size)
is a good
argument to use, because the number of comments in the buffer cannot
exceed that many.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Most of the major modes in Emacs have their own syntax tables. Here are several of them:
This function returns the standard syntax table, which is the syntax table used in Fundamental mode.
The value of this variable is the syntax table used in Text mode.
The value of this variable is the syntax table for C-mode buffers.
The value of this variable is the syntax table used in Emacs Lisp mode
by editing commands. (It has no effect on the Lisp read
function.)
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Lisp programs don’t usually work with the elements directly; the Lisp-level syntax table functions usually work with syntax descriptors (see section Syntax Descriptors). Nonetheless, here we document the internal format. This format is used mostly when manipulating syntax properties.
Each element of a syntax table is a cons cell of the form
(syntax-code . matching-char)
. The CAR,
syntax-code, is an integer that encodes the syntax class, and any
flags. The CDR, matching-char, is non-nil
if
a character to match was specified.
This table gives the value of syntax-code which corresponds to each syntactic type.
Integer Class | Integer Class | Integer Class | |
0 whitespace | 5 close parenthesis | 10 character quote | |
1 punctuation | 6 expression prefix | 11 comment-start | |
2 word | 7 string quote | 12 comment-end | |
3 symbol | 8 paired delimiter | 13 inherit | |
4 open parenthesis | 9 escape | 14 comment-fence | |
15 string-fence |
For example, the usual syntax value for ‘(’ is (4 . 41)
.
(41 is the character code for ‘)’.)
The flags are encoded in higher order bits, starting 16 bits from the least significant bit. This table gives the power of two which corresponds to each syntax flag.
Prefix Flag | Prefix Flag | Prefix Flag | |
‘1’ (lsh 1 16) | ‘4’ (lsh 1 19) | ‘b’ (lsh 1 21) | |
‘2’ (lsh 1 17) | ‘p’ (lsh 1 20) | ‘n’ (lsh 1 22) | |
‘3’ (lsh 1 18) |
This function returns the internal form (syntax-code .
matching-char)
corresponding to the syntax descriptor desc.
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Yasutaka SHINDOH on April 18, 2010 using texi2html 1.82.