]> code.delx.au - gnu-emacs/blob - lispref/syntax.texi
*** empty log message ***
[gnu-emacs] / lispref / syntax.texi
1 @c -*-texinfo-*-
2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2002, 2003,
4 @c 2004, 2005, 2006 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
8 @chapter Syntax Tables
9 @cindex parsing
10 @cindex syntax table
11 @cindex text parsing
12
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.
20
21 @menu
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.
32 @end menu
33
34 @node Syntax Basics
35 @section Syntax Table Concepts
36
37 @ifnottex
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
45 this chapter.
46 @end ifnottex
47
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
51 question.
52
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.)
58
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
69 table.
70
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.
76
77 @defun syntax-table-p object
78 This function returns @code{t} if @var{object} is a syntax table.
79 @end defun
80
81 @node Syntax Descriptors
82 @section Syntax Descriptors
83 @cindex syntax classes
84
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.
89
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.
93
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.
101
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.
109
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).
116
117 @menu
118 * Syntax Class Table:: Table of syntax classes.
119 * Syntax Flags:: Additional flags each character can have.
120 @end menu
121
122 @node Syntax Class Table
123 @subsection Table of Syntax Classes
124
125 Here is a table of syntax classes, the characters that stand for them,
126 their meanings, and examples of their use.
127
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
134 modes.
135 @end deffn
136
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.
142 @end deffn
143
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{_}).
152 @end deffn
153
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 Some programming language modes, such as 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. Other programming language modes,
161 such as C mode, use punctuation syntax for operators.
162 @end deffn
163
164 @deffn {Syntax class} @w{open parenthesis character}
165 @deffnx {Syntax class} @w{close parenthesis character}
166 @cindex parenthesis syntax
167 Open and close @dfn{parenthesis characters} are characters used in
168 dissimilar pairs to surround sentences or expressions. Such a grouping
169 is begun with an open parenthesis character and terminated with a close.
170 Each open parenthesis character matches a particular close parenthesis
171 character, and vice versa. Normally, Emacs indicates momentarily the
172 matching open parenthesis when you insert a close parenthesis.
173 @xref{Blinking}.
174
175 The class of open parentheses is designated by @samp{(}, and that of
176 close parentheses by @samp{)}.
177
178 In English text, and in C code, the parenthesis pairs are @samp{()},
179 @samp{[]}, and @samp{@{@}}. In Emacs Lisp, the delimiters for lists and
180 vectors (@samp{()} and @samp{[]}) are classified as parenthesis
181 characters.
182 @end deffn
183
184 @deffn {Syntax class} @w{string quote}
185 @dfn{String quote characters} (designated by @samp{"}) are used in
186 many languages, including Lisp and C, to delimit string constants. The
187 same string quote character appears at the beginning and the end of a
188 string. Such quoted strings do not nest.
189
190 The parsing facilities of Emacs consider a string as a single token.
191 The usual syntactic meanings of the characters in the string are
192 suppressed.
193
194 The Lisp modes have two string quote characters: double-quote (@samp{"})
195 and vertical bar (@samp{|}). @samp{|} is not used in Emacs Lisp, but it
196 is used in Common Lisp. C also has two string quote characters:
197 double-quote for strings, and single-quote (@samp{'}) for character
198 constants.
199
200 English text has no string quote characters because English is not a
201 programming language. Although quotation marks are used in English,
202 we do not want them to turn off the usual syntactic properties of
203 other characters in the quotation.
204 @end deffn
205
206 @deffn {Syntax class} @w{escape}
207 An @dfn{escape character} (designated by @samp{\}) starts an escape
208 sequence such as is used in C string and character constants. The
209 character @samp{\} belongs to this class in both C and Lisp. (In C, it
210 is used thus only inside strings, but it turns out to cause no trouble
211 to treat it this way throughout C code.)
212
213 Characters in this class count as part of words if
214 @code{words-include-escapes} is non-@code{nil}. @xref{Word Motion}.
215 @end deffn
216
217 @deffn {Syntax class} @w{character quote}
218 A @dfn{character quote character} (designated by @samp{/}) quotes the
219 following character so that it loses its normal syntactic meaning. This
220 differs from an escape character in that only the character immediately
221 following is ever affected.
222
223 Characters in this class count as part of words if
224 @code{words-include-escapes} is non-@code{nil}. @xref{Word Motion}.
225
226 This class is used for backslash in @TeX{} mode.
227 @end deffn
228
229 @deffn {Syntax class} @w{paired delimiter}
230 @dfn{Paired delimiter characters} (designated by @samp{$}) are like
231 string quote characters except that the syntactic properties of the
232 characters between the delimiters are not suppressed. Only @TeX{} mode
233 uses a paired delimiter presently---the @samp{$} that both enters and
234 leaves math mode.
235 @end deffn
236
237 @deffn {Syntax class} @w{expression prefix}
238 An @dfn{expression prefix operator} (designated by @samp{'}) is used for
239 syntactic operators that are considered as part of an expression if they
240 appear next to one. In Lisp modes, these characters include the
241 apostrophe, @samp{'} (used for quoting), the comma, @samp{,} (used in
242 macros), and @samp{#} (used in the read syntax for certain data types).
243 @end deffn
244
245 @deffn {Syntax class} @w{comment starter}
246 @deffnx {Syntax class} @w{comment ender}
247 @cindex comment syntax
248 The @dfn{comment starter} and @dfn{comment ender} characters are used in
249 various languages to delimit comments. These classes are designated
250 by @samp{<} and @samp{>}, respectively.
251
252 English text has no comment characters. In Lisp, the semicolon
253 (@samp{;}) starts a comment and a newline or formfeed ends one.
254 @end deffn
255
256 @deffn {Syntax class} @w{inherit}
257 This syntax class does not specify a particular syntax. It says to look
258 in the standard syntax table to find the syntax of this character. The
259 designator for this syntax class is @samp{@@}.
260 @end deffn
261
262 @deffn {Syntax class} @w{generic comment delimiter}
263 A @dfn{generic comment delimiter} (designated by @samp{!}) starts
264 or ends a special kind of comment. @emph{Any} generic comment delimiter
265 matches @emph{any} generic comment delimiter, but they cannot match
266 a comment starter or comment ender; generic comment delimiters can only
267 match each other.
268
269 This syntax class is primarily meant for use with the
270 @code{syntax-table} text property (@pxref{Syntax Properties}). You can
271 mark any range of characters as forming a comment, by giving the first
272 and last characters of the range @code{syntax-table} properties
273 identifying them as generic comment delimiters.
274 @end deffn
275
276 @deffn {Syntax class} @w{generic string delimiter}
277 A @dfn{generic string delimiter} (designated by @samp{|}) starts or ends
278 a string. This class differs from the string quote class in that @emph{any}
279 generic string delimiter can match any other generic string delimiter; but
280 they do not match ordinary string quote characters.
281
282 This syntax class is primarily meant for use with the
283 @code{syntax-table} text property (@pxref{Syntax Properties}). You can
284 mark any range of characters as forming a string constant, by giving the
285 first and last characters of the range @code{syntax-table} properties
286 identifying them as generic string delimiters.
287 @end deffn
288
289 @node Syntax Flags
290 @subsection Syntax Flags
291 @cindex syntax flags
292
293 In addition to the classes, entries for characters in a syntax table
294 can specify flags. There are seven possible flags, represented by the
295 characters @samp{1}, @samp{2}, @samp{3}, @samp{4}, @samp{b}, @samp{n},
296 and @samp{p}.
297
298 All the flags except @samp{n} and @samp{p} are used to describe
299 multi-character comment delimiters. The digit flags indicate that a
300 character can @emph{also} be part of a comment sequence, in addition to
301 the syntactic properties associated with its character class. The flags
302 are independent of the class and each other for the sake of characters
303 such as @samp{*} in C mode, which is a punctuation character, @emph{and}
304 the second character of a start-of-comment sequence (@samp{/*}),
305 @emph{and} the first character of an end-of-comment sequence
306 (@samp{*/}).
307
308 Here is a table of the possible flags for a character @var{c},
309 and what they mean:
310
311 @itemize @bullet
312 @item
313 @samp{1} means @var{c} is the start of a two-character comment-start
314 sequence.
315
316 @item
317 @samp{2} means @var{c} is the second character of such a sequence.
318
319 @item
320 @samp{3} means @var{c} is the start of a two-character comment-end
321 sequence.
322
323 @item
324 @samp{4} means @var{c} is the second character of such a sequence.
325
326 @item
327 @c Emacs 19 feature
328 @samp{b} means that @var{c} as a comment delimiter belongs to the
329 alternative ``b'' comment style.
330
331 Emacs supports two comment styles simultaneously in any one syntax
332 table. This is for the sake of C++. Each style of comment syntax has
333 its own comment-start sequence and its own comment-end sequence. Each
334 comment must stick to one style or the other; thus, if it starts with
335 the comment-start sequence of style ``b,'' it must also end with the
336 comment-end sequence of style ``b.''
337
338 The two comment-start sequences must begin with the same character; only
339 the second character may differ. Mark the second character of the
340 ``b''-style comment-start sequence with the @samp{b} flag.
341
342 A comment-end sequence (one or two characters) applies to the ``b''
343 style if its first character has the @samp{b} flag set; otherwise, it
344 applies to the ``a'' style.
345
346 The appropriate comment syntax settings for C++ are as follows:
347
348 @table @asis
349 @item @samp{/}
350 @samp{124b}
351 @item @samp{*}
352 @samp{23}
353 @item newline
354 @samp{>b}
355 @end table
356
357 This defines four comment-delimiting sequences:
358
359 @table @asis
360 @item @samp{/*}
361 This is a comment-start sequence for ``a'' style because the
362 second character, @samp{*}, does not have the @samp{b} flag.
363
364 @item @samp{//}
365 This is a comment-start sequence for ``b'' style because the second
366 character, @samp{/}, does have the @samp{b} flag.
367
368 @item @samp{*/}
369 This is a comment-end sequence for ``a'' style because the first
370 character, @samp{*}, does not have the @samp{b} flag.
371
372 @item newline
373 This is a comment-end sequence for ``b'' style, because the newline
374 character has the @samp{b} flag.
375 @end table
376
377 @item
378 @samp{n} on a comment delimiter character specifies
379 that this kind of comment can be nested. For a two-character
380 comment delimiter, @samp{n} on either character makes it
381 nestable.
382
383 @item
384 @c Emacs 19 feature
385 @samp{p} identifies an additional ``prefix character'' for Lisp syntax.
386 These characters are treated as whitespace when they appear between
387 expressions. When they appear within an expression, they are handled
388 according to their usual syntax classes.
389
390 The function @code{backward-prefix-chars} moves back over these
391 characters, as well as over characters whose primary syntax class is
392 prefix (@samp{'}). @xref{Motion and Syntax}.
393 @end itemize
394
395 @node Syntax Table Functions
396 @section Syntax Table Functions
397
398 In this section we describe functions for creating, accessing and
399 altering syntax tables.
400
401 @defun make-syntax-table &optional table
402 This function creates a new syntax table, with all values initialized
403 to @code{nil}. If @var{table} is non-@code{nil}, it becomes the
404 parent of the new syntax table, otherwise the standard syntax table is
405 the parent. Like all char-tables, a syntax table inherits from its
406 parent. Thus the original syntax of all characters in the returned
407 syntax table is determined by the parent. @xref{Char-Tables}.
408
409 Most major mode syntax tables are created in this way.
410 @end defun
411
412 @defun copy-syntax-table &optional table
413 This function constructs a copy of @var{table} and returns it. If
414 @var{table} is not supplied (or is @code{nil}), it returns a copy of the
415 standard syntax table. Otherwise, an error is signaled if @var{table} is
416 not a syntax table.
417 @end defun
418
419 @deffn Command modify-syntax-entry char syntax-descriptor &optional table
420 This function sets the syntax entry for @var{char} according to
421 @var{syntax-descriptor}. The syntax is changed only for @var{table},
422 which defaults to the current buffer's syntax table, and not in any
423 other syntax table. The argument @var{syntax-descriptor} specifies the
424 desired syntax; this is a string beginning with a class designator
425 character, and optionally containing a matching character and flags as
426 well. @xref{Syntax Descriptors}.
427
428 This function always returns @code{nil}. The old syntax information in
429 the table for this character is discarded.
430
431 An error is signaled if the first character of the syntax descriptor is not
432 one of the seventeen syntax class designator characters. An error is also
433 signaled if @var{char} is not a character.
434
435 @example
436 @group
437 @exdent @r{Examples:}
438
439 ;; @r{Put the space character in class whitespace.}
440 (modify-syntax-entry ?\s " ")
441 @result{} nil
442 @end group
443
444 @group
445 ;; @r{Make @samp{$} an open parenthesis character,}
446 ;; @r{with @samp{^} as its matching close.}
447 (modify-syntax-entry ?$ "(^")
448 @result{} nil
449 @end group
450
451 @group
452 ;; @r{Make @samp{^} a close parenthesis character,}
453 ;; @r{with @samp{$} as its matching open.}
454 (modify-syntax-entry ?^ ")$")
455 @result{} nil
456 @end group
457
458 @group
459 ;; @r{Make @samp{/} a punctuation character,}
460 ;; @r{the first character of a start-comment sequence,}
461 ;; @r{and the second character of an end-comment sequence.}
462 ;; @r{This is used in C mode.}
463 (modify-syntax-entry ?/ ". 14")
464 @result{} nil
465 @end group
466 @end example
467 @end deffn
468
469 @defun char-syntax character
470 This function returns the syntax class of @var{character}, represented
471 by its mnemonic designator character. This returns @emph{only} the
472 class, not any matching parenthesis or flags.
473
474 An error is signaled if @var{char} is not a character.
475
476 The following examples apply to C mode. The first example shows that
477 the syntax class of space is whitespace (represented by a space). The
478 second example shows that the syntax of @samp{/} is punctuation. This
479 does not show the fact that it is also part of comment-start and -end
480 sequences. The third example shows that open parenthesis is in the class
481 of open parentheses. This does not show the fact that it has a matching
482 character, @samp{)}.
483
484 @example
485 @group
486 (string (char-syntax ?\s))
487 @result{} " "
488 @end group
489
490 @group
491 (string (char-syntax ?/))
492 @result{} "."
493 @end group
494
495 @group
496 (string (char-syntax ?\())
497 @result{} "("
498 @end group
499 @end example
500
501 We use @code{string} to make it easier to see the character returned by
502 @code{char-syntax}.
503 @end defun
504
505 @defun set-syntax-table table
506 This function makes @var{table} the syntax table for the current buffer.
507 It returns @var{table}.
508 @end defun
509
510 @defun syntax-table
511 This function returns the current syntax table, which is the table for
512 the current buffer.
513 @end defun
514
515 @defmac with-syntax-table @var{table} @var{body}@dots{}
516 This macro executes @var{body} using @var{table} as the current syntax
517 table. It returns the value of the last form in @var{body}, after
518 restoring the old current syntax table.
519
520 Since each buffer has its own current syntax table, we should make that
521 more precise: @code{with-syntax-table} temporarily alters the current
522 syntax table of whichever buffer is current at the time the macro
523 execution starts. Other buffers are not affected.
524 @end defmac
525
526 @node Syntax Properties
527 @section Syntax Properties
528 @kindex syntax-table @r{(text property)}
529
530 When the syntax table is not flexible enough to specify the syntax of
531 a language, you can use @code{syntax-table} text properties to
532 override the syntax table for specific character occurrences in the
533 buffer. @xref{Text Properties}. You can use Font Lock mode to set
534 @code{syntax-table} text properties. @xref{Setting Syntax
535 Properties}.
536
537 The valid values of @code{syntax-table} text property are:
538
539 @table @asis
540 @item @var{syntax-table}
541 If the property value is a syntax table, that table is used instead of
542 the current buffer's syntax table to determine the syntax for this
543 occurrence of the character.
544
545 @item @code{(@var{syntax-code} . @var{matching-char})}
546 A cons cell of this format specifies the syntax for this
547 occurrence of the character. (@pxref{Syntax Table Internals})
548
549 @item @code{nil}
550 If the property is @code{nil}, the character's syntax is determined from
551 the current syntax table in the usual way.
552 @end table
553
554 @defvar parse-sexp-lookup-properties
555 If this is non-@code{nil}, the syntax scanning functions pay attention
556 to syntax text properties. Otherwise they use only the current syntax
557 table.
558 @end defvar
559
560 @node Motion and Syntax
561 @section Motion and Syntax
562
563 This section describes functions for moving across characters that
564 have certain syntax classes.
565
566 @defun skip-syntax-forward syntaxes &optional limit
567 This function moves point forward across characters having syntax
568 classes mentioned in @var{syntaxes} (a string of syntax class
569 characters). It stops when it encounters the end of the buffer, or
570 position @var{limit} (if specified), or a character it is not supposed
571 to skip.
572
573 If @var{syntaxes} starts with @samp{^}, then the function skips
574 characters whose syntax is @emph{not} in @var{syntaxes}.
575
576 The return value is the distance traveled, which is a nonnegative
577 integer.
578 @end defun
579
580 @defun skip-syntax-backward syntaxes &optional limit
581 This function moves point backward across characters whose syntax
582 classes are mentioned in @var{syntaxes}. It stops when it encounters
583 the beginning of the buffer, or position @var{limit} (if specified), or
584 a character it is not supposed to skip.
585
586 If @var{syntaxes} starts with @samp{^}, then the function skips
587 characters whose syntax is @emph{not} in @var{syntaxes}.
588
589 The return value indicates the distance traveled. It is an integer that
590 is zero or less.
591 @end defun
592
593 @defun backward-prefix-chars
594 This function moves point backward over any number of characters with
595 expression prefix syntax. This includes both characters in the
596 expression prefix syntax class, and characters with the @samp{p} flag.
597 @end defun
598
599 @node Parsing Expressions
600 @section Parsing Balanced Expressions
601
602 Here are several functions for parsing and scanning balanced
603 expressions, also known as @dfn{sexps}. Basically, a sexp is either a
604 balanced parenthetical grouping, or a symbol name (a sequence of
605 characters whose syntax is either word constituent or symbol
606 constituent). However, characters whose syntax is expression prefix
607 are treated as part of the sexp if they appear next to it.
608
609 The syntax table controls the interpretation of characters, so these
610 functions can be used for Lisp expressions when in Lisp mode and for C
611 expressions when in C mode. @xref{List Motion}, for convenient
612 higher-level functions for moving over balanced expressions.
613
614 A syntax table only describes how each character changes the state
615 of the parser, rather than describing the state itself. For example,
616 a string delimiter character toggles the parser state between
617 ``in-string'' and ``in-code'' but the characters inside the string do
618 not have any particular syntax to identify them as such. For example
619 (note that 15 is the syntax code for generic string delimiters),
620
621 @example
622 (put-text-property 1 9 'syntax-table '(15 . nil))
623 @end example
624
625 @noindent
626 does not tell Emacs that the first eight chars of the current buffer
627 are a string, but rather that they are all string delimiters. As a
628 result, Emacs treats them as four consecutive empty string constants.
629
630 Every time you use the parser, you specify it a starting state as
631 well as a starting position. If you omit the starting state, the
632 default is ``top level in parenthesis structure,'' as it would be at
633 the beginning of a function definition. (This is the case for
634 @code{forward-sexp}, which blindly assumes that the starting point is
635 in such a state.)
636
637 @defun parse-partial-sexp start limit &optional target-depth stop-before state stop-comment
638 This function parses a sexp in the current buffer starting at
639 @var{start}, not scanning past @var{limit}. It stops at position
640 @var{limit} or when certain criteria described below are met, and sets
641 point to the location where parsing stops. It returns a value
642 describing the status of the parse at the point where it stops.
643
644 If @var{state} is @code{nil}, @var{start} is assumed to be at the top
645 level of parenthesis structure, such as the beginning of a function
646 definition. Alternatively, you might wish to resume parsing in the
647 middle of the structure. To do this, you must provide a @var{state}
648 argument that describes the initial status of parsing.
649
650 @cindex parenthesis depth
651 If the third argument @var{target-depth} is non-@code{nil}, parsing
652 stops if the depth in parentheses becomes equal to @var{target-depth}.
653 The depth starts at 0, or at whatever is given in @var{state}.
654
655 If the fourth argument @var{stop-before} is non-@code{nil}, parsing
656 stops when it comes to any character that starts a sexp. If
657 @var{stop-comment} is non-@code{nil}, parsing stops when it comes to the
658 start of a comment. If @var{stop-comment} is the symbol
659 @code{syntax-table}, parsing stops after the start of a comment or a
660 string, or the end of a comment or a string, whichever comes first.
661
662 @cindex parse state
663 The fifth argument @var{state} is a ten-element list of the same form
664 as the value of this function, described below. The return value of
665 one call may be used to initialize the state of the parse on another
666 call to @code{parse-partial-sexp}.
667
668 The result is a list of ten elements describing the final state of
669 the parse:
670
671 @enumerate 0
672 @item
673 The depth in parentheses, counting from 0. @strong{Warning:} this can
674 be negative if there are more close parens than open parens between
675 the start of the defun and point.
676
677 @item
678 @cindex innermost containing parentheses
679 The character position of the start of the innermost parenthetical
680 grouping containing the stopping point; @code{nil} if none.
681
682 @item
683 @cindex previous complete subexpression
684 The character position of the start of the last complete subexpression
685 terminated; @code{nil} if none.
686
687 @item
688 @cindex inside string
689 Non-@code{nil} if inside a string. More precisely, this is the
690 character that will terminate the string, or @code{t} if a generic
691 string delimiter character should terminate it.
692
693 @item
694 @cindex inside comment
695 @code{t} if inside a comment (of either style),
696 or the comment nesting level if inside a kind of comment
697 that can be nested.
698
699 @item
700 @cindex quote character
701 @code{t} if point is just after a quote character.
702
703 @item
704 The minimum parenthesis depth encountered during this scan.
705
706 @item
707 What kind of comment is active: @code{nil} for a comment of style
708 ``a'' or when not inside a comment, @code{t} for a comment of style
709 ``b,'' and @code{syntax-table} for a comment that should be ended by a
710 generic comment delimiter character.
711
712 @item
713 The string or comment start position. While inside a comment, this is
714 the position where the comment began; while inside a string, this is the
715 position where the string began. When outside of strings and comments,
716 this element is @code{nil}.
717
718 @item
719 Internal data for continuing the parsing. The meaning of this
720 data is subject to change; it is used if you pass this list
721 as the @var{state} argument to another call.
722 @end enumerate
723
724 Elements 1, 2, and 6 are ignored in the argument @var{state}. Element
725 8 is used only to set the corresponding element of the return value,
726 in certain simple cases. Element 9 is used only to set element 1 of
727 the return value, in trivial cases where parsing starts and stops
728 within the same pair of parentheses.
729
730 @cindex indenting with parentheses
731 This function is most often used to compute indentation for languages
732 that have nested parentheses.
733 @end defun
734
735 @defun syntax-ppss &optional pos
736 This function returns the state that the parser would have at position
737 @var{pos}, if it were started with a default start state at the
738 beginning of the buffer. Thus, it is equivalent to
739 @code{(parse-partial-sexp (point-min) @var{pos})}, except that
740 @code{syntax-ppss} uses a cache to speed up the computation. Also,
741 the 2nd value (previous complete subexpression) and 6th value (minimum
742 parenthesis depth) of the returned state are not meaningful.
743 @end defun
744
745 @defun syntax-ppss-flush-cache beg
746 This function flushes the cache used by @code{syntax-ppss}, starting at
747 position @var{beg}.
748
749 When @code{syntax-ppss} is called, it automatically hooks itself
750 to @code{before-change-functions} to keep its cache consistent.
751 But this can fail if @code{syntax-ppss} is called while
752 @code{before-change-functions} is temporarily let-bound, or if the
753 buffer is modified without obeying the hook, such as when using
754 @code{inhibit-modification-hooks}. For this reason, it is sometimes
755 necessary to flush the cache manually.
756 @end defun
757
758 @defvar syntax-begin-function
759 If this is non-@code{nil}, it should be a function that moves to an
760 earlier buffer position where the parser state is equivalent to
761 @code{nil}---in other words, a position outside of any comment,
762 string, or parenthesis. @code{syntax-ppss} uses it to supplement its
763 cache.
764 @end defvar
765
766 @defun scan-lists from count depth
767 This function scans forward @var{count} balanced parenthetical groupings
768 from position @var{from}. It returns the position where the scan stops.
769 If @var{count} is negative, the scan moves backwards.
770
771 If @var{depth} is nonzero, parenthesis depth counting begins from that
772 value. The only candidates for stopping are places where the depth in
773 parentheses becomes zero; @code{scan-lists} counts @var{count} such
774 places and then stops. Thus, a positive value for @var{depth} means go
775 out @var{depth} levels of parenthesis.
776
777 Scanning ignores comments if @code{parse-sexp-ignore-comments} is
778 non-@code{nil}.
779
780 If the scan reaches the beginning or end of the buffer (or its
781 accessible portion), and the depth is not zero, an error is signaled.
782 If the depth is zero but the count is not used up, @code{nil} is
783 returned.
784 @end defun
785
786 @defun scan-sexps from count
787 This function scans forward @var{count} sexps from position @var{from}.
788 It returns the position where the scan stops. If @var{count} is
789 negative, the scan moves backwards.
790
791 Scanning ignores comments if @code{parse-sexp-ignore-comments} is
792 non-@code{nil}.
793
794 If the scan reaches the beginning or end of (the accessible part of) the
795 buffer while in the middle of a parenthetical grouping, an error is
796 signaled. If it reaches the beginning or end between groupings but
797 before count is used up, @code{nil} is returned.
798 @end defun
799
800 @defvar multibyte-syntax-as-symbol
801 If this variable is non-@code{nil}, @code{scan-sexps} treats all
802 non-@acronym{ASCII} characters as symbol constituents regardless
803 of what the syntax table says about them. (However, text properties
804 can still override the syntax.)
805 @end defvar
806
807 @defopt parse-sexp-ignore-comments
808 @cindex skipping comments
809 If the value is non-@code{nil}, then comments are treated as
810 whitespace by the functions in this section and by @code{forward-sexp}.
811 @end defopt
812
813 @vindex parse-sexp-lookup-properties
814 The behavior of @code{parse-partial-sexp} is also affected by
815 @code{parse-sexp-lookup-properties} (@pxref{Syntax Properties}).
816
817 You can use @code{forward-comment} to move forward or backward over
818 one comment or several comments.
819
820 @defun forward-comment count
821 This function moves point forward across @var{count} complete comments
822 (that is, including the starting delimiter and the terminating
823 delimiter if any), plus any whitespace encountered on the way. It
824 moves backward if @var{count} is negative. If it encounters anything
825 other than a comment or whitespace, it stops, leaving point at the
826 place where it stopped. This includes (for instance) finding the end
827 of a comment when moving forward and expecting the beginning of one.
828 The function also stops immediately after moving over the specified
829 number of complete comments. If @var{count} comments are found as
830 expected, with nothing except whitespace between them, it returns
831 @code{t}; otherwise it returns @code{nil}.
832
833 This function cannot tell whether the ``comments'' it traverses are
834 embedded within a string. If they look like comments, it treats them
835 as comments.
836 @end defun
837
838 To move forward over all comments and whitespace following point, use
839 @code{(forward-comment (buffer-size))}. @code{(buffer-size)} is a good
840 argument to use, because the number of comments in the buffer cannot
841 exceed that many.
842
843 @node Standard Syntax Tables
844 @section Some Standard Syntax Tables
845
846 Most of the major modes in Emacs have their own syntax tables. Here
847 are several of them:
848
849 @defun standard-syntax-table
850 This function returns the standard syntax table, which is the syntax
851 table used in Fundamental mode.
852 @end defun
853
854 @defvar text-mode-syntax-table
855 The value of this variable is the syntax table used in Text mode.
856 @end defvar
857
858 @defvar c-mode-syntax-table
859 The value of this variable is the syntax table for C-mode buffers.
860 @end defvar
861
862 @defvar emacs-lisp-mode-syntax-table
863 The value of this variable is the syntax table used in Emacs Lisp mode
864 by editing commands. (It has no effect on the Lisp @code{read}
865 function.)
866 @end defvar
867
868 @node Syntax Table Internals
869 @section Syntax Table Internals
870 @cindex syntax table internals
871
872 Lisp programs don't usually work with the elements directly; the
873 Lisp-level syntax table functions usually work with syntax descriptors
874 (@pxref{Syntax Descriptors}). Nonetheless, here we document the
875 internal format. This format is used mostly when manipulating
876 syntax properties.
877
878 Each element of a syntax table is a cons cell of the form
879 @code{(@var{syntax-code} . @var{matching-char})}. The @sc{car},
880 @var{syntax-code}, is an integer that encodes the syntax class, and any
881 flags. The @sc{cdr}, @var{matching-char}, is non-@code{nil} if
882 a character to match was specified.
883
884 This table gives the value of @var{syntax-code} which corresponds
885 to each syntactic type.
886
887 @multitable @columnfractions .05 .3 .3 .31
888 @item
889 @tab
890 @i{Integer} @i{Class}
891 @tab
892 @i{Integer} @i{Class}
893 @tab
894 @i{Integer} @i{Class}
895 @item
896 @tab
897 0 @ @ whitespace
898 @tab
899 5 @ @ close parenthesis
900 @tab
901 10 @ @ character quote
902 @item
903 @tab
904 1 @ @ punctuation
905 @tab
906 6 @ @ expression prefix
907 @tab
908 11 @ @ comment-start
909 @item
910 @tab
911 2 @ @ word
912 @tab
913 7 @ @ string quote
914 @tab
915 12 @ @ comment-end
916 @item
917 @tab
918 3 @ @ symbol
919 @tab
920 8 @ @ paired delimiter
921 @tab
922 13 @ @ inherit
923 @item
924 @tab
925 4 @ @ open parenthesis
926 @tab
927 9 @ @ escape
928 @tab
929 14 @ @ generic comment
930 @item
931 @tab
932 15 @ generic string
933 @end multitable
934
935 For example, the usual syntax value for @samp{(} is @code{(4 . 41)}.
936 (41 is the character code for @samp{)}.)
937
938 The flags are encoded in higher order bits, starting 16 bits from the
939 least significant bit. This table gives the power of two which
940 corresponds to each syntax flag.
941
942 @multitable @columnfractions .05 .3 .3 .3
943 @item
944 @tab
945 @i{Prefix} @i{Flag}
946 @tab
947 @i{Prefix} @i{Flag}
948 @tab
949 @i{Prefix} @i{Flag}
950 @item
951 @tab
952 @samp{1} @ @ @code{(lsh 1 16)}
953 @tab
954 @samp{4} @ @ @code{(lsh 1 19)}
955 @tab
956 @samp{b} @ @ @code{(lsh 1 21)}
957 @item
958 @tab
959 @samp{2} @ @ @code{(lsh 1 17)}
960 @tab
961 @samp{p} @ @ @code{(lsh 1 20)}
962 @tab
963 @samp{n} @ @ @code{(lsh 1 22)}
964 @item
965 @tab
966 @samp{3} @ @ @code{(lsh 1 18)}
967 @end multitable
968
969 @defun string-to-syntax @var{desc}
970 This function returns the internal form @code{(@var{syntax-code} .
971 @var{matching-char})} corresponding to the syntax descriptor @var{desc}.
972 @end defun
973
974 @defun syntax-after pos
975 This function returns the syntax code of the character in the buffer
976 after position @var{pos}, taking account of syntax properties as well
977 as the syntax table. If @var{pos} is outside the buffer's accessible
978 portion (@pxref{Narrowing, accessible portion}), this function returns
979 @code{nil}.
980 @end defun
981
982 @defun syntax-class syntax
983 This function returns the syntax class of the syntax code
984 @var{syntax}. (It masks off the high 16 bits that hold the flags
985 encoded in the syntax descriptor.) If @var{syntax} is @code{nil}, it
986 returns @code{nil}; this is so evaluating the expression
987
988 @example
989 (syntax-class (syntax-after pos))
990 @end example
991
992 @noindent
993 where @code{pos} is outside the buffer's accessible portion, will
994 yield @code{nil} without throwing errors or producing wrong syntax
995 class codes.
996 @end defun
997
998 @node Categories
999 @section Categories
1000 @cindex categories of characters
1001
1002 @dfn{Categories} provide an alternate way of classifying characters
1003 syntactically. You can define several categories as needed, then
1004 independently assign each character to one or more categories. Unlike
1005 syntax classes, categories are not mutually exclusive; it is normal for
1006 one character to belong to several categories.
1007
1008 Each buffer has a @dfn{category table} which records which categories
1009 are defined and also which characters belong to each category. Each
1010 category table defines its own categories, but normally these are
1011 initialized by copying from the standard categories table, so that the
1012 standard categories are available in all modes.
1013
1014 Each category has a name, which is an @acronym{ASCII} printing character in
1015 the range @w{@samp{ }} to @samp{~}. You specify the name of a category
1016 when you define it with @code{define-category}.
1017
1018 The category table is actually a char-table (@pxref{Char-Tables}).
1019 The element of the category table at index @var{c} is a @dfn{category
1020 set}---a bool-vector---that indicates which categories character @var{c}
1021 belongs to. In this category set, if the element at index @var{cat} is
1022 @code{t}, that means category @var{cat} is a member of the set, and that
1023 character @var{c} belongs to category @var{cat}.
1024
1025 For the next three functions, the optional argument @var{table}
1026 defaults to the current buffer's category table.
1027
1028 @defun define-category char docstring &optional table
1029 This function defines a new category, with name @var{char} and
1030 documentation @var{docstring}, for the category table @var{table}.
1031 @end defun
1032
1033 @defun category-docstring category &optional table
1034 This function returns the documentation string of category @var{category}
1035 in category table @var{table}.
1036
1037 @example
1038 (category-docstring ?a)
1039 @result{} "ASCII"
1040 (category-docstring ?l)
1041 @result{} "Latin"
1042 @end example
1043 @end defun
1044
1045 @defun get-unused-category &optional table
1046 This function returns a category name (a character) which is not
1047 currently defined in @var{table}. If all possible categories are in use
1048 in @var{table}, it returns @code{nil}.
1049 @end defun
1050
1051 @defun category-table
1052 This function returns the current buffer's category table.
1053 @end defun
1054
1055 @defun category-table-p object
1056 This function returns @code{t} if @var{object} is a category table,
1057 otherwise @code{nil}.
1058 @end defun
1059
1060 @defun standard-category-table
1061 This function returns the standard category table.
1062 @end defun
1063
1064 @defun copy-category-table &optional table
1065 This function constructs a copy of @var{table} and returns it. If
1066 @var{table} is not supplied (or is @code{nil}), it returns a copy of the
1067 standard category table. Otherwise, an error is signaled if @var{table}
1068 is not a category table.
1069 @end defun
1070
1071 @defun set-category-table table
1072 This function makes @var{table} the category table for the current
1073 buffer. It returns @var{table}.
1074 @end defun
1075
1076 @defun make-category-table
1077 This creates and returns an empty category table. In an empty category
1078 table, no categories have been allocated, and no characters belong to
1079 any categories.
1080 @end defun
1081
1082 @defun make-category-set categories
1083 This function returns a new category set---a bool-vector---whose initial
1084 contents are the categories listed in the string @var{categories}. The
1085 elements of @var{categories} should be category names; the new category
1086 set has @code{t} for each of those categories, and @code{nil} for all
1087 other categories.
1088
1089 @example
1090 (make-category-set "al")
1091 @result{} #&128"\0\0\0\0\0\0\0\0\0\0\0\0\2\20\0\0"
1092 @end example
1093 @end defun
1094
1095 @defun char-category-set char
1096 This function returns the category set for character @var{char} in the
1097 current buffer's category table. This is the bool-vector which
1098 records which categories the character @var{char} belongs to. The
1099 function @code{char-category-set} does not allocate storage, because
1100 it returns the same bool-vector that exists in the category table.
1101
1102 @example
1103 (char-category-set ?a)
1104 @result{} #&128"\0\0\0\0\0\0\0\0\0\0\0\0\2\20\0\0"
1105 @end example
1106 @end defun
1107
1108 @defun category-set-mnemonics category-set
1109 This function converts the category set @var{category-set} into a string
1110 containing the characters that designate the categories that are members
1111 of the set.
1112
1113 @example
1114 (category-set-mnemonics (char-category-set ?a))
1115 @result{} "al"
1116 @end example
1117 @end defun
1118
1119 @defun modify-category-entry character category &optional table reset
1120 This function modifies the category set of @var{character} in category
1121 table @var{table} (which defaults to the current buffer's category
1122 table).
1123
1124 Normally, it modifies the category set by adding @var{category} to it.
1125 But if @var{reset} is non-@code{nil}, then it deletes @var{category}
1126 instead.
1127 @end defun
1128
1129 @deffn Command describe-categories &optional buffer-or-name
1130 This function describes the category specifications in the current
1131 category table. It inserts the descriptions in a buffer, and then
1132 displays that buffer. If @var{buffer-or-name} is non-@code{nil}, it
1133 describes the category table of that buffer instead.
1134 @end deffn
1135
1136 @ignore
1137 arch-tag: 4d914e96-0283-445c-9233-75d33662908c
1138 @end ignore