Commit | Line | Data |
---|---|---|
7015aca4 RS |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
b3d90e46 GM |
3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2001, |
4 | @c 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc. | |
7015aca4 RS |
5 | @c See the file elisp.texi for copying conditions. |
6 | @setfilename ../info/searching | |
f9f59935 | 7 | @node Searching and Matching, Syntax Tables, Non-ASCII Characters, Top |
7015aca4 RS |
8 | @chapter Searching and Matching |
9 | @cindex searching | |
10 | ||
11 | GNU Emacs provides two ways to search through a buffer for specified | |
12 | text: exact string searches and regular expression searches. After a | |
13 | regular expression search, you can examine the @dfn{match data} to | |
14 | determine which text matched the whole regular expression or various | |
15 | portions of it. | |
16 | ||
17 | @menu | |
18 | * String Search:: Search for an exact match. | |
99543e8b | 19 | * Searching and Case:: Case-independent or case-significant searching. |
7015aca4 RS |
20 | * Regular Expressions:: Describing classes of strings. |
21 | * Regexp Search:: Searching for a match for a regexp. | |
22697dac | 22 | * POSIX Regexps:: Searching POSIX-style for the longest match. |
2a233172 RS |
23 | * Match Data:: Finding out which part of the text matched, |
24 | after a string or regexp search. | |
99543e8b | 25 | * Search and Replace:: Commands that loop, searching and replacing. |
7015aca4 RS |
26 | * Standard Regexps:: Useful regexps for finding sentences, pages,... |
27 | @end menu | |
28 | ||
29 | The @samp{skip-chars@dots{}} functions also perform a kind of searching. | |
2f680b20 RS |
30 | @xref{Skipping Characters}. To search for changes in character |
31 | properties, see @ref{Property Search}. | |
7015aca4 RS |
32 | |
33 | @node String Search | |
34 | @section Searching for Strings | |
35 | @cindex string search | |
36 | ||
37 | These are the primitive functions for searching through the text in a | |
38 | buffer. They are meant for use in programs, but you may call them | |
8241495d RS |
39 | interactively. If you do so, they prompt for the search string; the |
40 | arguments @var{limit} and @var{noerror} are @code{nil}, and @var{repeat} | |
41 | is 1. | |
7015aca4 | 42 | |
f9f59935 RS |
43 | These search functions convert the search string to multibyte if the |
44 | buffer is multibyte; they convert the search string to unibyte if the | |
45 | buffer is unibyte. @xref{Text Representations}. | |
46 | ||
7015aca4 | 47 | @deffn Command search-forward string &optional limit noerror repeat |
f9f59935 | 48 | This function searches forward from point for an exact match for |
7015aca4 RS |
49 | @var{string}. If successful, it sets point to the end of the occurrence |
50 | found, and returns the new value of point. If no match is found, the | |
51 | value and side effects depend on @var{noerror} (see below). | |
52 | @c Emacs 19 feature | |
53 | ||
f9f59935 | 54 | In the following example, point is initially at the beginning of the |
7015aca4 RS |
55 | line. Then @code{(search-forward "fox")} moves point after the last |
56 | letter of @samp{fox}: | |
57 | ||
58 | @example | |
59 | @group | |
60 | ---------- Buffer: foo ---------- | |
61 | @point{}The quick brown fox jumped over the lazy dog. | |
62 | ---------- Buffer: foo ---------- | |
63 | @end group | |
64 | ||
65 | @group | |
66 | (search-forward "fox") | |
67 | @result{} 20 | |
68 | ||
69 | ---------- Buffer: foo ---------- | |
70 | The quick brown fox@point{} jumped over the lazy dog. | |
71 | ---------- Buffer: foo ---------- | |
72 | @end group | |
73 | @end example | |
74 | ||
f9f59935 | 75 | The argument @var{limit} specifies the upper bound to the search. (It |
7015aca4 RS |
76 | must be a position in the current buffer.) No match extending after |
77 | that position is accepted. If @var{limit} is omitted or @code{nil}, it | |
78 | defaults to the end of the accessible portion of the buffer. | |
79 | ||
80 | @kindex search-failed | |
f9f59935 | 81 | What happens when the search fails depends on the value of |
7015aca4 RS |
82 | @var{noerror}. If @var{noerror} is @code{nil}, a @code{search-failed} |
83 | error is signaled. If @var{noerror} is @code{t}, @code{search-forward} | |
84 | returns @code{nil} and does nothing. If @var{noerror} is neither | |
85 | @code{nil} nor @code{t}, then @code{search-forward} moves point to the | |
f9f59935 RS |
86 | upper bound and returns @code{nil}. (It would be more consistent now to |
87 | return the new position of point in that case, but some existing | |
88 | programs may depend on a value of @code{nil}.) | |
7015aca4 | 89 | |
50363cd8 RS |
90 | The argument @var{noerror} only affects valid searches which fail to |
91 | find a match. Invalid arguments cause errors regardless of | |
92 | @var{noerror}. | |
93 | ||
61cfa852 RS |
94 | If @var{repeat} is supplied (it must be a positive number), then the |
95 | search is repeated that many times (each time starting at the end of the | |
96 | previous time's match). If these successive searches succeed, the | |
97 | function succeeds, moving point and returning its new value. Otherwise | |
bcb6b6b8 LT |
98 | the search fails, with results depending on the value of |
99 | @var{noerror}, as described above. | |
7015aca4 RS |
100 | @end deffn |
101 | ||
102 | @deffn Command search-backward string &optional limit noerror repeat | |
103 | This function searches backward from point for @var{string}. It is | |
104 | just like @code{search-forward} except that it searches backwards and | |
105 | leaves point at the beginning of the match. | |
106 | @end deffn | |
107 | ||
108 | @deffn Command word-search-forward string &optional limit noerror repeat | |
0fb7e7f2 | 109 | @c @cindex word search Redundant |
7015aca4 RS |
110 | This function searches forward from point for a ``word'' match for |
111 | @var{string}. If it finds a match, it sets point to the end of the | |
112 | match found, and returns the new value of point. | |
113 | @c Emacs 19 feature | |
114 | ||
115 | Word matching regards @var{string} as a sequence of words, disregarding | |
116 | punctuation that separates them. It searches the buffer for the same | |
117 | sequence of words. Each word must be distinct in the buffer (searching | |
118 | for the word @samp{ball} does not match the word @samp{balls}), but the | |
119 | details of punctuation and spacing are ignored (searching for @samp{ball | |
120 | boy} does match @samp{ball. Boy!}). | |
121 | ||
122 | In this example, point is initially at the beginning of the buffer; the | |
123 | search leaves it between the @samp{y} and the @samp{!}. | |
124 | ||
125 | @example | |
126 | @group | |
127 | ---------- Buffer: foo ---------- | |
128 | @point{}He said "Please! Find | |
129 | the ball boy!" | |
130 | ---------- Buffer: foo ---------- | |
131 | @end group | |
132 | ||
133 | @group | |
134 | (word-search-forward "Please find the ball, boy.") | |
135 | @result{} 35 | |
136 | ||
137 | ---------- Buffer: foo ---------- | |
138 | He said "Please! Find | |
139 | the ball boy@point{}!" | |
140 | ---------- Buffer: foo ---------- | |
141 | @end group | |
142 | @end example | |
143 | ||
5bb8ca2a RS |
144 | If @var{limit} is non-@code{nil}, it must be a position in the current |
145 | buffer; it specifies the upper bound to the search. The match found | |
146 | must not extend after that position. | |
7015aca4 RS |
147 | |
148 | If @var{noerror} is @code{nil}, then @code{word-search-forward} signals | |
149 | an error if the search fails. If @var{noerror} is @code{t}, then it | |
150 | returns @code{nil} instead of signaling an error. If @var{noerror} is | |
151 | neither @code{nil} nor @code{t}, it moves point to @var{limit} (or the | |
bcb6b6b8 | 152 | end of the accessible portion of the buffer) and returns @code{nil}. |
7015aca4 RS |
153 | |
154 | If @var{repeat} is non-@code{nil}, then the search is repeated that many | |
155 | times. Point is positioned at the end of the last match. | |
156 | @end deffn | |
157 | ||
158 | @deffn Command word-search-backward string &optional limit noerror repeat | |
159 | This function searches backward from point for a word match to | |
160 | @var{string}. This function is just like @code{word-search-forward} | |
161 | except that it searches backward and normally leaves point at the | |
162 | beginning of the match. | |
163 | @end deffn | |
164 | ||
99543e8b RS |
165 | @node Searching and Case |
166 | @section Searching and Case | |
167 | @cindex searching and case | |
168 | ||
169 | By default, searches in Emacs ignore the case of the text they are | |
170 | searching through; if you specify searching for @samp{FOO}, then | |
171 | @samp{Foo} or @samp{foo} is also considered a match. This applies to | |
172 | regular expressions, too; thus, @samp{[aB]} would match @samp{a} or | |
173 | @samp{A} or @samp{b} or @samp{B}. | |
174 | ||
175 | If you do not want this feature, set the variable | |
176 | @code{case-fold-search} to @code{nil}. Then all letters must match | |
177 | exactly, including case. This is a buffer-local variable; altering the | |
178 | variable affects only the current buffer. (@xref{Intro to | |
179 | Buffer-Local}.) Alternatively, you may change the value of | |
180 | @code{default-case-fold-search}, which is the default value of | |
181 | @code{case-fold-search} for buffers that do not override it. | |
182 | ||
183 | Note that the user-level incremental search feature handles case | |
184 | distinctions differently. When given a lower case letter, it looks for | |
185 | a match of either case, but when given an upper case letter, it looks | |
186 | for an upper case letter only. But this has nothing to do with the | |
187 | searching functions used in Lisp code. | |
188 | ||
189 | @defopt case-replace | |
190 | This variable determines whether the higher level replacement | |
191 | functions should preserve case. If the variable is @code{nil}, that | |
192 | means to use the replacement text verbatim. A non-@code{nil} value | |
193 | means to convert the case of the replacement text according to the | |
194 | text being replaced. | |
195 | ||
196 | This variable is used by passing it as an argument to the function | |
197 | @code{replace-match}. @xref{Replacing Match}. | |
198 | @end defopt | |
199 | ||
200 | @defopt case-fold-search | |
201 | This buffer-local variable determines whether searches should ignore | |
202 | case. If the variable is @code{nil} they do not ignore case; otherwise | |
203 | they do ignore case. | |
204 | @end defopt | |
205 | ||
206 | @defvar default-case-fold-search | |
207 | The value of this variable is the default value for | |
208 | @code{case-fold-search} in buffers that do not override it. This is the | |
209 | same as @code{(default-value 'case-fold-search)}. | |
210 | @end defvar | |
211 | ||
7015aca4 RS |
212 | @node Regular Expressions |
213 | @section Regular Expressions | |
214 | @cindex regular expression | |
215 | @cindex regexp | |
216 | ||
217 | A @dfn{regular expression} (@dfn{regexp}, for short) is a pattern that | |
218 | denotes a (possibly infinite) set of strings. Searching for matches for | |
219 | a regexp is a very powerful operation. This section explains how to write | |
220 | regexps; the following section says how to search for them. | |
221 | ||
85b6b13c | 222 | @findex re-builder |
0fb7e7f2 | 223 | @cindex regular expressions, developing |
85b6b13c RS |
224 | For convenient interactive development of regular expressions, you |
225 | can use the @kbd{M-x re-builder} command. It provides a convenient | |
226 | interface for creating regular expressions, by giving immediate visual | |
227 | feedback in a separate buffer. As you edit the regexp, all its | |
228 | matches in the target buffer are highlighted. Each parenthesized | |
229 | sub-expression of the regexp is shown in a distinct face, which makes | |
230 | it easier to verify even very complex regexps. | |
231 | ||
7015aca4 RS |
232 | @menu |
233 | * Syntax of Regexps:: Rules for writing regular expressions. | |
234 | * Regexp Example:: Illustrates regular expression syntax. | |
bcb6b6b8 | 235 | * Regexp Functions:: Functions for operating on regular expressions. |
7015aca4 RS |
236 | @end menu |
237 | ||
238 | @node Syntax of Regexps | |
239 | @subsection Syntax of Regular Expressions | |
240 | ||
61cfa852 RS |
241 | Regular expressions have a syntax in which a few characters are |
242 | special constructs and the rest are @dfn{ordinary}. An ordinary | |
179a6f21 LT |
243 | character is a simple regular expression that matches that character |
244 | and nothing else. The special characters are @samp{.}, @samp{*}, | |
245 | @samp{+}, @samp{?}, @samp{[}, @samp{^}, @samp{$}, and @samp{\}; no new | |
246 | special characters will be defined in the future. The character | |
247 | @samp{]} is special if it ends a character alternative (see later). | |
248 | The character @samp{-} is special inside a character alternative. A | |
249 | @samp{[:} and balancing @samp{:]} enclose a character class inside a | |
250 | character alternative. Any other character appearing in a regular | |
251 | expression is ordinary, unless a @samp{\} precedes it. | |
7015aca4 | 252 | |
8241495d | 253 | For example, @samp{f} is not a special character, so it is ordinary, and |
7015aca4 RS |
254 | therefore @samp{f} is a regular expression that matches the string |
255 | @samp{f} and no other string. (It does @emph{not} match the string | |
8241495d RS |
256 | @samp{fg}, but it does match a @emph{part} of that string.) Likewise, |
257 | @samp{o} is a regular expression that matches only @samp{o}.@refill | |
7015aca4 | 258 | |
8241495d | 259 | Any two regular expressions @var{a} and @var{b} can be concatenated. The |
61cfa852 | 260 | result is a regular expression that matches a string if @var{a} matches |
7015aca4 RS |
261 | some amount of the beginning of that string and @var{b} matches the rest of |
262 | the string.@refill | |
263 | ||
8241495d | 264 | As a simple example, we can concatenate the regular expressions @samp{f} |
7015aca4 RS |
265 | and @samp{o} to get the regular expression @samp{fo}, which matches only |
266 | the string @samp{fo}. Still trivial. To do something more powerful, you | |
8241495d RS |
267 | need to use one of the special regular expression constructs. |
268 | ||
269 | @menu | |
270 | * Regexp Special:: Special characters in regular expressions. | |
271 | * Char Classes:: Character classes used in regular expressions. | |
272 | * Regexp Backslash:: Backslash-sequences in regular expressions. | |
273 | @end menu | |
274 | ||
275 | @node Regexp Special | |
276 | @subsubsection Special Characters in Regular Expressions | |
277 | ||
278 | Here is a list of the characters that are special in a regular | |
279 | expression. | |
7015aca4 | 280 | |
7dd3d99f | 281 | @need 800 |
969fe9b5 RS |
282 | @table @asis |
283 | @item @samp{.}@: @r{(Period)} | |
7015aca4 RS |
284 | @cindex @samp{.} in regexp |
285 | is a special character that matches any single character except a newline. | |
286 | Using concatenation, we can make regular expressions like @samp{a.b}, which | |
287 | matches any three-character string that begins with @samp{a} and ends with | |
288 | @samp{b}.@refill | |
289 | ||
969fe9b5 | 290 | @item @samp{*} |
7015aca4 | 291 | @cindex @samp{*} in regexp |
1cd71ce0 RS |
292 | is not a construct by itself; it is a postfix operator that means to |
293 | match the preceding regular expression repetitively as many times as | |
294 | possible. Thus, @samp{o*} matches any number of @samp{o}s (including no | |
295 | @samp{o}s). | |
7015aca4 RS |
296 | |
297 | @samp{*} always applies to the @emph{smallest} possible preceding | |
1cd71ce0 RS |
298 | expression. Thus, @samp{fo*} has a repeating @samp{o}, not a repeating |
299 | @samp{fo}. It matches @samp{f}, @samp{fo}, @samp{foo}, and so on. | |
7015aca4 | 300 | |
f9f59935 RS |
301 | The matcher processes a @samp{*} construct by matching, immediately, as |
302 | many repetitions as can be found. Then it continues with the rest of | |
303 | the pattern. If that fails, backtracking occurs, discarding some of the | |
304 | matches of the @samp{*}-modified construct in the hope that that will | |
305 | make it possible to match the rest of the pattern. For example, in | |
306 | matching @samp{ca*ar} against the string @samp{caaar}, the @samp{a*} | |
307 | first tries to match all three @samp{a}s; but the rest of the pattern is | |
7015aca4 | 308 | @samp{ar} and there is only @samp{r} left to match, so this try fails. |
f9f59935 | 309 | The next alternative is for @samp{a*} to match only two @samp{a}s. With |
bc023640 | 310 | this choice, the rest of the regexp matches successfully. |
7015aca4 | 311 | |
cd64b8f1 KB |
312 | @strong{Warning:} Nested repetition operators can run for an |
313 | indefinitely long time, if they lead to ambiguous matching. For | |
314 | example, trying to match the regular expression @samp{\(x+y*\)*a} | |
315 | against the string @samp{xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz} could | |
316 | take hours before it ultimately fails. Emacs must try each way of | |
317 | grouping the @samp{x}s before concluding that none of them can work. | |
318 | Even worse, @samp{\(x*\)*} can match the null string in infinitely | |
319 | many ways, so it causes an infinite loop. To avoid these problems, | |
320 | check nested repetitions carefully, to make sure that they do not | |
321 | cause combinatorial explosions in backtracking. | |
73031603 | 322 | |
969fe9b5 | 323 | @item @samp{+} |
7015aca4 | 324 | @cindex @samp{+} in regexp |
1cd71ce0 RS |
325 | is a postfix operator, similar to @samp{*} except that it must match |
326 | the preceding expression at least once. So, for example, @samp{ca+r} | |
7015aca4 RS |
327 | matches the strings @samp{car} and @samp{caaaar} but not the string |
328 | @samp{cr}, whereas @samp{ca*r} matches all three strings. | |
329 | ||
969fe9b5 | 330 | @item @samp{?} |
7015aca4 | 331 | @cindex @samp{?} in regexp |
f9f59935 | 332 | is a postfix operator, similar to @samp{*} except that it must match the |
1cd71ce0 RS |
333 | preceding expression either once or not at all. For example, |
334 | @samp{ca?r} matches @samp{car} or @samp{cr}; nothing else. | |
7015aca4 | 335 | |
c082a348 RS |
336 | @item @samp{*?}, @samp{+?}, @samp{??} |
337 | These are ``non-greedy'' variants of the operators @samp{*}, @samp{+} | |
338 | and @samp{?}. Where those operators match the largest possible | |
339 | substring (consistent with matching the entire containing expression), | |
340 | the non-greedy variants match the smallest possible substring | |
341 | (consistent with matching the entire containing expression). | |
342 | ||
343 | For example, the regular expression @samp{c[ad]*a} when applied to the | |
344 | string @samp{cdaaada} matches the whole string; but the regular | |
345 | expression @samp{c[ad]*?a}, applied to that same string, matches just | |
346 | @samp{cda}. (The smallest possible match here for @samp{[ad]*?} that | |
347 | permits the whole expression to match is @samp{d}.) | |
348 | ||
969fe9b5 RS |
349 | @item @samp{[ @dots{} ]} |
350 | @cindex character alternative (in regexp) | |
7015aca4 RS |
351 | @cindex @samp{[} in regexp |
352 | @cindex @samp{]} in regexp | |
969fe9b5 RS |
353 | is a @dfn{character alternative}, which begins with @samp{[} and is |
354 | terminated by @samp{]}. In the simplest case, the characters between | |
355 | the two brackets are what this character alternative can match. | |
1cd71ce0 RS |
356 | |
357 | Thus, @samp{[ad]} matches either one @samp{a} or one @samp{d}, and | |
358 | @samp{[ad]*} matches any string composed of just @samp{a}s and @samp{d}s | |
359 | (including the empty string), from which it follows that @samp{c[ad]*r} | |
360 | matches @samp{cr}, @samp{car}, @samp{cdr}, @samp{caddaar}, etc. | |
361 | ||
969fe9b5 RS |
362 | You can also include character ranges in a character alternative, by |
363 | writing the starting and ending characters with a @samp{-} between them. | |
bcb6b6b8 LT |
364 | Thus, @samp{[a-z]} matches any lower-case @acronym{ASCII} letter. |
365 | Ranges may be intermixed freely with individual characters, as in | |
366 | @samp{[a-z$%.]}, which matches any lower case @acronym{ASCII} letter | |
367 | or @samp{$}, @samp{%} or period. | |
1cd71ce0 RS |
368 | |
369 | Note that the usual regexp special characters are not special inside a | |
86494bd5 | 370 | character alternative. A completely different set of characters is |
969fe9b5 | 371 | special inside character alternatives: @samp{]}, @samp{-} and @samp{^}. |
1cd71ce0 | 372 | |
969fe9b5 RS |
373 | To include a @samp{]} in a character alternative, you must make it the |
374 | first character. For example, @samp{[]a]} matches @samp{]} or @samp{a}. | |
375 | To include a @samp{-}, write @samp{-} as the first or last character of | |
376 | the character alternative, or put it after a range. Thus, @samp{[]-]} | |
377 | matches both @samp{]} and @samp{-}. | |
7015aca4 | 378 | |
969fe9b5 RS |
379 | To include @samp{^} in a character alternative, put it anywhere but at |
380 | the beginning. | |
7015aca4 | 381 | |
8f17d892 RS |
382 | The beginning and end of a range of multibyte characters must be in |
383 | the same character set (@pxref{Character Sets}). Thus, | |
384 | @code{"[\x8e0-\x97c]"} is invalid because character 0x8e0 (@samp{a} | |
385 | with grave accent) is in the Emacs character set for Latin-1 but the | |
386 | character 0x97c (@samp{u} with diaeresis) is in the Emacs character | |
387 | set for Latin-2. (We use Lisp string syntax to write that example, | |
388 | and a few others in the next few paragraphs, in order to include hex | |
389 | escape sequences in them.) | |
6cc089d2 DL |
390 | |
391 | If a range starts with a unibyte character @var{c} and ends with a | |
392 | multibyte character @var{c2}, the range is divided into two parts: one | |
393 | is @samp{@var{c}..?\377}, the other is @samp{@var{c1}..@var{c2}}, where | |
394 | @var{c1} is the first character of the charset to which @var{c2} | |
395 | belongs. | |
177c0ea7 | 396 | |
ad800164 | 397 | You cannot always match all non-@acronym{ASCII} characters with the regular |
8f17d892 | 398 | expression @code{"[\200-\377]"}. This works when searching a unibyte |
8241495d | 399 | buffer or string (@pxref{Text Representations}), but not in a multibyte |
ad800164 | 400 | buffer or string, because many non-@acronym{ASCII} characters have codes |
8f17d892 | 401 | above octal 0377. However, the regular expression @code{"[^\000-\177]"} |
ad800164 | 402 | does match all non-@acronym{ASCII} characters (see below regarding @samp{^}), |
8241495d | 403 | in both multibyte and unibyte representations, because only the |
ad800164 | 404 | @acronym{ASCII} characters are excluded. |
8241495d | 405 | |
63f508b4 | 406 | A character alternative can also specify named |
8241495d RS |
407 | character classes (@pxref{Char Classes}). This is a POSIX feature whose |
408 | syntax is @samp{[:@var{class}:]}. Using a character class is equivalent | |
409 | to mentioning each of the characters in that class; but the latter is | |
410 | not feasible in practice, since some classes include thousands of | |
411 | different characters. | |
412 | ||
969fe9b5 | 413 | @item @samp{[^ @dots{} ]} |
7015aca4 | 414 | @cindex @samp{^} in regexp |
342fd6cd RS |
415 | @samp{[^} begins a @dfn{complemented character alternative}. This |
416 | matches any character except the ones specified. Thus, | |
417 | @samp{[^a-z0-9A-Z]} matches all characters @emph{except} letters and | |
418 | digits. | |
7015aca4 | 419 | |
969fe9b5 | 420 | @samp{^} is not special in a character alternative unless it is the first |
7015aca4 | 421 | character. The character following the @samp{^} is treated as if it |
1cd71ce0 | 422 | were first (in other words, @samp{-} and @samp{]} are not special there). |
7015aca4 | 423 | |
969fe9b5 | 424 | A complemented character alternative can match a newline, unless newline is |
1cd71ce0 RS |
425 | mentioned as one of the characters not to match. This is in contrast to |
426 | the handling of regexps in programs such as @code{grep}. | |
7015aca4 | 427 | |
969fe9b5 | 428 | @item @samp{^} |
7015aca4 | 429 | @cindex beginning of line in regexp |
bcb6b6b8 LT |
430 | When matching a buffer, @samp{^} matches the empty string, but only at the |
431 | beginning of a line in the text being matched (or the beginning of the | |
432 | accessible portion of the buffer). Otherwise it fails to match | |
433 | anything. Thus, @samp{^foo} matches a @samp{foo} that occurs at the | |
434 | beginning of a line. | |
7015aca4 | 435 | |
61cfa852 | 436 | When matching a string instead of a buffer, @samp{^} matches at the |
8f17d892 | 437 | beginning of the string or after a newline character. |
7015aca4 | 438 | |
8241495d | 439 | For historical compatibility reasons, @samp{^} can be used only at the |
6cd77d30 RS |
440 | beginning of the regular expression, or after @samp{\(}, @samp{\(?:} |
441 | or @samp{\|}. | |
8241495d | 442 | |
969fe9b5 | 443 | @item @samp{$} |
7015aca4 | 444 | @cindex @samp{$} in regexp |
8241495d | 445 | @cindex end of line in regexp |
bcb6b6b8 LT |
446 | is similar to @samp{^} but matches only at the end of a line (or the |
447 | end of the accessible portion of the buffer). Thus, @samp{x+$} | |
448 | matches a string of one @samp{x} or more at the end of a line. | |
7015aca4 | 449 | |
61cfa852 | 450 | When matching a string instead of a buffer, @samp{$} matches at the end |
8f17d892 | 451 | of the string or before a newline character. |
7015aca4 | 452 | |
8241495d RS |
453 | For historical compatibility reasons, @samp{$} can be used only at the |
454 | end of the regular expression, or before @samp{\)} or @samp{\|}. | |
455 | ||
969fe9b5 | 456 | @item @samp{\} |
7015aca4 RS |
457 | @cindex @samp{\} in regexp |
458 | has two functions: it quotes the special characters (including | |
459 | @samp{\}), and it introduces additional special constructs. | |
460 | ||
461 | Because @samp{\} quotes special characters, @samp{\$} is a regular | |
61cfa852 RS |
462 | expression that matches only @samp{$}, and @samp{\[} is a regular |
463 | expression that matches only @samp{[}, and so on. | |
7015aca4 RS |
464 | |
465 | Note that @samp{\} also has special meaning in the read syntax of Lisp | |
466 | strings (@pxref{String Type}), and must be quoted with @samp{\}. For | |
467 | example, the regular expression that matches the @samp{\} character is | |
468 | @samp{\\}. To write a Lisp string that contains the characters | |
469 | @samp{\\}, Lisp syntax requires you to quote each @samp{\} with another | |
470 | @samp{\}. Therefore, the read syntax for a regular expression matching | |
471 | @samp{\} is @code{"\\\\"}.@refill | |
472 | @end table | |
473 | ||
b22f3a19 | 474 | @strong{Please note:} For historical compatibility, special characters |
7015aca4 RS |
475 | are treated as ordinary ones if they are in contexts where their special |
476 | meanings make no sense. For example, @samp{*foo} treats @samp{*} as | |
477 | ordinary since there is no preceding expression on which the @samp{*} | |
61cfa852 RS |
478 | can act. It is poor practice to depend on this behavior; quote the |
479 | special character anyway, regardless of where it appears.@refill | |
7015aca4 | 480 | |
179a6f21 LT |
481 | As a @samp{\} is not special inside a character alternative, it can |
482 | never remove the special meaning of @samp{-} or @samp{]}. So you | |
483 | should not quote these characters when they have no special meaning | |
484 | either. This would not clarify anything, since backslashes can | |
485 | legitimately precede these characters where they @emph{have} special | |
ba44fca9 | 486 | meaning, as in @samp{[^\]} (@code{"[^\\]"} for Lisp string syntax), |
179a6f21 LT |
487 | which matches any single character except a backslash. |
488 | ||
489 | In practice, most @samp{]} that occur in regular expressions close a | |
490 | character alternative and hence are special. However, occasionally a | |
491 | regular expression may try to match a complex pattern of literal | |
492 | @samp{[} and @samp{]}. In such situations, it sometimes may be | |
493 | necessary to carefully parse the regexp from the start to determine | |
494 | which square brackets enclose a character alternative. For example, | |
ba44fca9 LT |
495 | @samp{[^][]]} consists of the complemented character alternative |
496 | @samp{[^][]} (which matches any single character that is not a square | |
1ab7aea1 | 497 | bracket), followed by a literal @samp{]}. |
179a6f21 LT |
498 | |
499 | The exact rules are that at the beginning of a regexp, @samp{[} is | |
500 | special and @samp{]} not. This lasts until the first unquoted | |
501 | @samp{[}, after which we are in a character alternative; @samp{[} is | |
502 | no longer special (except when it starts a character class) but @samp{]} | |
503 | is special, unless it immediately follows the special @samp{[} or that | |
504 | @samp{[} followed by a @samp{^}. This lasts until the next special | |
505 | @samp{]} that does not end a character class. This ends the character | |
506 | alternative and restores the ordinary syntax of regular expressions; | |
507 | an unquoted @samp{[} is special again and a @samp{]} not. | |
508 | ||
8241495d RS |
509 | @node Char Classes |
510 | @subsubsection Character Classes | |
511 | @cindex character classes in regexp | |
512 | ||
513 | Here is a table of the classes you can use in a character alternative, | |
63f508b4 | 514 | and what they mean: |
8241495d RS |
515 | |
516 | @table @samp | |
517 | @item [:ascii:] | |
1bae538c | 518 | This matches any @acronym{ASCII} character (codes 0--127). |
8241495d RS |
519 | @item [:alnum:] |
520 | This matches any letter or digit. (At present, for multibyte | |
521 | characters, it matches anything that has word syntax.) | |
522 | @item [:alpha:] | |
523 | This matches any letter. (At present, for multibyte characters, it | |
524 | matches anything that has word syntax.) | |
525 | @item [:blank:] | |
526 | This matches space and tab only. | |
527 | @item [:cntrl:] | |
ad800164 | 528 | This matches any @acronym{ASCII} control character. |
8241495d RS |
529 | @item [:digit:] |
530 | This matches @samp{0} through @samp{9}. Thus, @samp{[-+[:digit:]]} | |
531 | matches any digit, as well as @samp{+} and @samp{-}. | |
532 | @item [:graph:] | |
ad800164 | 533 | This matches graphic characters---everything except @acronym{ASCII} control |
75708135 | 534 | characters, space, and the delete character. |
8241495d RS |
535 | @item [:lower:] |
536 | This matches any lower-case letter, as determined by | |
537 | the current case table (@pxref{Case Tables}). | |
1bae538c RS |
538 | @item [:multibyte:] |
539 | This matches any multibyte character (@pxref{Text Representations}). | |
8241495d | 540 | @item [:nonascii:] |
1bae538c | 541 | This matches any non-@acronym{ASCII} character. |
8241495d | 542 | @item [:print:] |
ad800164 | 543 | This matches printing characters---everything except @acronym{ASCII} control |
caccdcbb | 544 | characters and the delete character. |
8241495d RS |
545 | @item [:punct:] |
546 | This matches any punctuation character. (At present, for multibyte | |
547 | characters, it matches anything that has non-word syntax.) | |
548 | @item [:space:] | |
549 | This matches any character that has whitespace syntax | |
550 | (@pxref{Syntax Class Table}). | |
1bae538c RS |
551 | @item [:unibyte:] |
552 | This matches any unibyte character (@pxref{Text Representations}). | |
8241495d RS |
553 | @item [:upper:] |
554 | This matches any upper-case letter, as determined by | |
555 | the current case table (@pxref{Case Tables}). | |
556 | @item [:word:] | |
557 | This matches any character that has word syntax (@pxref{Syntax Class | |
558 | Table}). | |
559 | @item [:xdigit:] | |
560 | This matches the hexadecimal digits: @samp{0} through @samp{9}, @samp{a} | |
561 | through @samp{f} and @samp{A} through @samp{F}. | |
562 | @end table | |
563 | ||
564 | @node Regexp Backslash | |
565 | @subsubsection Backslash Constructs in Regular Expressions | |
566 | ||
567 | For the most part, @samp{\} followed by any character matches only | |
568 | that character. However, there are several exceptions: certain | |
569 | two-character sequences starting with @samp{\} that have special | |
570 | meanings. (The character after the @samp{\} in such a sequence is | |
571 | always ordinary when used on its own.) Here is a table of the special | |
572 | @samp{\} constructs. | |
7015aca4 | 573 | |
969fe9b5 | 574 | @table @samp |
7015aca4 RS |
575 | @item \| |
576 | @cindex @samp{|} in regexp | |
577 | @cindex regexp alternative | |
578 | specifies an alternative. | |
579 | Two regular expressions @var{a} and @var{b} with @samp{\|} in | |
580 | between form an expression that matches anything that either @var{a} or | |
581 | @var{b} matches.@refill | |
582 | ||
583 | Thus, @samp{foo\|bar} matches either @samp{foo} or @samp{bar} | |
584 | but no other string.@refill | |
585 | ||
586 | @samp{\|} applies to the largest possible surrounding expressions. Only a | |
587 | surrounding @samp{\( @dots{} \)} grouping can limit the grouping power of | |
588 | @samp{\|}.@refill | |
589 | ||
01913af2 RS |
590 | If you need full backtracking capability to handle multiple uses of |
591 | @samp{\|}, use the POSIX regular expression functions (@pxref{POSIX | |
592 | Regexps}). | |
7015aca4 | 593 | |
2d06696f RS |
594 | @item \@{@var{m}\@} |
595 | is a postfix operator that repeats the previous pattern exactly @var{m} | |
596 | times. Thus, @samp{x\@{5\@}} matches the string @samp{xxxxx} | |
597 | and nothing else. @samp{c[ad]\@{3\@}r} matches string such as | |
598 | @samp{caaar}, @samp{cdddr}, @samp{cadar}, and so on. | |
599 | ||
600 | @item \@{@var{m},@var{n}\@} | |
2a233172 | 601 | is a more general postfix operator that specifies repetition with a |
2d06696f RS |
602 | minimum of @var{m} repeats and a maximum of @var{n} repeats. If @var{m} |
603 | is omitted, the minimum is 0; if @var{n} is omitted, there is no | |
604 | maximum. | |
605 | ||
606 | For example, @samp{c[ad]\@{1,2\@}r} matches the strings @samp{car}, | |
607 | @samp{cdr}, @samp{caar}, @samp{cadr}, @samp{cdar}, and @samp{cddr}, and | |
608 | nothing else.@* | |
609 | @samp{\@{0,1\@}} or @samp{\@{,1\@}} is equivalent to @samp{?}. @* | |
610 | @samp{\@{0,\@}} or @samp{\@{,\@}} is equivalent to @samp{*}. @* | |
611 | @samp{\@{1,\@}} is equivalent to @samp{+}. | |
612 | ||
7015aca4 RS |
613 | @item \( @dots{} \) |
614 | @cindex @samp{(} in regexp | |
615 | @cindex @samp{)} in regexp | |
616 | @cindex regexp grouping | |
617 | is a grouping construct that serves three purposes: | |
618 | ||
619 | @enumerate | |
620 | @item | |
9e2b495b RS |
621 | To enclose a set of @samp{\|} alternatives for other operations. Thus, |
622 | the regular expression @samp{\(foo\|bar\)x} matches either @samp{foox} | |
623 | or @samp{barx}. | |
7015aca4 RS |
624 | |
625 | @item | |
1cd71ce0 RS |
626 | To enclose a complicated expression for the postfix operators @samp{*}, |
627 | @samp{+} and @samp{?} to operate on. Thus, @samp{ba\(na\)*} matches | |
a9f0a989 RS |
628 | @samp{ba}, @samp{bana}, @samp{banana}, @samp{bananana}, etc., with any |
629 | number (zero or more) of @samp{na} strings. | |
7015aca4 RS |
630 | |
631 | @item | |
2d06696f RS |
632 | To record a matched substring for future reference with |
633 | @samp{\@var{digit}} (see below). | |
7015aca4 RS |
634 | @end enumerate |
635 | ||
636 | This last application is not a consequence of the idea of a | |
2d06696f RS |
637 | parenthetical grouping; it is a separate feature that was assigned as a |
638 | second meaning to the same @samp{\( @dots{} \)} construct because, in | |
a39c2e0d | 639 | practice, there was usually no conflict between the two meanings. But |
2d06696f RS |
640 | occasionally there is a conflict, and that led to the introduction of |
641 | shy groups. | |
642 | ||
643 | @item \(?: @dots{} \) | |
644 | is the @dfn{shy group} construct. A shy group serves the first two | |
645 | purposes of an ordinary group (controlling the nesting of other | |
646 | operators), but it does not get a number, so you cannot refer back to | |
647 | its value with @samp{\@var{digit}}. | |
648 | ||
bcb6b6b8 | 649 | Shy groups are particularly useful for mechanically-constructed regular |
2d06696f RS |
650 | expressions because they can be added automatically without altering the |
651 | numbering of any ordinary, non-shy groups. | |
7015aca4 | 652 | |
c69b0314 SM |
653 | @item \(?@var{num}: @dots{} \) |
654 | is the @dfn{explicitly numbered group} construct. Normal groups get | |
655 | their number implicitly, based on their position, which can be | |
656 | inconvenient. This construct allows you to force a particular group | |
657 | number. There is no particular restriction on the numbering, | |
9f505b2e SM |
658 | e.g.@: you can have several groups with the same number in which case |
659 | the last one to match (i.e.@: the rightmost match) will win. | |
c69b0314 SM |
660 | Implicitly numbered groups always get the smallest integer larger than |
661 | the one of any previous group. | |
662 | ||
7015aca4 | 663 | @item \@var{digit} |
61cfa852 | 664 | matches the same text that matched the @var{digit}th occurrence of a |
a5d0a32e | 665 | grouping (@samp{\( @dots{} \)}) construct. |
7015aca4 | 666 | |
a5d0a32e RS |
667 | In other words, after the end of a group, the matcher remembers the |
668 | beginning and end of the text matched by that group. Later on in the | |
669 | regular expression you can use @samp{\} followed by @var{digit} to | |
670 | match that same text, whatever it may have been. | |
7015aca4 | 671 | |
a5d0a32e RS |
672 | The strings matching the first nine grouping constructs appearing in |
673 | the entire regular expression passed to a search or matching function | |
674 | are assigned numbers 1 through 9 in the order that the open | |
675 | parentheses appear in the regular expression. So you can use | |
676 | @samp{\1} through @samp{\9} to refer to the text matched by the | |
677 | corresponding grouping constructs. | |
7015aca4 RS |
678 | |
679 | For example, @samp{\(.*\)\1} matches any newline-free string that is | |
680 | composed of two identical halves. The @samp{\(.*\)} matches the first | |
681 | half, which may be anything, but the @samp{\1} that follows must match | |
682 | the same exact text. | |
683 | ||
bcb6b6b8 LT |
684 | If a @samp{\( @dots{} \)} construct matches more than once (which can |
685 | happen, for instance, if it is followed by @samp{*}), only the last | |
686 | match is recorded. | |
687 | ||
a5d0a32e RS |
688 | If a particular grouping construct in the regular expression was never |
689 | matched---for instance, if it appears inside of an alternative that | |
690 | wasn't used, or inside of a repetition that repeated zero times---then | |
691 | the corresponding @samp{\@var{digit}} construct never matches | |
692 | anything. To use an artificial example,, @samp{\(foo\(b*\)\|lose\)\2} | |
693 | cannot match @samp{lose}: the second alternative inside the larger | |
694 | group matches it, but then @samp{\2} is undefined and can't match | |
695 | anything. But it can match @samp{foobb}, because the first | |
696 | alternative matches @samp{foob} and @samp{\2} matches @samp{b}. | |
697 | ||
7015aca4 RS |
698 | @item \w |
699 | @cindex @samp{\w} in regexp | |
700 | matches any word-constituent character. The editor syntax table | |
701 | determines which characters these are. @xref{Syntax Tables}. | |
702 | ||
703 | @item \W | |
704 | @cindex @samp{\W} in regexp | |
61cfa852 | 705 | matches any character that is not a word constituent. |
7015aca4 RS |
706 | |
707 | @item \s@var{code} | |
708 | @cindex @samp{\s} in regexp | |
709 | matches any character whose syntax is @var{code}. Here @var{code} is a | |
61cfa852 | 710 | character that represents a syntax code: thus, @samp{w} for word |
7015aca4 | 711 | constituent, @samp{-} for whitespace, @samp{(} for open parenthesis, |
f9f59935 RS |
712 | etc. To represent whitespace syntax, use either @samp{-} or a space |
713 | character. @xref{Syntax Class Table}, for a list of syntax codes and | |
714 | the characters that stand for them. | |
7015aca4 RS |
715 | |
716 | @item \S@var{code} | |
717 | @cindex @samp{\S} in regexp | |
718 | matches any character whose syntax is not @var{code}. | |
a8b5bbef DL |
719 | |
720 | @item \c@var{c} | |
721 | matches any character whose category is @var{c}. Here @var{c} is a | |
722 | character that represents a category: thus, @samp{c} for Chinese | |
723 | characters or @samp{g} for Greek characters in the standard category | |
724 | table. | |
725 | ||
726 | @item \C@var{c} | |
727 | matches any character whose category is not @var{c}. | |
7015aca4 RS |
728 | @end table |
729 | ||
61cfa852 | 730 | The following regular expression constructs match the empty string---that is, |
7015aca4 | 731 | they don't use up any characters---but whether they match depends on the |
bcb6b6b8 LT |
732 | context. For all, the beginning and end of the accessible portion of |
733 | the buffer are treated as if they were the actual beginning and end of | |
734 | the buffer. | |
7015aca4 | 735 | |
969fe9b5 | 736 | @table @samp |
7015aca4 RS |
737 | @item \` |
738 | @cindex @samp{\`} in regexp | |
739 | matches the empty string, but only at the beginning | |
740 | of the buffer or string being matched against. | |
741 | ||
742 | @item \' | |
743 | @cindex @samp{\'} in regexp | |
744 | matches the empty string, but only at the end of | |
745 | the buffer or string being matched against. | |
746 | ||
747 | @item \= | |
748 | @cindex @samp{\=} in regexp | |
749 | matches the empty string, but only at point. | |
750 | (This construct is not defined when matching against a string.) | |
751 | ||
752 | @item \b | |
753 | @cindex @samp{\b} in regexp | |
754 | matches the empty string, but only at the beginning or | |
755 | end of a word. Thus, @samp{\bfoo\b} matches any occurrence of | |
756 | @samp{foo} as a separate word. @samp{\bballs?\b} matches | |
757 | @samp{ball} or @samp{balls} as a separate word.@refill | |
758 | ||
bcb6b6b8 | 759 | @samp{\b} matches at the beginning or end of the buffer (or string) |
1cd71ce0 RS |
760 | regardless of what text appears next to it. |
761 | ||
7015aca4 RS |
762 | @item \B |
763 | @cindex @samp{\B} in regexp | |
764 | matches the empty string, but @emph{not} at the beginning or | |
bcb6b6b8 | 765 | end of a word, nor at the beginning or end of the buffer (or string). |
7015aca4 RS |
766 | |
767 | @item \< | |
768 | @cindex @samp{\<} in regexp | |
769 | matches the empty string, but only at the beginning of a word. | |
bcb6b6b8 | 770 | @samp{\<} matches at the beginning of the buffer (or string) only if a |
1cd71ce0 | 771 | word-constituent character follows. |
7015aca4 RS |
772 | |
773 | @item \> | |
774 | @cindex @samp{\>} in regexp | |
1cd71ce0 | 775 | matches the empty string, but only at the end of a word. @samp{\>} |
bcb6b6b8 LT |
776 | matches at the end of the buffer (or string) only if the contents end |
777 | with a word-constituent character. | |
9a7e97c6 LT |
778 | |
779 | @item \_< | |
780 | @cindex @samp{\_<} in regexp | |
781 | matches the empty string, but only at the beginning of a symbol. A | |
782 | symbol is a sequence of one or more word or symbol constituent | |
783 | characters. @samp{\_<} matches at the beginning of the buffer (or | |
784 | string) only if a symbol-constituent character follows. | |
785 | ||
786 | @item \_> | |
787 | @cindex @samp{\_>} in regexp | |
788 | matches the empty string, but only at the end of a symbol. @samp{\_>} | |
789 | matches at the end of the buffer (or string) only if the contents end | |
790 | with a symbol-constituent character. | |
7015aca4 RS |
791 | @end table |
792 | ||
793 | @kindex invalid-regexp | |
794 | Not every string is a valid regular expression. For example, a string | |
179a6f21 LT |
795 | that ends inside a character alternative without terminating @samp{]} |
796 | is invalid, and so is a string that ends with a single @samp{\}. If | |
7015aca4 RS |
797 | an invalid regular expression is passed to any of the search functions, |
798 | an @code{invalid-regexp} error is signaled. | |
799 | ||
7015aca4 RS |
800 | @node Regexp Example |
801 | @comment node-name, next, previous, up | |
802 | @subsection Complex Regexp Example | |
803 | ||
bcb6b6b8 LT |
804 | Here is a complicated regexp which was formerly used by Emacs to |
805 | recognize the end of a sentence together with any whitespace that | |
45fa30b2 LT |
806 | follows. (Nowadays Emacs uses a similar but more complex default |
807 | regexp constructed by the function @code{sentence-end}. | |
808 | @xref{Standard Regexps}.) | |
7015aca4 RS |
809 | |
810 | First, we show the regexp as a string in Lisp syntax to distinguish | |
811 | spaces from tab characters. The string constant begins and ends with a | |
812 | double-quote. @samp{\"} stands for a double-quote as part of the | |
813 | string, @samp{\\} for a backslash as part of the string, @samp{\t} for a | |
814 | tab and @samp{\n} for a newline. | |
815 | ||
816 | @example | |
bcb6b6b8 | 817 | "[.?!][]\"')@}]*\\($\\| $\\|\t\\|@ @ \\)[ \t\n]*" |
7015aca4 RS |
818 | @end example |
819 | ||
969fe9b5 | 820 | @noindent |
bcb6b6b8 | 821 | In contrast, if you evaluate this string, you will see the following: |
7015aca4 RS |
822 | |
823 | @example | |
824 | @group | |
bcb6b6b8 LT |
825 | "[.?!][]\"')@}]*\\($\\| $\\|\t\\|@ @ \\)[ \t\n]*" |
826 | @result{} "[.?!][]\"')@}]*\\($\\| $\\| \\|@ @ \\)[ | |
7015aca4 RS |
827 | ]*" |
828 | @end group | |
829 | @end example | |
830 | ||
831 | @noindent | |
832 | In this output, tab and newline appear as themselves. | |
833 | ||
834 | This regular expression contains four parts in succession and can be | |
835 | deciphered as follows: | |
836 | ||
837 | @table @code | |
838 | @item [.?!] | |
969fe9b5 RS |
839 | The first part of the pattern is a character alternative that matches |
840 | any one of three characters: period, question mark, and exclamation | |
bcb6b6b8 | 841 | mark. The match must begin with one of these three characters. (This |
45fa30b2 LT |
842 | is one point where the new default regexp used by Emacs differs from |
843 | the old. The new value also allows some non-@acronym{ASCII} | |
844 | characters that end a sentence without any following whitespace.) | |
7015aca4 RS |
845 | |
846 | @item []\"')@}]* | |
847 | The second part of the pattern matches any closing braces and quotation | |
848 | marks, zero or more of them, that may follow the period, question mark | |
849 | or exclamation mark. The @code{\"} is Lisp syntax for a double-quote in | |
850 | a string. The @samp{*} at the end indicates that the immediately | |
969fe9b5 | 851 | preceding regular expression (a character alternative, in this case) may be |
7015aca4 RS |
852 | repeated zero or more times. |
853 | ||
7fd1911a | 854 | @item \\($\\|@ $\\|\t\\|@ @ \\) |
7015aca4 | 855 | The third part of the pattern matches the whitespace that follows the |
f9f59935 RS |
856 | end of a sentence: the end of a line (optionally with a space), or a |
857 | tab, or two spaces. The double backslashes mark the parentheses and | |
858 | vertical bars as regular expression syntax; the parentheses delimit a | |
859 | group and the vertical bars separate alternatives. The dollar sign is | |
860 | used to match the end of a line. | |
7015aca4 RS |
861 | |
862 | @item [ \t\n]* | |
863 | Finally, the last part of the pattern matches any additional whitespace | |
864 | beyond the minimum needed to end a sentence. | |
865 | @end table | |
866 | ||
8241495d RS |
867 | @node Regexp Functions |
868 | @subsection Regular Expression Functions | |
869 | ||
870 | These functions operate on regular expressions. | |
871 | ||
872 | @defun regexp-quote string | |
873 | This function returns a regular expression whose only exact match is | |
874 | @var{string}. Using this regular expression in @code{looking-at} will | |
875 | succeed only if the next characters in the buffer are @var{string}; | |
876 | using it in a search function will succeed if the text being searched | |
877 | contains @var{string}. | |
878 | ||
879 | This allows you to request an exact string match or search when calling | |
880 | a function that wants a regular expression. | |
881 | ||
882 | @example | |
883 | @group | |
884 | (regexp-quote "^The cat$") | |
885 | @result{} "\\^The cat\\$" | |
886 | @end group | |
887 | @end example | |
888 | ||
889 | One use of @code{regexp-quote} is to combine an exact string match with | |
890 | context described as a regular expression. For example, this searches | |
891 | for the string that is the value of @var{string}, surrounded by | |
892 | whitespace: | |
893 | ||
894 | @example | |
895 | @group | |
896 | (re-search-forward | |
897 | (concat "\\s-" (regexp-quote string) "\\s-")) | |
898 | @end group | |
899 | @end example | |
900 | @end defun | |
901 | ||
902 | @defun regexp-opt strings &optional paren | |
8241495d | 903 | This function returns an efficient regular expression that will match |
bcb6b6b8 LT |
904 | any of the strings in the list @var{strings}. This is useful when you |
905 | need to make matching or searching as fast as possible---for example, | |
906 | for Font Lock mode. | |
8241495d RS |
907 | |
908 | If the optional argument @var{paren} is non-@code{nil}, then the | |
909 | returned regular expression is always enclosed by at least one | |
bcb6b6b8 LT |
910 | parentheses-grouping construct. If @var{paren} is @code{words}, then |
911 | that construct is additionally surrounded by @samp{\<} and @samp{\>}. | |
8241495d RS |
912 | |
913 | This simplified definition of @code{regexp-opt} produces a | |
914 | regular expression which is equivalent to the actual value | |
915 | (but not as efficient): | |
916 | ||
917 | @example | |
918 | (defun regexp-opt (strings paren) | |
919 | (let ((open-paren (if paren "\\(" "")) | |
920 | (close-paren (if paren "\\)" ""))) | |
921 | (concat open-paren | |
922 | (mapconcat 'regexp-quote strings "\\|") | |
923 | close-paren))) | |
924 | @end example | |
925 | @end defun | |
926 | ||
927 | @defun regexp-opt-depth regexp | |
8241495d | 928 | This function returns the total number of grouping constructs |
bcb6b6b8 LT |
929 | (parenthesized expressions) in @var{regexp}. (This does not include |
930 | shy groups.) | |
8241495d RS |
931 | @end defun |
932 | ||
7015aca4 RS |
933 | @node Regexp Search |
934 | @section Regular Expression Searching | |
935 | @cindex regular expression searching | |
936 | @cindex regexp searching | |
937 | @cindex searching for regexp | |
938 | ||
969fe9b5 RS |
939 | In GNU Emacs, you can search for the next match for a regular |
940 | expression either incrementally or not. For incremental search | |
941 | commands, see @ref{Regexp Search, , Regular Expression Search, emacs, | |
942 | The GNU Emacs Manual}. Here we describe only the search functions | |
943 | useful in programs. The principal one is @code{re-search-forward}. | |
7015aca4 | 944 | |
f9f59935 RS |
945 | These search functions convert the regular expression to multibyte if |
946 | the buffer is multibyte; they convert the regular expression to unibyte | |
947 | if the buffer is unibyte. @xref{Text Representations}. | |
948 | ||
7015aca4 RS |
949 | @deffn Command re-search-forward regexp &optional limit noerror repeat |
950 | This function searches forward in the current buffer for a string of | |
951 | text that is matched by the regular expression @var{regexp}. The | |
952 | function skips over any amount of text that is not matched by | |
953 | @var{regexp}, and leaves point at the end of the first match found. | |
954 | It returns the new value of point. | |
955 | ||
5bb8ca2a RS |
956 | If @var{limit} is non-@code{nil}, it must be a position in the current |
957 | buffer. It specifies the upper bound to the search. No match | |
958 | extending after that position is accepted. | |
7015aca4 | 959 | |
5bb8ca2a RS |
960 | If @var{repeat} is supplied, it must be a positive number; the search |
961 | is repeated that many times; each repetition starts at the end of the | |
4362c714 RS |
962 | previous match. If all these successive searches succeed, the search |
963 | succeeds, moving point and returning its new value. Otherwise the | |
964 | search fails. What @code{re-search-forward} does when the search | |
965 | fails depends on the value of @var{noerror}: | |
f9f59935 | 966 | |
4362c714 RS |
967 | @table @asis |
968 | @item @code{nil} | |
969 | Signal a @code{search-failed} error. | |
970 | @item @code{t} | |
971 | Do nothing and return @code{nil}. | |
972 | @item anything else | |
973 | Move point to @var{limit} (or the end of the accessible portion of the | |
974 | buffer) and return @code{nil}. | |
975 | @end table | |
7015aca4 | 976 | |
7015aca4 RS |
977 | In the following example, point is initially before the @samp{T}. |
978 | Evaluating the search call moves point to the end of that line (between | |
979 | the @samp{t} of @samp{hat} and the newline). | |
980 | ||
981 | @example | |
982 | @group | |
983 | ---------- Buffer: foo ---------- | |
984 | I read "@point{}The cat in the hat | |
985 | comes back" twice. | |
986 | ---------- Buffer: foo ---------- | |
987 | @end group | |
988 | ||
989 | @group | |
990 | (re-search-forward "[a-z]+" nil t 5) | |
991 | @result{} 27 | |
992 | ||
993 | ---------- Buffer: foo ---------- | |
994 | I read "The cat in the hat@point{} | |
995 | comes back" twice. | |
996 | ---------- Buffer: foo ---------- | |
997 | @end group | |
998 | @end example | |
999 | @end deffn | |
1000 | ||
1001 | @deffn Command re-search-backward regexp &optional limit noerror repeat | |
1002 | This function searches backward in the current buffer for a string of | |
1003 | text that is matched by the regular expression @var{regexp}, leaving | |
1004 | point at the beginning of the first text found. | |
1005 | ||
7fd1911a RS |
1006 | This function is analogous to @code{re-search-forward}, but they are not |
1007 | simple mirror images. @code{re-search-forward} finds the match whose | |
1008 | beginning is as close as possible to the starting point. If | |
1009 | @code{re-search-backward} were a perfect mirror image, it would find the | |
1010 | match whose end is as close as possible. However, in fact it finds the | |
bcb6b6b8 LT |
1011 | match whose beginning is as close as possible (and yet ends before the |
1012 | starting point). The reason for this is that matching a regular | |
1013 | expression at a given spot always works from beginning to end, and | |
1014 | starts at a specified beginning position. | |
7015aca4 RS |
1015 | |
1016 | A true mirror-image of @code{re-search-forward} would require a special | |
969fe9b5 RS |
1017 | feature for matching regular expressions from end to beginning. It's |
1018 | not worth the trouble of implementing that. | |
7015aca4 RS |
1019 | @end deffn |
1020 | ||
1021 | @defun string-match regexp string &optional start | |
1022 | This function returns the index of the start of the first match for | |
1023 | the regular expression @var{regexp} in @var{string}, or @code{nil} if | |
1024 | there is no match. If @var{start} is non-@code{nil}, the search starts | |
1025 | at that index in @var{string}. | |
1026 | ||
1027 | For example, | |
1028 | ||
1029 | @example | |
1030 | @group | |
1031 | (string-match | |
1032 | "quick" "The quick brown fox jumped quickly.") | |
1033 | @result{} 4 | |
1034 | @end group | |
1035 | @group | |
1036 | (string-match | |
1037 | "quick" "The quick brown fox jumped quickly." 8) | |
1038 | @result{} 27 | |
1039 | @end group | |
1040 | @end example | |
1041 | ||
1042 | @noindent | |
1043 | The index of the first character of the | |
1044 | string is 0, the index of the second character is 1, and so on. | |
1045 | ||
1046 | After this function returns, the index of the first character beyond | |
1047 | the match is available as @code{(match-end 0)}. @xref{Match Data}. | |
1048 | ||
1049 | @example | |
1050 | @group | |
1051 | (string-match | |
1052 | "quick" "The quick brown fox jumped quickly." 8) | |
1053 | @result{} 27 | |
1054 | @end group | |
1055 | ||
1056 | @group | |
1057 | (match-end 0) | |
1058 | @result{} 32 | |
1059 | @end group | |
1060 | @end example | |
1061 | @end defun | |
1062 | ||
1063 | @defun looking-at regexp | |
1064 | This function determines whether the text in the current buffer directly | |
1065 | following point matches the regular expression @var{regexp}. ``Directly | |
1066 | following'' means precisely that: the search is ``anchored'' and it can | |
1067 | succeed only starting with the first character following point. The | |
1068 | result is @code{t} if so, @code{nil} otherwise. | |
1069 | ||
1070 | This function does not move point, but it updates the match data, which | |
1071 | you can access using @code{match-beginning} and @code{match-end}. | |
1072 | @xref{Match Data}. | |
1073 | ||
1074 | In this example, point is located directly before the @samp{T}. If it | |
1075 | were anywhere else, the result would be @code{nil}. | |
1076 | ||
1077 | @example | |
1078 | @group | |
1079 | ---------- Buffer: foo ---------- | |
1080 | I read "@point{}The cat in the hat | |
1081 | comes back" twice. | |
1082 | ---------- Buffer: foo ---------- | |
1083 | ||
1084 | (looking-at "The cat in the hat$") | |
1085 | @result{} t | |
1086 | @end group | |
1087 | @end example | |
1088 | @end defun | |
1089 | ||
4d4d2d07 RS |
1090 | @defun looking-back regexp &optional limit |
1091 | This function returns @code{t} if @var{regexp} matches text before | |
1092 | point, ending at point, and @code{nil} otherwise. | |
1093 | ||
1094 | Because regular expression matching works only going forward, this is | |
1095 | implemented by searching backwards from point for a match that ends at | |
1096 | point. That can be quite slow if it has to search a long distance. | |
1097 | You can bound the time required by specifying @var{limit}, which says | |
1098 | not to search before @var{limit}. In this case, the match that is | |
1099 | found must begin at or after @var{limit}. | |
1100 | ||
1101 | @example | |
1102 | @group | |
1103 | ---------- Buffer: foo ---------- | |
1104 | I read "@point{}The cat in the hat | |
1105 | comes back" twice. | |
1106 | ---------- Buffer: foo ---------- | |
1107 | ||
1108 | (looking-back "read \"" 3) | |
1109 | @result{} t | |
1110 | (looking-back "read \"" 4) | |
1111 | @result{} nil | |
1112 | @end group | |
1113 | @end example | |
1114 | @end defun | |
1115 | ||
fe83e8de | 1116 | @defvar search-spaces-regexp |
65b65d26 RS |
1117 | If this variable is non-@code{nil}, it should be a regular expression |
1118 | that says how to search for whitespace. In that case, any group of | |
5bb8ca2a RS |
1119 | spaces in a regular expression being searched for stands for use of |
1120 | this regular expression. However, spaces inside of constructs such as | |
1121 | @samp{[@dots{}]} and @samp{*}, @samp{+}, @samp{?} are not affected by | |
1122 | @code{search-spaces-regexp}. | |
1123 | ||
1124 | Since this variable affects all regular expression search and match | |
1125 | constructs, you should bind it temporarily for as small as possible | |
1126 | a part of the code. | |
65b65d26 RS |
1127 | @end defvar |
1128 | ||
22697dac KH |
1129 | @node POSIX Regexps |
1130 | @section POSIX Regular Expression Searching | |
1131 | ||
1132 | The usual regular expression functions do backtracking when necessary | |
1133 | to handle the @samp{\|} and repetition constructs, but they continue | |
1134 | this only until they find @emph{some} match. Then they succeed and | |
1135 | report the first match found. | |
1136 | ||
1137 | This section describes alternative search functions which perform the | |
1138 | full backtracking specified by the POSIX standard for regular expression | |
1139 | matching. They continue backtracking until they have tried all | |
1140 | possibilities and found all matches, so they can report the longest | |
1141 | match, as required by POSIX. This is much slower, so use these | |
1142 | functions only when you really need the longest match. | |
1143 | ||
01913af2 RS |
1144 | The POSIX search and match functions do not properly support the |
1145 | non-greedy repetition operators. This is because POSIX backtracking | |
1146 | conflicts with the semantics of non-greedy repetition. | |
1147 | ||
22697dac KH |
1148 | @defun posix-search-forward regexp &optional limit noerror repeat |
1149 | This is like @code{re-search-forward} except that it performs the full | |
1150 | backtracking specified by the POSIX standard for regular expression | |
1151 | matching. | |
1152 | @end defun | |
1153 | ||
1154 | @defun posix-search-backward regexp &optional limit noerror repeat | |
1155 | This is like @code{re-search-backward} except that it performs the full | |
1156 | backtracking specified by the POSIX standard for regular expression | |
1157 | matching. | |
1158 | @end defun | |
1159 | ||
1160 | @defun posix-looking-at regexp | |
1161 | This is like @code{looking-at} except that it performs the full | |
1162 | backtracking specified by the POSIX standard for regular expression | |
1163 | matching. | |
1164 | @end defun | |
1165 | ||
1166 | @defun posix-string-match regexp string &optional start | |
1167 | This is like @code{string-match} except that it performs the full | |
1168 | backtracking specified by the POSIX standard for regular expression | |
1169 | matching. | |
1170 | @end defun | |
1171 | ||
7015aca4 RS |
1172 | @node Match Data |
1173 | @section The Match Data | |
1174 | @cindex match data | |
1175 | ||
3f63de1e | 1176 | Emacs keeps track of the start and end positions of the segments of |
99543e8b RS |
1177 | text found during a search; this is called the @dfn{match data}. |
1178 | Thanks to the match data, you can search for a complex pattern, such | |
1179 | as a date in a mail message, and then extract parts of the match under | |
1180 | control of the pattern. | |
7015aca4 RS |
1181 | |
1182 | Because the match data normally describe the most recent search only, | |
1183 | you must be careful not to do another search inadvertently between the | |
1184 | search you wish to refer back to and the use of the match data. If you | |
1185 | can't avoid another intervening search, you must save and restore the | |
1186 | match data around it, to prevent it from being overwritten. | |
1187 | ||
1188 | @menu | |
969fe9b5 | 1189 | * Replacing Match:: Replacing a substring that was matched. |
7015aca4 RS |
1190 | * Simple Match Data:: Accessing single items of match data, |
1191 | such as where a particular subexpression started. | |
7015aca4 RS |
1192 | * Entire Match Data:: Accessing the entire match data at once, as a list. |
1193 | * Saving Match Data:: Saving and restoring the match data. | |
1194 | @end menu | |
1195 | ||
969fe9b5 | 1196 | @node Replacing Match |
8241495d | 1197 | @subsection Replacing the Text that Matched |
0fb7e7f2 | 1198 | @cindex replace matched text |
969fe9b5 | 1199 | |
99543e8b RS |
1200 | This function replaces all or part of the text matched by the last |
1201 | search. It works by means of the match data. | |
969fe9b5 RS |
1202 | |
1203 | @cindex case in replacements | |
1204 | @defun replace-match replacement &optional fixedcase literal string subexp | |
1205 | This function replaces the text in the buffer (or in @var{string}) that | |
1206 | was matched by the last search. It replaces that text with | |
1207 | @var{replacement}. | |
1208 | ||
1209 | If you did the last search in a buffer, you should specify @code{nil} | |
bcb6b6b8 LT |
1210 | for @var{string} and make sure that the current buffer when you call |
1211 | @code{replace-match} is the one in which you did the searching or | |
1212 | matching. Then @code{replace-match} does the replacement by editing | |
1213 | the buffer; it leaves point at the end of the replacement text, and | |
1214 | returns @code{t}. | |
969fe9b5 RS |
1215 | |
1216 | If you did the search in a string, pass the same string as @var{string}. | |
1217 | Then @code{replace-match} does the replacement by constructing and | |
1218 | returning a new string. | |
1219 | ||
2037b263 RS |
1220 | If @var{fixedcase} is non-@code{nil}, then @code{replace-match} uses |
1221 | the replacement text without case conversion; otherwise, it converts | |
1222 | the replacement text depending upon the capitalization of the text to | |
1223 | be replaced. If the original text is all upper case, this converts | |
1224 | the replacement text to upper case. If all words of the original text | |
1225 | are capitalized, this capitalizes all the words of the replacement | |
1226 | text. If all the words are one-letter and they are all upper case, | |
1227 | they are treated as capitalized words rather than all-upper-case | |
1228 | words. | |
969fe9b5 | 1229 | |
969fe9b5 RS |
1230 | If @var{literal} is non-@code{nil}, then @var{replacement} is inserted |
1231 | exactly as it is, the only alterations being case changes as needed. | |
1232 | If it is @code{nil} (the default), then the character @samp{\} is treated | |
1233 | specially. If a @samp{\} appears in @var{replacement}, then it must be | |
1234 | part of one of the following sequences: | |
1235 | ||
1236 | @table @asis | |
1237 | @item @samp{\&} | |
1238 | @cindex @samp{&} in replacement | |
1239 | @samp{\&} stands for the entire text being replaced. | |
1240 | ||
1241 | @item @samp{\@var{n}} | |
1242 | @cindex @samp{\@var{n}} in replacement | |
1243 | @samp{\@var{n}}, where @var{n} is a digit, stands for the text that | |
1244 | matched the @var{n}th subexpression in the original regexp. | |
1245 | Subexpressions are those expressions grouped inside @samp{\(@dots{}\)}. | |
bcb6b6b8 | 1246 | If the @var{n}th subexpression never matched, an empty string is substituted. |
969fe9b5 RS |
1247 | |
1248 | @item @samp{\\} | |
1249 | @cindex @samp{\} in replacement | |
1250 | @samp{\\} stands for a single @samp{\} in the replacement text. | |
1251 | @end table | |
1252 | ||
2037b263 RS |
1253 | These substitutions occur after case conversion, if any, |
1254 | so the strings they substitute are never case-converted. | |
1255 | ||
969fe9b5 RS |
1256 | If @var{subexp} is non-@code{nil}, that says to replace just |
1257 | subexpression number @var{subexp} of the regexp that was matched, not | |
1258 | the entire match. For example, after matching @samp{foo \(ba*r\)}, | |
1259 | calling @code{replace-match} with 1 as @var{subexp} means to replace | |
1260 | just the text that matched @samp{\(ba*r\)}. | |
1261 | @end defun | |
1262 | ||
7015aca4 RS |
1263 | @node Simple Match Data |
1264 | @subsection Simple Match Data Access | |
1265 | ||
22697dac | 1266 | This section explains how to use the match data to find out what was |
87bf725e | 1267 | matched by the last search or match operation, if it succeeded. |
22697dac KH |
1268 | |
1269 | You can ask about the entire matching text, or about a particular | |
1270 | parenthetical subexpression of a regular expression. The @var{count} | |
1271 | argument in the functions below specifies which. If @var{count} is | |
1272 | zero, you are asking about the entire match. If @var{count} is | |
1273 | positive, it specifies which subexpression you want. | |
1274 | ||
1275 | Recall that the subexpressions of a regular expression are those | |
1276 | expressions grouped with escaped parentheses, @samp{\(@dots{}\)}. The | |
1277 | @var{count}th subexpression is found by counting occurrences of | |
1278 | @samp{\(} from the beginning of the whole regular expression. The first | |
1279 | subexpression is numbered 1, the second 2, and so on. Only regular | |
1280 | expressions can have subexpressions---after a simple string search, the | |
1281 | only information available is about the entire match. | |
1282 | ||
5345f90d EZ |
1283 | Every successful search sets the match data. Therefore, you should |
1284 | query the match data immediately after searching, before calling any | |
1285 | other function that might perform another search. Alternatively, you | |
1286 | may save and restore the match data (@pxref{Saving Match Data}) around | |
1287 | the call to functions that could perform another search. | |
1288 | ||
a9f0a989 RS |
1289 | A search which fails may or may not alter the match data. In the |
1290 | past, a failing search did not do this, but we may change it in the | |
87bf725e RS |
1291 | future. So don't try to rely on the value of the match data after |
1292 | a failing search. | |
a9f0a989 | 1293 | |
22697dac KH |
1294 | @defun match-string count &optional in-string |
1295 | This function returns, as a string, the text matched in the last search | |
1296 | or match operation. It returns the entire text if @var{count} is zero, | |
1297 | or just the portion corresponding to the @var{count}th parenthetical | |
a5d0a32e | 1298 | subexpression, if @var{count} is positive. |
22697dac KH |
1299 | |
1300 | If the last such operation was done against a string with | |
1301 | @code{string-match}, then you should pass the same string as the | |
969fe9b5 | 1302 | argument @var{in-string}. After a buffer search or match, |
22697dac KH |
1303 | you should omit @var{in-string} or pass @code{nil} for it; but you |
1304 | should make sure that the current buffer when you call | |
1305 | @code{match-string} is the one in which you did the searching or | |
1306 | matching. | |
a5d0a32e RS |
1307 | |
1308 | The value is @code{nil} if @var{count} is out of range, or for a | |
1309 | subexpression inside a @samp{\|} alternative that wasn't used or a | |
1310 | repetition that repeated zero times. | |
22697dac | 1311 | @end defun |
7015aca4 | 1312 | |
79ddc9c9 | 1313 | @defun match-string-no-properties count &optional in-string |
f9f59935 RS |
1314 | This function is like @code{match-string} except that the result |
1315 | has no text properties. | |
1316 | @end defun | |
1317 | ||
7015aca4 RS |
1318 | @defun match-beginning count |
1319 | This function returns the position of the start of text matched by the | |
1320 | last regular expression searched for, or a subexpression of it. | |
1321 | ||
7fd1911a | 1322 | If @var{count} is zero, then the value is the position of the start of |
eaac2be1 | 1323 | the entire match. Otherwise, @var{count} specifies a subexpression in |
969fe9b5 | 1324 | the regular expression, and the value of the function is the starting |
22697dac KH |
1325 | position of the match for that subexpression. |
1326 | ||
1327 | The value is @code{nil} for a subexpression inside a @samp{\|} | |
a5d0a32e | 1328 | alternative that wasn't used or a repetition that repeated zero times. |
7015aca4 RS |
1329 | @end defun |
1330 | ||
1331 | @defun match-end count | |
22697dac KH |
1332 | This function is like @code{match-beginning} except that it returns the |
1333 | position of the end of the match, rather than the position of the | |
1334 | beginning. | |
7015aca4 RS |
1335 | @end defun |
1336 | ||
1337 | Here is an example of using the match data, with a comment showing the | |
1338 | positions within the text: | |
1339 | ||
1340 | @example | |
1341 | @group | |
1342 | (string-match "\\(qu\\)\\(ick\\)" | |
1343 | "The quick fox jumped quickly.") | |
177c0ea7 | 1344 | ;0123456789 |
7015aca4 RS |
1345 | @result{} 4 |
1346 | @end group | |
1347 | ||
22697dac KH |
1348 | @group |
1349 | (match-string 0 "The quick fox jumped quickly.") | |
1350 | @result{} "quick" | |
1351 | (match-string 1 "The quick fox jumped quickly.") | |
1352 | @result{} "qu" | |
1353 | (match-string 2 "The quick fox jumped quickly.") | |
1354 | @result{} "ick" | |
1355 | @end group | |
1356 | ||
7015aca4 RS |
1357 | @group |
1358 | (match-beginning 1) ; @r{The beginning of the match} | |
1359 | @result{} 4 ; @r{with @samp{qu} is at index 4.} | |
1360 | @end group | |
1361 | ||
1362 | @group | |
1363 | (match-beginning 2) ; @r{The beginning of the match} | |
1364 | @result{} 6 ; @r{with @samp{ick} is at index 6.} | |
1365 | @end group | |
1366 | ||
1367 | @group | |
1368 | (match-end 1) ; @r{The end of the match} | |
1369 | @result{} 6 ; @r{with @samp{qu} is at index 6.} | |
1370 | ||
1371 | (match-end 2) ; @r{The end of the match} | |
1372 | @result{} 9 ; @r{with @samp{ick} is at index 9.} | |
1373 | @end group | |
1374 | @end example | |
1375 | ||
1376 | Here is another example. Point is initially located at the beginning | |
1377 | of the line. Searching moves point to between the space and the word | |
1378 | @samp{in}. The beginning of the entire match is at the 9th character of | |
1379 | the buffer (@samp{T}), and the beginning of the match for the first | |
1380 | subexpression is at the 13th character (@samp{c}). | |
1381 | ||
1382 | @example | |
1383 | @group | |
1384 | (list | |
1385 | (re-search-forward "The \\(cat \\)") | |
1386 | (match-beginning 0) | |
1387 | (match-beginning 1)) | |
7fd1911a | 1388 | @result{} (9 9 13) |
7015aca4 RS |
1389 | @end group |
1390 | ||
1391 | @group | |
1392 | ---------- Buffer: foo ---------- | |
1393 | I read "The cat @point{}in the hat comes back" twice. | |
1394 | ^ ^ | |
1395 | 9 13 | |
1396 | ---------- Buffer: foo ---------- | |
1397 | @end group | |
1398 | @end example | |
1399 | ||
1400 | @noindent | |
1401 | (In this case, the index returned is a buffer position; the first | |
1402 | character of the buffer counts as 1.) | |
1403 | ||
7015aca4 RS |
1404 | @node Entire Match Data |
1405 | @subsection Accessing the Entire Match Data | |
1406 | ||
1407 | The functions @code{match-data} and @code{set-match-data} read or | |
1408 | write the entire match data, all at once. | |
1409 | ||
4e370af2 | 1410 | @defun match-data &optional integers reuse reseat |
8135a25a RS |
1411 | This function returns a list of positions (markers or integers) that |
1412 | record all the information on what text the last search matched. | |
1413 | Element zero is the position of the beginning of the match for the | |
1414 | whole expression; element one is the position of the end of the match | |
1415 | for the expression. The next two elements are the positions of the | |
1416 | beginning and end of the match for the first subexpression, and so on. | |
1417 | In general, element | |
37680279 | 1418 | @ifnottex |
7015aca4 | 1419 | number 2@var{n} |
37680279 | 1420 | @end ifnottex |
7015aca4 RS |
1421 | @tex |
1422 | number {\mathsurround=0pt $2n$} | |
1423 | @end tex | |
1424 | corresponds to @code{(match-beginning @var{n})}; and | |
1425 | element | |
37680279 | 1426 | @ifnottex |
7015aca4 | 1427 | number 2@var{n} + 1 |
37680279 | 1428 | @end ifnottex |
7015aca4 RS |
1429 | @tex |
1430 | number {\mathsurround=0pt $2n+1$} | |
1431 | @end tex | |
1432 | corresponds to @code{(match-end @var{n})}. | |
1433 | ||
8135a25a RS |
1434 | Normally all the elements are markers or @code{nil}, but if |
1435 | @var{integers} is non-@code{nil}, that means to use integers instead | |
1436 | of markers. (In that case, the buffer itself is appended as an | |
1437 | additional element at the end of the list, to facilitate complete | |
1438 | restoration of the match data.) If the last match was done on a | |
1439 | string with @code{string-match}, then integers are always used, | |
1440 | since markers can't point into a string. | |
bcb6b6b8 LT |
1441 | |
1442 | If @var{reuse} is non-@code{nil}, it should be a list. In that case, | |
1443 | @code{match-data} stores the match data in @var{reuse}. That is, | |
1444 | @var{reuse} is destructively modified. @var{reuse} does not need to | |
1445 | have the right length. If it is not long enough to contain the match | |
1446 | data, it is extended. If it is too long, the length of @var{reuse} | |
1447 | stays the same, but the elements that were not used are set to | |
8135a25a RS |
1448 | @code{nil}. The purpose of this feature is to reduce the need for |
1449 | garbage collection. | |
7015aca4 | 1450 | |
4e370af2 | 1451 | If @var{reseat} is non-@code{nil}, all markers on the @var{reuse} list |
68be435e | 1452 | are reseated to point to nowhere. |
4e370af2 | 1453 | |
7015aca4 RS |
1454 | As always, there must be no possibility of intervening searches between |
1455 | the call to a search function and the call to @code{match-data} that is | |
1456 | intended to access the match data for that search. | |
1457 | ||
1458 | @example | |
1459 | @group | |
1460 | (match-data) | |
1461 | @result{} (#<marker at 9 in foo> | |
1462 | #<marker at 17 in foo> | |
1463 | #<marker at 13 in foo> | |
1464 | #<marker at 17 in foo>) | |
1465 | @end group | |
1466 | @end example | |
1467 | @end defun | |
1468 | ||
4e370af2 | 1469 | @defun set-match-data match-list &optional reseat |
7015aca4 RS |
1470 | This function sets the match data from the elements of @var{match-list}, |
1471 | which should be a list that was the value of a previous call to | |
3ab8acb9 RS |
1472 | @code{match-data}. (More precisely, anything that has the same format |
1473 | will work.) | |
7015aca4 RS |
1474 | |
1475 | If @var{match-list} refers to a buffer that doesn't exist, you don't get | |
1476 | an error; that sets the match data in a meaningless but harmless way. | |
1477 | ||
4e370af2 | 1478 | If @var{reseat} is non-@code{nil}, all markers on the @var{match-list} list |
68be435e | 1479 | are reseated to point to nowhere. |
4e370af2 | 1480 | |
7015aca4 | 1481 | @findex store-match-data |
969fe9b5 | 1482 | @code{store-match-data} is a semi-obsolete alias for @code{set-match-data}. |
7015aca4 RS |
1483 | @end defun |
1484 | ||
1485 | @node Saving Match Data | |
1486 | @subsection Saving and Restoring the Match Data | |
1487 | ||
d1280259 RS |
1488 | When you call a function that may do a search, you may need to save |
1489 | and restore the match data around that call, if you want to preserve the | |
1490 | match data from an earlier search for later use. Here is an example | |
1491 | that shows the problem that arises if you fail to save the match data: | |
7015aca4 RS |
1492 | |
1493 | @example | |
1494 | @group | |
1495 | (re-search-forward "The \\(cat \\)") | |
1496 | @result{} 48 | |
1497 | (foo) ; @r{Perhaps @code{foo} does} | |
1498 | ; @r{more searching.} | |
1499 | (match-end 0) | |
1500 | @result{} 61 ; @r{Unexpected result---not 48!} | |
1501 | @end group | |
1502 | @end example | |
1503 | ||
d1280259 | 1504 | You can save and restore the match data with @code{save-match-data}: |
7015aca4 | 1505 | |
bfe721d1 | 1506 | @defmac save-match-data body@dots{} |
1911e6e5 | 1507 | This macro executes @var{body}, saving and restoring the match |
bcb6b6b8 LT |
1508 | data around it. The return value is the value of the last form in |
1509 | @var{body}. | |
bfe721d1 | 1510 | @end defmac |
7015aca4 | 1511 | |
969fe9b5 RS |
1512 | You could use @code{set-match-data} together with @code{match-data} to |
1513 | imitate the effect of the special form @code{save-match-data}. Here is | |
1514 | how: | |
7015aca4 RS |
1515 | |
1516 | @example | |
1517 | @group | |
1518 | (let ((data (match-data))) | |
1519 | (unwind-protect | |
f9f59935 | 1520 | @dots{} ; @r{Ok to change the original match data.} |
7015aca4 RS |
1521 | (set-match-data data))) |
1522 | @end group | |
1523 | @end example | |
1524 | ||
d1280259 RS |
1525 | Emacs automatically saves and restores the match data when it runs |
1526 | process filter functions (@pxref{Filter Functions}) and process | |
1527 | sentinels (@pxref{Sentinels}). | |
1528 | ||
7015aca4 RS |
1529 | @ignore |
1530 | Here is a function which restores the match data provided the buffer | |
1531 | associated with it still exists. | |
1532 | ||
1533 | @smallexample | |
1534 | @group | |
1535 | (defun restore-match-data (data) | |
1536 | @c It is incorrect to split the first line of a doc string. | |
1537 | @c If there's a problem here, it should be solved in some other way. | |
1538 | "Restore the match data DATA unless the buffer is missing." | |
1539 | (catch 'foo | |
1540 | (let ((d data)) | |
1541 | @end group | |
1542 | (while d | |
1543 | (and (car d) | |
1544 | (null (marker-buffer (car d))) | |
1545 | @group | |
1546 | ;; @file{match-data} @r{buffer is deleted.} | |
1547 | (throw 'foo nil)) | |
1548 | (setq d (cdr d))) | |
1549 | (set-match-data data)))) | |
1550 | @end group | |
1551 | @end smallexample | |
1552 | @end ignore | |
1553 | ||
99543e8b RS |
1554 | @node Search and Replace |
1555 | @section Search and Replace | |
0fb7e7f2 RS |
1556 | @cindex replacement after search |
1557 | @cindex searching and replacing | |
7015aca4 | 1558 | |
99543e8b RS |
1559 | If you want to find all matches for a regexp in part of the buffer, |
1560 | and replace them, the best way is to write an explicit loop using | |
1561 | @code{re-search-forward} and @code{replace-match}, like this: | |
7015aca4 | 1562 | |
99543e8b RS |
1563 | @example |
1564 | (while (re-search-forward "foo[ \t]+bar" nil t) | |
1565 | (replace-match "foobar")) | |
1566 | @end example | |
7015aca4 | 1567 | |
99543e8b RS |
1568 | @noindent |
1569 | @xref{Replacing Match,, Replacing the Text that Matched}, for a | |
1570 | description of @code{replace-match}. | |
7015aca4 | 1571 | |
99543e8b RS |
1572 | However, replacing matches in a string is more complex, especially |
1573 | if you want to do it efficiently. So Emacs provides a function to do | |
1574 | this. | |
7fd1911a | 1575 | |
99543e8b RS |
1576 | @defun replace-regexp-in-string regexp rep string &optional fixedcase literal subexp start |
1577 | This function copies @var{string} and searches it for matches for | |
1578 | @var{regexp}, and replaces them with @var{rep}. It returns the | |
1579 | modified copy. If @var{start} is non-@code{nil}, the search for | |
1580 | matches starts at that index in @var{string}, so matches starting | |
1581 | before that index are not changed. | |
7015aca4 | 1582 | |
99543e8b RS |
1583 | This function uses @code{replace-match} to do the replacement, and it |
1584 | passes the optional arguments @var{fixedcase}, @var{literal} and | |
1585 | @var{subexp} along to @code{replace-match}. | |
7015aca4 | 1586 | |
99543e8b RS |
1587 | Instead of a string, @var{rep} can be a function. In that case, |
1588 | @code{replace-regexp-in-string} calls @var{rep} for each match, | |
1589 | passing the text of the match as its sole argument. It collects the | |
1590 | value @var{rep} returns and passes that to @code{replace-match} as the | |
1591 | replacement string. The match-data at this point are the result | |
1592 | of matching @var{regexp} against a substring of @var{string}. | |
1593 | @end defun | |
1594 | ||
1595 | If you want to write a command along the lines of @code{query-replace}, | |
1596 | you can use @code{perform-replace} to do the work. | |
1597 | ||
1598 | @defun perform-replace from-string replacements query-flag regexp-flag delimited-flag &optional repeat-count map start end | |
1599 | This function is the guts of @code{query-replace} and related | |
1600 | commands. It searches for occurrences of @var{from-string} in the | |
1601 | text between positions @var{start} and @var{end} and replaces some or | |
1602 | all of them. If @var{start} is @code{nil} (or omitted), point is used | |
1603 | instead, and the end of the buffer's accessible portion is used for | |
1604 | @var{end}. | |
1605 | ||
1606 | If @var{query-flag} is @code{nil}, it replaces all | |
1607 | occurrences; otherwise, it asks the user what to do about each one. | |
1608 | ||
1609 | If @var{regexp-flag} is non-@code{nil}, then @var{from-string} is | |
1610 | considered a regular expression; otherwise, it must match literally. If | |
1611 | @var{delimited-flag} is non-@code{nil}, then only replacements | |
1612 | surrounded by word boundaries are considered. | |
1613 | ||
1614 | The argument @var{replacements} specifies what to replace occurrences | |
1615 | with. If it is a string, that string is used. It can also be a list of | |
1616 | strings, to be used in cyclic order. | |
1617 | ||
1618 | If @var{replacements} is a cons cell, @code{(@var{function} | |
1619 | . @var{data})}, this means to call @var{function} after each match to | |
1620 | get the replacement text. This function is called with two arguments: | |
1621 | @var{data}, and the number of replacements already made. | |
1622 | ||
1623 | If @var{repeat-count} is non-@code{nil}, it should be an integer. Then | |
1624 | it specifies how many times to use each of the strings in the | |
1625 | @var{replacements} list before advancing cyclically to the next one. | |
1626 | ||
1627 | If @var{from-string} contains upper-case letters, then | |
1628 | @code{perform-replace} binds @code{case-fold-search} to @code{nil}, and | |
1629 | it uses the @code{replacements} without altering the case of them. | |
1630 | ||
1631 | Normally, the keymap @code{query-replace-map} defines the possible | |
1632 | user responses for queries. The argument @var{map}, if | |
1633 | non-@code{nil}, specifies a keymap to use instead of | |
1634 | @code{query-replace-map}. | |
1635 | @end defun | |
1636 | ||
1637 | @defvar query-replace-map | |
1638 | This variable holds a special keymap that defines the valid user | |
1639 | responses for @code{perform-replace} and the commands that use it, as | |
1640 | well as @code{y-or-n-p} and @code{map-y-or-n-p}. This map is unusual | |
1641 | in two ways: | |
1642 | ||
1643 | @itemize @bullet | |
1644 | @item | |
1645 | The ``key bindings'' are not commands, just symbols that are meaningful | |
1646 | to the functions that use this map. | |
1647 | ||
1648 | @item | |
1649 | Prefix keys are not supported; each key binding must be for a | |
1650 | single-event key sequence. This is because the functions don't use | |
1651 | @code{read-key-sequence} to get the input; instead, they read a single | |
1652 | event and look it up ``by hand.'' | |
1653 | @end itemize | |
7015aca4 RS |
1654 | @end defvar |
1655 | ||
99543e8b RS |
1656 | Here are the meaningful ``bindings'' for @code{query-replace-map}. |
1657 | Several of them are meaningful only for @code{query-replace} and | |
1658 | friends. | |
1659 | ||
1660 | @table @code | |
1661 | @item act | |
1662 | Do take the action being considered---in other words, ``yes.'' | |
1663 | ||
1664 | @item skip | |
1665 | Do not take action for this question---in other words, ``no.'' | |
1666 | ||
1667 | @item exit | |
1668 | Answer this question ``no,'' and give up on the entire series of | |
1669 | questions, assuming that the answers will be ``no.'' | |
1670 | ||
1671 | @item act-and-exit | |
1672 | Answer this question ``yes,'' and give up on the entire series of | |
1673 | questions, assuming that subsequent answers will be ``no.'' | |
1674 | ||
1675 | @item act-and-show | |
1676 | Answer this question ``yes,'' but show the results---don't advance yet | |
1677 | to the next question. | |
1678 | ||
1679 | @item automatic | |
1680 | Answer this question and all subsequent questions in the series with | |
1681 | ``yes,'' without further user interaction. | |
1682 | ||
1683 | @item backup | |
1684 | Move back to the previous place that a question was asked about. | |
1685 | ||
1686 | @item edit | |
1687 | Enter a recursive edit to deal with this question---instead of any | |
1688 | other action that would normally be taken. | |
1689 | ||
1690 | @item delete-and-edit | |
1691 | Delete the text being considered, then enter a recursive edit to replace | |
1692 | it. | |
1693 | ||
1694 | @item recenter | |
1695 | Redisplay and center the window, then ask the same question again. | |
1696 | ||
1697 | @item quit | |
1698 | Perform a quit right away. Only @code{y-or-n-p} and related functions | |
1699 | use this answer. | |
1700 | ||
1701 | @item help | |
1702 | Display some help, then ask again. | |
1703 | @end table | |
1704 | ||
7015aca4 RS |
1705 | @node Standard Regexps |
1706 | @section Standard Regular Expressions Used in Editing | |
1707 | @cindex regexps used standardly in editing | |
1708 | @cindex standard regexps used in editing | |
1709 | ||
1710 | This section describes some variables that hold regular expressions | |
1711 | used for certain purposes in editing: | |
1712 | ||
1713 | @defvar page-delimiter | |
969fe9b5 RS |
1714 | This is the regular expression describing line-beginnings that separate |
1715 | pages. The default value is @code{"^\014"} (i.e., @code{"^^L"} or | |
1716 | @code{"^\C-l"}); this matches a line that starts with a formfeed | |
1717 | character. | |
7015aca4 RS |
1718 | @end defvar |
1719 | ||
22697dac KH |
1720 | The following two regular expressions should @emph{not} assume the |
1721 | match always starts at the beginning of a line; they should not use | |
1722 | @samp{^} to anchor the match. Most often, the paragraph commands do | |
1723 | check for a match only at the beginning of a line, which means that | |
bfe721d1 KH |
1724 | @samp{^} would be superfluous. When there is a nonzero left margin, |
1725 | they accept matches that start after the left margin. In that case, a | |
1726 | @samp{^} would be incorrect. However, a @samp{^} is harmless in modes | |
1727 | where a left margin is never used. | |
22697dac | 1728 | |
7015aca4 RS |
1729 | @defvar paragraph-separate |
1730 | This is the regular expression for recognizing the beginning of a line | |
1731 | that separates paragraphs. (If you change this, you may have to | |
7fd1911a | 1732 | change @code{paragraph-start} also.) The default value is |
22697dac KH |
1733 | @w{@code{"[@ \t\f]*$"}}, which matches a line that consists entirely of |
1734 | spaces, tabs, and form feeds (after its left margin). | |
7015aca4 RS |
1735 | @end defvar |
1736 | ||
1737 | @defvar paragraph-start | |
1738 | This is the regular expression for recognizing the beginning of a line | |
1739 | that starts @emph{or} separates paragraphs. The default value is | |
bcb6b6b8 LT |
1740 | @w{@code{"\f\\|[ \t]*$"}}, which matches a line containing only |
1741 | whitespace or starting with a form feed (after its left margin). | |
7015aca4 RS |
1742 | @end defvar |
1743 | ||
1744 | @defvar sentence-end | |
45fa30b2 LT |
1745 | If non-@code{nil}, the value should be a regular expression describing |
1746 | the end of a sentence, including the whitespace following the | |
1747 | sentence. (All paragraph boundaries also end sentences, regardless.) | |
1748 | ||
1749 | If the value is @code{nil}, the default, then the function | |
1750 | @code{sentence-end} has to construct the regexp. That is why you | |
1751 | should always call the function @code{sentence-end} to obtain the | |
1752 | regexp to be used to recognize the end of a sentence. | |
7015aca4 | 1753 | @end defvar |
ab5796a9 | 1754 | |
45fa30b2 LT |
1755 | @defun sentence-end |
1756 | This function returns the value of the variable @code{sentence-end}, | |
1757 | if non-@code{nil}. Otherwise it returns a default value based on the | |
1758 | values of the variables @code{sentence-end-double-space} | |
1759 | (@pxref{Definition of sentence-end-double-space}), | |
1760 | @code{sentence-end-without-period} and | |
1761 | @code{sentence-end-without-space}. | |
1762 | @end defun | |
1763 | ||
ab5796a9 MB |
1764 | @ignore |
1765 | arch-tag: c2573ca2-18aa-4839-93b8-924043ef831f | |
1766 | @end ignore |