2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
4 @c Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../info/syntax
7 @node Syntax Tables, Abbrevs, Searching and Matching, Top
13 A @dfn{syntax table} specifies the syntactic textual function of each
14 character. This information is used by the @dfn{parsing functions}, the
15 complex movement commands, and others to determine where words, symbols,
16 and other syntactic constructs begin and end. The current syntax table
17 controls the meaning of the word motion functions (@pxref{Word Motion})
18 and the list motion functions (@pxref{List Motion}), as well as the
19 functions in this chapter.
22 * Basics: Syntax Basics. Basic concepts of syntax tables.
23 * Desc: Syntax Descriptors. How characters are classified.
24 * Syntax Table Functions:: How to create, examine and alter syntax tables.
25 * Syntax Properties:: Overriding syntax with text properties.
26 * Motion and Syntax:: Moving over characters with certain syntaxes.
27 * Parsing Expressions:: Parsing balanced expressions
28 using the syntax table.
29 * Standard Syntax Tables:: Syntax tables used by various major modes.
30 * Syntax Table Internals:: How syntax table information is stored.
31 * Categories:: Another way of classifying character syntax.
35 @section Syntax Table Concepts
38 A @dfn{syntax table} provides Emacs with the information that
39 determines the syntactic use of each character in a buffer. This
40 information is used by the parsing commands, the complex movement
41 commands, and others to determine where words, symbols, and other
42 syntactic constructs begin and end. The current syntax table controls
43 the meaning of the word motion functions (@pxref{Word Motion}) and the
44 list motion functions (@pxref{List Motion}) as well as the functions in
48 A syntax table is a char-table (@pxref{Char-Tables}). The element at
49 index @var{c} describes the character with code @var{c}. The element's
50 value should be a list that encodes the syntax of the character in
53 Syntax tables are used only for moving across text, not for the Emacs
54 Lisp reader. Emacs Lisp uses built-in syntactic rules when reading Lisp
55 expressions, and these rules cannot be changed. (Some Lisp systems
56 provide ways to redefine the read syntax, but we decided to leave this
57 feature out of Emacs Lisp for simplicity.)
59 Each buffer has its own major mode, and each major mode has its own
60 idea of the syntactic class of various characters. For example, in Lisp
61 mode, the character @samp{;} begins a comment, but in C mode, it
62 terminates a statement. To support these variations, Emacs makes the
63 choice of syntax table local to each buffer. Typically, each major
64 mode has its own syntax table and installs that table in each buffer
65 that uses that mode. Changing this table alters the syntax in all
66 those buffers as well as in any buffers subsequently put in that mode.
67 Occasionally several similar modes share one syntax table.
68 @xref{Example Major Modes}, for an example of how to set up a syntax
71 A syntax table can inherit the data for some characters from the
72 standard syntax table, while specifying other characters itself. The
73 ``inherit'' syntax class means ``inherit this character's syntax from
74 the standard syntax table.'' Just changing the standard syntax for a
75 character affects all syntax tables that inherit from it.
77 @defun syntax-table-p object
78 This function returns @code{t} if @var{object} is a syntax table.
81 @node Syntax Descriptors
82 @section Syntax Descriptors
83 @cindex syntax classes
85 This section describes the syntax classes and flags that denote the
86 syntax of a character, and how they are represented as a @dfn{syntax
87 descriptor}, which is a Lisp string that you pass to
88 @code{modify-syntax-entry} to specify the syntax you want.
90 The syntax table specifies a syntax class for each character. There
91 is no necessary relationship between the class of a character in one
92 syntax table and its class in any other table.
94 Each class is designated by a mnemonic character, which serves as the
95 name of the class when you need to specify a class. Usually the
96 designator character is one that is often assigned that class; however,
97 its meaning as a designator is unvarying and independent of what syntax
98 that character currently has. Thus, @samp{\} as a designator character
99 always gives ``escape character'' syntax, regardless of what syntax
100 @samp{\} currently has.
102 @cindex syntax descriptor
103 A syntax descriptor is a Lisp string that specifies a syntax class, a
104 matching character (used only for the parenthesis classes) and flags.
105 The first character is the designator for a syntax class. The second
106 character is the character to match; if it is unused, put a space there.
107 Then come the characters for any desired flags. If no matching
108 character or flags are needed, one character is sufficient.
110 For example, the syntax descriptor for the character @samp{*} in C
111 mode is @samp{@w{. 23}} (i.e., punctuation, matching character slot
112 unused, second character of a comment-starter, first character of a
113 comment-ender), and the entry for @samp{/} is @samp{@w{. 14}} (i.e.,
114 punctuation, matching character slot unused, first character of a
115 comment-starter, second character of a comment-ender).
118 * Syntax Class Table:: Table of syntax classes.
119 * Syntax Flags:: Additional flags each character can have.
122 @node Syntax Class Table
123 @subsection Table of Syntax Classes
125 Here is a table of syntax classes, the characters that stand for them,
126 their meanings, and examples of their use.
128 @deffn {Syntax class} @w{whitespace character}
129 @dfn{Whitespace characters} (designated by @w{@samp{@ }} or @samp{-})
130 separate symbols and words from each other. Typically, whitespace
131 characters have no other syntactic significance, and multiple whitespace
132 characters are syntactically equivalent to a single one. Space, tab,
133 newline and formfeed are classified as whitespace in almost all major
137 @deffn {Syntax class} @w{word constituent}
138 @dfn{Word constituents} (designated by @samp{w}) are parts of words in
139 human languages, and are typically used in variable and command names
140 in programs. All upper- and lower-case letters, and the digits, are
141 typically word constituents.
144 @deffn {Syntax class} @w{symbol constituent}
145 @dfn{Symbol constituents} (designated by @samp{_}) are the extra
146 characters that are used in variable and command names along with word
147 constituents. For example, the symbol constituents class is used in
148 Lisp mode to indicate that certain characters may be part of symbol
149 names even though they are not part of English words. These characters
150 are @samp{$&*+-_<>}. In standard C, the only non-word-constituent
151 character that is valid in symbols is underscore (@samp{_}).
154 @deffn {Syntax class} @w{punctuation character}
155 @dfn{Punctuation characters} (designated by @samp{.}) are those
156 characters that are used as punctuation in English, or are used in some
157 way in a programming language to separate symbols from one another.
158 Most programming language modes, including Emacs Lisp mode, have no
159 characters in this class since the few characters that are not symbol or
160 word constituents all have other uses.
163 @deffn {Syntax class} @w{open parenthesis character}
164 @deffnx {Syntax class} @w{close parenthesis character}
165 @cindex parenthesis syntax
166 Open and close @dfn{parenthesis characters} are characters used in
167 dissimilar pairs to surround sentences or expressions. Such a grouping
168 is begun with an open parenthesis character and terminated with a close.
169 Each open parenthesis character matches a particular close parenthesis
170 character, and vice versa. Normally, Emacs indicates momentarily the
171 matching open parenthesis when you insert a close parenthesis.
174 The class of open parentheses is designated by @samp{(}, and that of
175 close parentheses by @samp{)}.
177 In English text, and in C code, the parenthesis pairs are @samp{()},
178 @samp{[]}, and @samp{@{@}}. In Emacs Lisp, the delimiters for lists and
179 vectors (@samp{()} and @samp{[]}) are classified as parenthesis
183 @deffn {Syntax class} @w{string quote}
184 @dfn{String quote characters} (designated by @samp{"}) are used in
185 many languages, including Lisp and C, to delimit string constants. The
186 same string quote character appears at the beginning and the end of a
187 string. Such quoted strings do not nest.
189 The parsing facilities of Emacs consider a string as a single token.
190 The usual syntactic meanings of the characters in the string are
193 The Lisp modes have two string quote characters: double-quote (@samp{"})
194 and vertical bar (@samp{|}). @samp{|} is not used in Emacs Lisp, but it
195 is used in Common Lisp. C also has two string quote characters:
196 double-quote for strings, and single-quote (@samp{'}) for character
199 English text has no string quote characters because English is not a
200 programming language. Although quotation marks are used in English,
201 we do not want them to turn off the usual syntactic properties of
202 other characters in the quotation.
205 @deffn {Syntax class} @w{escape}
206 An @dfn{escape character} (designated by @samp{\}) starts an escape
207 sequence such as is used in C string and character constants. The
208 character @samp{\} belongs to this class in both C and Lisp. (In C, it
209 is used thus only inside strings, but it turns out to cause no trouble
210 to treat it this way throughout C code.)
212 Characters in this class count as part of words if
213 @code{words-include-escapes} is non-@code{nil}. @xref{Word Motion}.
216 @deffn {Syntax class} @w{character quote}
217 A @dfn{character quote character} (designated by @samp{/}) quotes the
218 following character so that it loses its normal syntactic meaning. This
219 differs from an escape character in that only the character immediately
220 following is ever affected.
222 Characters in this class count as part of words if
223 @code{words-include-escapes} is non-@code{nil}. @xref{Word Motion}.
225 This class is used for backslash in @TeX{} mode.
228 @deffn {Syntax class} @w{paired delimiter}
229 @dfn{Paired delimiter characters} (designated by @samp{$}) are like
230 string quote characters except that the syntactic properties of the
231 characters between the delimiters are not suppressed. Only @TeX{} mode
232 uses a paired delimiter presently---the @samp{$} that both enters and
236 @deffn {Syntax class} @w{expression prefix}
237 An @dfn{expression prefix operator} (designated by @samp{'}) is used for
238 syntactic operators that are considered as part of an expression if they
239 appear next to one. In Lisp modes, these characters include the
240 apostrophe, @samp{'} (used for quoting), the comma, @samp{,} (used in
241 macros), and @samp{#} (used in the read syntax for certain data types).
244 @deffn {Syntax class} @w{comment starter}
245 @deffnx {Syntax class} @w{comment ender}
246 @cindex comment syntax
247 The @dfn{comment starter} and @dfn{comment ender} characters are used in
248 various languages to delimit comments. These classes are designated
249 by @samp{<} and @samp{>}, respectively.
251 English text has no comment characters. In Lisp, the semicolon
252 (@samp{;}) starts a comment and a newline or formfeed ends one.
255 @deffn {Syntax class} @w{inherit}
256 This syntax class does not specify a particular syntax. It says to look
257 in the standard syntax table to find the syntax of this character. The
258 designator for this syntax code is @samp{@@}.
261 @deffn {Syntax class} @w{generic comment delimiter}
262 A @dfn{generic comment delimiter} (designated by @samp{!}) starts
263 or ends a special kind of comment. @emph{Any} generic comment delimiter
264 matches @emph{any} generic comment delimiter, but they cannot match
265 a comment starter or comment ender; generic comment delimiters can only
268 This syntax class is primarily meant for use with the
269 @code{syntax-table} text property (@pxref{Syntax Properties}). You can
270 mark any range of characters as forming a comment, by giving the first
271 and last characters of the range @code{syntax-table} properties
272 identifying them as generic comment delimiters.
275 @deffn {Syntax class} @w{generic string delimiter}
276 A @dfn{generic string delimiter} (designated by @samp{|}) starts or ends
277 a string. This class differs from the string quote class in that @emph{any}
278 generic string delimiter can match any other generic string delimiter; but
279 they do not match ordinary string quote characters.
281 This syntax class is primarily meant for use with the
282 @code{syntax-table} text property (@pxref{Syntax Properties}). You can
283 mark any range of characters as forming a string constant, by giving the
284 first and last characters of the range @code{syntax-table} properties
285 identifying them as generic string delimiters.
289 @subsection Syntax Flags
292 In addition to the classes, entries for characters in a syntax table
293 can specify flags. There are seven possible flags, represented by the
294 characters @samp{1}, @samp{2}, @samp{3}, @samp{4}, @samp{b}, @samp{n},
297 All the flags except @samp{n} and @samp{p} are used to describe
298 multi-character comment delimiters. The digit flags indicate that a
299 character can @emph{also} be part of a comment sequence, in addition to
300 the syntactic properties associated with its character class. The flags
301 are independent of the class and each other for the sake of characters
302 such as @samp{*} in C mode, which is a punctuation character, @emph{and}
303 the second character of a start-of-comment sequence (@samp{/*}),
304 @emph{and} the first character of an end-of-comment sequence
307 Here is a table of the possible flags for a character @var{c},
312 @samp{1} means @var{c} is the start of a two-character comment-start
316 @samp{2} means @var{c} is the second character of such a sequence.
319 @samp{3} means @var{c} is the start of a two-character comment-end
323 @samp{4} means @var{c} is the second character of such a sequence.
327 @samp{b} means that @var{c} as a comment delimiter belongs to the
328 alternative ``b'' comment style.
330 Emacs supports two comment styles simultaneously in any one syntax
331 table. This is for the sake of C++. Each style of comment syntax has
332 its own comment-start sequence and its own comment-end sequence. Each
333 comment must stick to one style or the other; thus, if it starts with
334 the comment-start sequence of style ``b'', it must also end with the
335 comment-end sequence of style ``b''.
337 The two comment-start sequences must begin with the same character; only
338 the second character may differ. Mark the second character of the
339 ``b''-style comment-start sequence with the @samp{b} flag.
341 A comment-end sequence (one or two characters) applies to the ``b''
342 style if its first character has the @samp{b} flag set; otherwise, it
343 applies to the ``a'' style.
345 The appropriate comment syntax settings for C++ are as follows:
356 This defines four comment-delimiting sequences:
360 This is a comment-start sequence for ``a'' style because the
361 second character, @samp{*}, does not have the @samp{b} flag.
364 This is a comment-start sequence for ``b'' style because the second
365 character, @samp{/}, does have the @samp{b} flag.
368 This is a comment-end sequence for ``a'' style because the first
369 character, @samp{*}, does not have the @samp{b} flag.
372 This is a comment-end sequence for ``b'' style, because the newline
373 character has the @samp{b} flag.
377 @samp{n} on a comment delimiter character specifies
378 that this kind of comment can be nested. For a two-character
379 comment delimiter, @samp{n} on either character makes it
384 @samp{p} identifies an additional ``prefix character'' for Lisp syntax.
385 These characters are treated as whitespace when they appear between
386 expressions. When they appear within an expression, they are handled
387 according to their usual syntax codes.
389 The function @code{backward-prefix-chars} moves back over these
390 characters, as well as over characters whose primary syntax class is
391 prefix (@samp{'}). @xref{Motion and Syntax}.
394 @node Syntax Table Functions
395 @section Syntax Table Functions
397 In this section we describe functions for creating, accessing and
398 altering syntax tables.
400 @defun make-syntax-table &optional table
401 This function creates a new syntax table, with all values initialized
402 to @code{nil}. If @var{table} is non-@code{nil}, it becomes the
403 parent of the new syntax table, otherwise the standard syntax table is
404 the parent. Like all char-tables, a syntax table inherits from its
405 parent. Thus the original syntax of all characters in the returned
406 syntax table is determined by the parent. @xref{Char-Tables}.
408 Most major mode syntax tables are created in this way.
411 @defun copy-syntax-table &optional table
412 This function constructs a copy of @var{table} and returns it. If
413 @var{table} is not supplied (or is @code{nil}), it returns a copy of the
414 standard syntax table. Otherwise, an error is signaled if @var{table} is
418 @deffn Command modify-syntax-entry char syntax-descriptor &optional table
419 This function sets the syntax entry for @var{char} according to
420 @var{syntax-descriptor}. The syntax is changed only for @var{table},
421 which defaults to the current buffer's syntax table, and not in any
422 other syntax table. The argument @var{syntax-descriptor} specifies the
423 desired syntax; this is a string beginning with a class designator
424 character, and optionally containing a matching character and flags as
425 well. @xref{Syntax Descriptors}.
427 This function always returns @code{nil}. The old syntax information in
428 the table for this character is discarded.
430 An error is signaled if the first character of the syntax descriptor is not
431 one of the seventeen syntax class designator characters. An error is also
432 signaled if @var{char} is not a character.
436 @exdent @r{Examples:}
438 ;; @r{Put the space character in class whitespace.}
439 (modify-syntax-entry ?\s " ")
444 ;; @r{Make @samp{$} an open parenthesis character,}
445 ;; @r{with @samp{^} as its matching close.}
446 (modify-syntax-entry ?$ "(^")
451 ;; @r{Make @samp{^} a close parenthesis character,}
452 ;; @r{with @samp{$} as its matching open.}
453 (modify-syntax-entry ?^ ")$")
458 ;; @r{Make @samp{/} a punctuation character,}
459 ;; @r{the first character of a start-comment sequence,}
460 ;; @r{and the second character of an end-comment sequence.}
461 ;; @r{This is used in C mode.}
462 (modify-syntax-entry ?/ ". 14")
468 @defun char-syntax character
469 This function returns the syntax class of @var{character}, represented
470 by its mnemonic designator character. This returns @emph{only} the
471 class, not any matching parenthesis or flags.
473 An error is signaled if @var{char} is not a character.
475 The following examples apply to C mode. The first example shows that
476 the syntax class of space is whitespace (represented by a space). The
477 second example shows that the syntax of @samp{/} is punctuation. This
478 does not show the fact that it is also part of comment-start and -end
479 sequences. The third example shows that open parenthesis is in the class
480 of open parentheses. This does not show the fact that it has a matching
485 (string (char-syntax ?\s))
490 (string (char-syntax ?/))
495 (string (char-syntax ?\())
500 We use @code{string} to make it easier to see the character returned by
504 @defun syntax-after pos
505 This function returns a description of the syntax of the character in
506 the buffer after position @var{pos}, taking account of syntax
507 properties as well as the syntax table.
509 The value is usually a syntax class character; however, if the buffer
510 character has parenthesis syntax, the value is a cons cell of the form
511 @code{(@var{class} . @var{match})}, where @var{class} is the syntax
512 class character and @var{match} is the buffer character's matching
516 @defun set-syntax-table table
517 This function makes @var{table} the syntax table for the current buffer.
518 It returns @var{table}.
522 This function returns the current syntax table, which is the table for
526 @defmac with-syntax-table @var{table} @var{body}...
527 @tindex with-syntax-table
528 This macro executes @var{body} using @var{table} as the current syntax
529 table. It returns the value of the last form in @var{body}, after
530 restoring the old current syntax table.
532 Since each buffer has its own current syntax table, we should make that
533 more precise: @code{with-syntax-table} temporarily alters the current
534 syntax table of whichever buffer is current at the time the macro
535 execution starts. Other buffers are not affected.
538 @node Syntax Properties
539 @section Syntax Properties
540 @kindex syntax-table @r{(text property)}
542 When the syntax table is not flexible enough to specify the syntax of a
543 language, you can use @code{syntax-table} text properties to override
544 the syntax table for specific character occurrences in the buffer.
545 @xref{Text Properties}.
547 The valid values of @code{syntax-table} text property are:
550 @item @var{syntax-table}
551 If the property value is a syntax table, that table is used instead of
552 the current buffer's syntax table to determine the syntax for this
553 occurrence of the character.
555 @item @code{(@var{syntax-code} . @var{matching-char})}
556 A cons cell of this format specifies the syntax for this
557 occurrence of the character. (@pxref{Syntax Table Internals})
560 If the property is @code{nil}, the character's syntax is determined from
561 the current syntax table in the usual way.
564 @defvar parse-sexp-lookup-properties
565 If this is non-@code{nil}, the syntax scanning functions pay attention
566 to syntax text properties. Otherwise they use only the current syntax
570 @node Motion and Syntax
571 @section Motion and Syntax
573 This section describes functions for moving across characters that
574 have certain syntax classes.
576 @defun skip-syntax-forward syntaxes &optional limit
577 This function moves point forward across characters having syntax
578 classes mentioned in @var{syntaxes} (a string of syntax code
579 characters). It stops when it encounters the end of the buffer, or
580 position @var{limit} (if specified), or a character it is not supposed
583 If @var{syntaxes} starts with @samp{^}, then the function skips
584 characters whose syntax is @emph{not} in @var{syntaxes}.
586 The return value is the distance traveled, which is a nonnegative
590 @defun skip-syntax-backward syntaxes &optional limit
591 This function moves point backward across characters whose syntax
592 classes are mentioned in @var{syntaxes}. It stops when it encounters
593 the beginning of the buffer, or position @var{limit} (if specified), or
594 a character it is not supposed to skip.
596 If @var{syntaxes} starts with @samp{^}, then the function skips
597 characters whose syntax is @emph{not} in @var{syntaxes}.
599 The return value indicates the distance traveled. It is an integer that
603 @defun backward-prefix-chars
604 This function moves point backward over any number of characters with
605 expression prefix syntax. This includes both characters in the
606 expression prefix syntax class, and characters with the @samp{p} flag.
609 @node Parsing Expressions
610 @section Parsing Balanced Expressions
612 Here are several functions for parsing and scanning balanced
613 expressions, also known as @dfn{sexps}. Basically, a sexp is either a
614 balanced parenthetical grouping, or a symbol name (a sequence of
615 characters whose syntax is either word constituent or symbol
616 constituent). However, characters whose syntax is expression prefix
617 are treated as part of the sexp if they appear next to it.
619 The syntax table controls the interpretation of characters, so these
620 functions can be used for Lisp expressions when in Lisp mode and for C
621 expressions when in C mode. @xref{List Motion}, for convenient
622 higher-level functions for moving over balanced expressions.
624 A syntax table only describes how each character changes the state
625 of the parser, rather than describing the state itself. For example,
626 a string delimiter character toggles the parser state between
627 ``in-string'' and ``in-code'' but the characters inside the string do
628 not have any particular syntax to identify them as such. For example
629 (note that 15 is the syntax code for generic string delimiters),
632 (put-text-property 1 9 'syntax-table '(15 . nil))
636 does not tell Emacs that the first eight chars of the current buffer
637 are a string, but rather that they are all string delimiters. As a
638 result, Emacs treats them as four consecutive empty string constants.
640 Every time you use the parser, you specify it a starting state as
641 well as a starting position. If you omit the starting state, the
642 default is ``top level in parenthesis structure,'' as it would be at
643 the beginning of a function definition. (This is the case for
644 @code{forward-sexp}, which blindly assumes that the starting point is
647 @defun parse-partial-sexp start limit &optional target-depth stop-before state stop-comment
648 This function parses a sexp in the current buffer starting at
649 @var{start}, not scanning past @var{limit}. It stops at position
650 @var{limit} or when certain criteria described below are met, and sets
651 point to the location where parsing stops. It returns a value
652 describing the status of the parse at the point where it stops.
654 If @var{state} is @code{nil}, @var{start} is assumed to be at the top
655 level of parenthesis structure, such as the beginning of a function
656 definition. Alternatively, you might wish to resume parsing in the
657 middle of the structure. To do this, you must provide a @var{state}
658 argument that describes the initial status of parsing.
660 @cindex parenthesis depth
661 If the third argument @var{target-depth} is non-@code{nil}, parsing
662 stops if the depth in parentheses becomes equal to @var{target-depth}.
663 The depth starts at 0, or at whatever is given in @var{state}.
665 If the fourth argument @var{stop-before} is non-@code{nil}, parsing
666 stops when it comes to any character that starts a sexp. If
667 @var{stop-comment} is non-@code{nil}, parsing stops when it comes to the
668 start of a comment. If @var{stop-comment} is the symbol
669 @code{syntax-table}, parsing stops after the start of a comment or a
670 string, or the end of a comment or a string, whichever comes first.
673 The fifth argument @var{state} is a nine-element list of the same form
674 as the value of this function, described below. (It is OK to omit the
675 last element of the nine.) The return value of one call may be used to
676 initialize the state of the parse on another call to
677 @code{parse-partial-sexp}.
679 The result is a list of nine elements describing the final state of
684 The depth in parentheses, counting from 0.
687 @cindex innermost containing parentheses
688 The character position of the start of the innermost parenthetical
689 grouping containing the stopping point; @code{nil} if none.
692 @cindex previous complete subexpression
693 The character position of the start of the last complete subexpression
694 terminated; @code{nil} if none.
697 @cindex inside string
698 Non-@code{nil} if inside a string. More precisely, this is the
699 character that will terminate the string, or @code{t} if a generic
700 string delimiter character should terminate it.
703 @cindex inside comment
704 @code{t} if inside a comment (of either style),
705 or the comment nesting level if inside a kind of comment
709 @cindex quote character
710 @code{t} if point is just after a quote character.
713 The minimum parenthesis depth encountered during this scan.
716 What kind of comment is active: @code{nil} for a comment of style
717 ``a'' or when not inside a comment, @code{t} for a comment of style
718 ``b'', and @code{syntax-table} for a comment that should be ended by a
719 generic comment delimiter character.
722 The string or comment start position. While inside a comment, this is
723 the position where the comment began; while inside a string, this is the
724 position where the string began. When outside of strings and comments,
725 this element is @code{nil}.
728 Elements 0, 3, 4, 5 and 7 are significant in the argument @var{state}.
730 Actually, the return value is currently a list of ten, rather than
731 nine, elements and @var{state} is allowed to be a list of ten elements
732 as well. However, the meaning of the tenth element is subject to
733 change and only the first eight elements of @var{state} need to be
736 @cindex indenting with parentheses
737 This function is most often used to compute indentation for languages
738 that have nested parentheses.
741 @defun scan-lists from count depth
742 This function scans forward @var{count} balanced parenthetical groupings
743 from position @var{from}. It returns the position where the scan stops.
744 If @var{count} is negative, the scan moves backwards.
746 If @var{depth} is nonzero, parenthesis depth counting begins from that
747 value. The only candidates for stopping are places where the depth in
748 parentheses becomes zero; @code{scan-lists} counts @var{count} such
749 places and then stops. Thus, a positive value for @var{depth} means go
750 out @var{depth} levels of parenthesis.
752 Scanning ignores comments if @code{parse-sexp-ignore-comments} is
755 If the scan reaches the beginning or end of the buffer (or its
756 accessible portion), and the depth is not zero, an error is signaled.
757 If the depth is zero but the count is not used up, @code{nil} is
761 @defun scan-sexps from count
762 This function scans forward @var{count} sexps from position @var{from}.
763 It returns the position where the scan stops. If @var{count} is
764 negative, the scan moves backwards.
766 Scanning ignores comments if @code{parse-sexp-ignore-comments} is
769 If the scan reaches the beginning or end of (the accessible part of) the
770 buffer while in the middle of a parenthetical grouping, an error is
771 signaled. If it reaches the beginning or end between groupings but
772 before count is used up, @code{nil} is returned.
775 @defvar multibyte-syntax-as-symbol
776 @tindex multibyte-syntax-as-symbol
777 If this variable is non-@code{nil}, @code{scan-sexps} treats all
778 non-@acronym{ASCII} characters as symbol constituents regardless
779 of what the syntax table says about them. (However, text properties
780 can still override the syntax.)
783 @defopt parse-sexp-ignore-comments
784 @cindex skipping comments
785 If the value is non-@code{nil}, then comments are treated as
786 whitespace by the functions in this section and by @code{forward-sexp}.
789 @vindex parse-sexp-lookup-properties
790 The behaviour of @code{parse-partial-sexp} is also affected by
791 @code{parse-sexp-lookup-properties} (@pxref{Syntax Properties}).
793 You can use @code{forward-comment} to move forward or backward over
794 one comment or several comments.
796 @defun forward-comment count
797 This function moves point forward across @var{count} complete comments
798 (that is, including the starting delimiter and the terminating
799 delimiter if any), plus any whitespace encountered on the way. It
800 moves backward if @var{count} is negative. If it encounters anything
801 other than a comment or whitespace, it stops, leaving point at the
802 place where it stopped. This includes (for instance) finding the end
803 of a comment when moving forward and expecting the beginning of one.
804 The function also stops immediately after moving over the specified
805 number of complete comments. If @var{count} comments are found as
806 expected, with nothing except whitespace between them, it returns
807 @code{t}; otherwise it returns @code{nil}.
809 This function cannot tell whether the ``comments'' it traverses are
810 embedded within a string. If they look like comments, it treats them
814 To move forward over all comments and whitespace following point, use
815 @code{(forward-comment (buffer-size))}. @code{(buffer-size)} is a good
816 argument to use, because the number of comments in the buffer cannot
819 @node Standard Syntax Tables
820 @section Some Standard Syntax Tables
822 Most of the major modes in Emacs have their own syntax tables. Here
825 @defun standard-syntax-table
826 This function returns the standard syntax table, which is the syntax
827 table used in Fundamental mode.
830 @defvar text-mode-syntax-table
831 The value of this variable is the syntax table used in Text mode.
834 @defvar c-mode-syntax-table
835 The value of this variable is the syntax table for C-mode buffers.
838 @defvar emacs-lisp-mode-syntax-table
839 The value of this variable is the syntax table used in Emacs Lisp mode
840 by editing commands. (It has no effect on the Lisp @code{read}
844 @node Syntax Table Internals
845 @section Syntax Table Internals
846 @cindex syntax table internals
848 Lisp programs don't usually work with the elements directly; the
849 Lisp-level syntax table functions usually work with syntax descriptors
850 (@pxref{Syntax Descriptors}). Nonetheless, here we document the
851 internal format. This format is used mostly when manipulating
854 Each element of a syntax table is a cons cell of the form
855 @code{(@var{syntax-code} . @var{matching-char})}. The @sc{car},
856 @var{syntax-code}, is an integer that encodes the syntax class, and any
857 flags. The @sc{cdr}, @var{matching-char}, is non-@code{nil} if
858 a character to match was specified.
860 This table gives the value of @var{syntax-code} which corresponds
861 to each syntactic type.
863 @multitable @columnfractions .05 .3 .3 .3
866 @i{Integer} @i{Class}
868 @i{Integer} @i{Class}
870 @i{Integer} @i{Class}
875 5 @ @ close parenthesis
877 10 @ @ character quote
882 6 @ @ expression prefix
896 8 @ @ paired delimiter
901 4 @ @ open parenthesis
905 14 @ @ generic comment
911 For example, the usual syntax value for @samp{(} is @code{(4 . 41)}.
912 (41 is the character code for @samp{)}.)
914 The flags are encoded in higher order bits, starting 16 bits from the
915 least significant bit. This table gives the power of two which
916 corresponds to each syntax flag.
918 @multitable @columnfractions .05 .3 .3 .3
928 @samp{1} @ @ @code{(lsh 1 16)}
930 @samp{4} @ @ @code{(lsh 1 19)}
932 @samp{b} @ @ @code{(lsh 1 21)}
935 @samp{2} @ @ @code{(lsh 1 17)}
937 @samp{p} @ @ @code{(lsh 1 20)}
939 @samp{n} @ @ @code{(lsh 1 22)}
942 @samp{3} @ @ @code{(lsh 1 18)}
945 @defun string-to-syntax @var{desc}
946 This function returns the internal form @code{(@var{syntax-code} .
947 @var{matching-char})} corresponding to the syntax descriptor @var{desc}.
952 @cindex categories of characters
954 @dfn{Categories} provide an alternate way of classifying characters
955 syntactically. You can define several categories as needed, then
956 independently assign each character to one or more categories. Unlike
957 syntax classes, categories are not mutually exclusive; it is normal for
958 one character to belong to several categories.
960 Each buffer has a @dfn{category table} which records which categories
961 are defined and also which characters belong to each category. Each
962 category table defines its own categories, but normally these are
963 initialized by copying from the standard categories table, so that the
964 standard categories are available in all modes.
966 Each category has a name, which is an @acronym{ASCII} printing character in
967 the range @w{@samp{ }} to @samp{~}. You specify the name of a category
968 when you define it with @code{define-category}.
970 The category table is actually a char-table (@pxref{Char-Tables}).
971 The element of the category table at index @var{c} is a @dfn{category
972 set}---a bool-vector---that indicates which categories character @var{c}
973 belongs to. In this category set, if the element at index @var{cat} is
974 @code{t}, that means category @var{cat} is a member of the set, and that
975 character @var{c} belongs to category @var{cat}.
977 For the next three functions, the optional argument @var{table}
978 defaults to the current buffer's category table.
980 @defun define-category char docstring &optional table
981 This function defines a new category, with name @var{char} and
982 documentation @var{docstring}, for the category table @var{table},
985 @defun category-docstring category &optional table
986 This function returns the documentation string of category @var{category}
987 in category table @var{table}.
990 (category-docstring ?a)
992 (category-docstring ?l)
997 @defun get-unused-category &optional table
998 This function returns a category name (a character) which is not
999 currently defined in @var{table}. If all possible categories are in use
1000 in @var{table}, it returns @code{nil}.
1003 @defun category-table
1004 This function returns the current buffer's category table.
1007 @defun category-table-p object
1008 This function returns @code{t} if @var{object} is a category table,
1009 otherwise @code{nil}.
1012 @defun standard-category-table
1013 This function returns the standard category table.
1016 @defun copy-category-table &optional table
1017 This function constructs a copy of @var{table} and returns it. If
1018 @var{table} is not supplied (or is @code{nil}), it returns a copy of the
1019 standard category table. Otherwise, an error is signaled if @var{table}
1020 is not a category table.
1023 @defun set-category-table table
1024 This function makes @var{table} the category table for the current
1025 buffer. It returns @var{table}.
1028 @defun make-category-table
1029 @tindex make-category-table
1030 This creates and returns an empty category table. In an empty category
1031 table, no categories have been allocated, and no characters belong to
1035 @defun make-category-set categories
1036 This function returns a new category set---a bool-vector---whose initial
1037 contents are the categories listed in the string @var{categories}. The
1038 elements of @var{categories} should be category names; the new category
1039 set has @code{t} for each of those categories, and @code{nil} for all
1043 (make-category-set "al")
1044 @result{} #&128"\0\0\0\0\0\0\0\0\0\0\0\0\2\20\0\0"
1048 @defun char-category-set char
1049 This function returns the category set for character @var{char} in the
1050 current buffer's category table. This is the bool-vector which
1051 records which categories the character @var{char} belongs to. The
1052 function @code{char-category-set} does not allocate storage, because
1053 it returns the same bool-vector that exists in the category table.
1056 (char-category-set ?a)
1057 @result{} #&128"\0\0\0\0\0\0\0\0\0\0\0\0\2\20\0\0"
1061 @defun category-set-mnemonics category-set
1062 This function converts the category set @var{category-set} into a string
1063 containing the characters that designate the categories that are members
1067 (category-set-mnemonics (char-category-set ?a))
1072 @defun modify-category-entry character category &optional table reset
1073 This function modifies the category set of @var{character} in category
1074 table @var{table} (which defaults to the current buffer's category
1077 Normally, it modifies the category set by adding @var{category} to it.
1078 But if @var{reset} is non-@code{nil}, then it deletes @var{category}
1082 @deffn Command describe-categories &optional buffer-or-name
1083 This function describes the category specifications in the current
1084 category table. It inserts the descriptions in a buffer, and then
1085 displays that buffer. If @var{buffer-or-name} is non-@code{nil}, it
1086 describes the category table of that buffer instead.
1090 arch-tag: 4d914e96-0283-445c-9233-75d33662908c