|
428
|
1 @c -*-texinfo-*-
|
|
|
2 @c This is part of the XEmacs Lisp Reference Manual.
|
|
444
|
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc.
|
|
428
|
4 @c See the file lispref.texi for copying conditions.
|
|
|
5 @setfilename ../../info/searching.info
|
|
|
6 @node Searching and Matching, Syntax Tables, Text, Top
|
|
|
7 @chapter Searching and Matching
|
|
|
8 @cindex searching
|
|
|
9
|
|
|
10 XEmacs provides two ways to search through a buffer for specified
|
|
|
11 text: exact string searches and regular expression searches. After a
|
|
|
12 regular expression search, you can examine the @dfn{match data} to
|
|
|
13 determine which text matched the whole regular expression or various
|
|
|
14 portions of it.
|
|
|
15
|
|
|
16 @menu
|
|
|
17 * String Search:: Search for an exact match.
|
|
|
18 * Regular Expressions:: Describing classes of strings.
|
|
|
19 * Regexp Search:: Searching for a match for a regexp.
|
|
|
20 * POSIX Regexps:: Searching POSIX-style for the longest match.
|
|
|
21 * Search and Replace:: Internals of @code{query-replace}.
|
|
|
22 * Match Data:: Finding out which part of the text matched
|
|
|
23 various parts of a regexp, after regexp search.
|
|
|
24 * Searching and Case:: Case-independent or case-significant searching.
|
|
|
25 * Standard Regexps:: Useful regexps for finding sentences, pages,...
|
|
|
26 @end menu
|
|
|
27
|
|
|
28 The @samp{skip-chars@dots{}} functions also perform a kind of searching.
|
|
|
29 @xref{Skipping Characters}.
|
|
|
30
|
|
|
31 @node String Search
|
|
|
32 @section Searching for Strings
|
|
|
33 @cindex string search
|
|
|
34
|
|
|
35 These are the primitive functions for searching through the text in a
|
|
|
36 buffer. They are meant for use in programs, but you may call them
|
|
|
37 interactively. If you do so, they prompt for the search string;
|
|
444
|
38 @var{limit} and @var{noerror} are set to @code{nil}, and @var{count}
|
|
428
|
39 is set to 1.
|
|
|
40
|
|
444
|
41 @deffn Command search-forward string &optional limit noerror count buffer
|
|
428
|
42 This function searches forward from point for an exact match for
|
|
|
43 @var{string}. If successful, it sets point to the end of the occurrence
|
|
|
44 found, and returns the new value of point. If no match is found, the
|
|
|
45 value and side effects depend on @var{noerror} (see below).
|
|
|
46
|
|
|
47 In the following example, point is initially at the beginning of the
|
|
|
48 line. Then @code{(search-forward "fox")} moves point after the last
|
|
|
49 letter of @samp{fox}:
|
|
|
50
|
|
|
51 @example
|
|
|
52 @group
|
|
|
53 ---------- Buffer: foo ----------
|
|
|
54 @point{}The quick brown fox jumped over the lazy dog.
|
|
|
55 ---------- Buffer: foo ----------
|
|
|
56 @end group
|
|
|
57
|
|
|
58 @group
|
|
|
59 (search-forward "fox")
|
|
|
60 @result{} 20
|
|
|
61
|
|
|
62 ---------- Buffer: foo ----------
|
|
|
63 The quick brown fox@point{} jumped over the lazy dog.
|
|
|
64 ---------- Buffer: foo ----------
|
|
|
65 @end group
|
|
|
66 @end example
|
|
|
67
|
|
|
68 The argument @var{limit} specifies the upper bound to the search. (It
|
|
|
69 must be a position in the current buffer.) No match extending after
|
|
|
70 that position is accepted. If @var{limit} is omitted or @code{nil}, it
|
|
|
71 defaults to the end of the accessible portion of the buffer.
|
|
|
72
|
|
|
73 @kindex search-failed
|
|
|
74 What happens when the search fails depends on the value of
|
|
|
75 @var{noerror}. If @var{noerror} is @code{nil}, a @code{search-failed}
|
|
|
76 error is signaled. If @var{noerror} is @code{t}, @code{search-forward}
|
|
|
77 returns @code{nil} and does nothing. If @var{noerror} is neither
|
|
|
78 @code{nil} nor @code{t}, then @code{search-forward} moves point to the
|
|
|
79 upper bound and returns @code{nil}. (It would be more consistent now
|
|
|
80 to return the new position of point in that case, but some programs
|
|
|
81 may depend on a value of @code{nil}.)
|
|
|
82
|
|
444
|
83 If @var{count} is supplied (it must be an integer), then the search is
|
|
|
84 repeated that many times (each time starting at the end of the previous
|
|
|
85 time's match). If @var{count} is negative, the search direction is
|
|
|
86 backward. If the successive searches succeed, the function succeeds,
|
|
|
87 moving point and returning its new value. Otherwise the search fails.
|
|
|
88
|
|
|
89 @var{buffer} is the buffer to search in, and defaults to the current buffer.
|
|
428
|
90 @end deffn
|
|
|
91
|
|
444
|
92 @deffn Command search-backward string &optional limit noerror count buffer
|
|
428
|
93 This function searches backward from point for @var{string}. It is
|
|
|
94 just like @code{search-forward} except that it searches backwards and
|
|
|
95 leaves point at the beginning of the match.
|
|
|
96 @end deffn
|
|
|
97
|
|
444
|
98 @deffn Command word-search-forward string &optional limit noerror count buffer
|
|
428
|
99 @cindex word search
|
|
|
100 This function searches forward from point for a ``word'' match for
|
|
|
101 @var{string}. If it finds a match, it sets point to the end of the
|
|
|
102 match found, and returns the new value of point.
|
|
|
103
|
|
|
104 Word matching regards @var{string} as a sequence of words, disregarding
|
|
|
105 punctuation that separates them. It searches the buffer for the same
|
|
|
106 sequence of words. Each word must be distinct in the buffer (searching
|
|
|
107 for the word @samp{ball} does not match the word @samp{balls}), but the
|
|
|
108 details of punctuation and spacing are ignored (searching for @samp{ball
|
|
|
109 boy} does match @samp{ball. Boy!}).
|
|
|
110
|
|
|
111 In this example, point is initially at the beginning of the buffer; the
|
|
|
112 search leaves it between the @samp{y} and the @samp{!}.
|
|
|
113
|
|
|
114 @example
|
|
|
115 @group
|
|
|
116 ---------- Buffer: foo ----------
|
|
|
117 @point{}He said "Please! Find
|
|
|
118 the ball boy!"
|
|
|
119 ---------- Buffer: foo ----------
|
|
|
120 @end group
|
|
|
121
|
|
|
122 @group
|
|
|
123 (word-search-forward "Please find the ball, boy.")
|
|
|
124 @result{} 35
|
|
|
125
|
|
|
126 ---------- Buffer: foo ----------
|
|
|
127 He said "Please! Find
|
|
|
128 the ball boy@point{}!"
|
|
|
129 ---------- Buffer: foo ----------
|
|
|
130 @end group
|
|
|
131 @end example
|
|
|
132
|
|
|
133 If @var{limit} is non-@code{nil} (it must be a position in the current
|
|
|
134 buffer), then it is the upper bound to the search. The match found must
|
|
|
135 not extend after that position.
|
|
|
136
|
|
|
137 If @var{noerror} is @code{nil}, then @code{word-search-forward} signals
|
|
|
138 an error if the search fails. If @var{noerror} is @code{t}, then it
|
|
|
139 returns @code{nil} instead of signaling an error. If @var{noerror} is
|
|
|
140 neither @code{nil} nor @code{t}, it moves point to @var{limit} (or the
|
|
|
141 end of the buffer) and returns @code{nil}.
|
|
|
142
|
|
444
|
143 If @var{count} is non-@code{nil}, then the search is repeated that many
|
|
428
|
144 times. Point is positioned at the end of the last match.
|
|
444
|
145
|
|
|
146 @var{buffer} is the buffer to search in, and defaults to the current buffer.
|
|
428
|
147 @end deffn
|
|
|
148
|
|
444
|
149 @deffn Command word-search-backward string &optional limit noerror count buffer
|
|
428
|
150 This function searches backward from point for a word match to
|
|
|
151 @var{string}. This function is just like @code{word-search-forward}
|
|
|
152 except that it searches backward and normally leaves point at the
|
|
|
153 beginning of the match.
|
|
|
154 @end deffn
|
|
|
155
|
|
|
156 @node Regular Expressions
|
|
|
157 @section Regular Expressions
|
|
|
158 @cindex regular expression
|
|
|
159 @cindex regexp
|
|
|
160
|
|
|
161 A @dfn{regular expression} (@dfn{regexp}, for short) is a pattern that
|
|
|
162 denotes a (possibly infinite) set of strings. Searching for matches for
|
|
|
163 a regexp is a very powerful operation. This section explains how to write
|
|
|
164 regexps; the following section says how to search for them.
|
|
|
165
|
|
|
166 To gain a thorough understanding of regular expressions and how to use
|
|
|
167 them to best advantage, we recommend that you study @cite{Mastering
|
|
|
168 Regular Expressions, by Jeffrey E.F. Friedl, O'Reilly and Associates,
|
|
|
169 1997}. (It's known as the "Hip Owls" book, because of the picture on its
|
|
|
170 cover.) You might also read the manuals to @ref{(gawk)Top},
|
|
|
171 @ref{(ed)Top}, @cite{sed}, @cite{grep}, @ref{(perl)Top},
|
|
|
172 @ref{(regex)Top}, @ref{(rx)Top}, @cite{pcre}, and @ref{(flex)Top}, which
|
|
|
173 also make good use of regular expressions.
|
|
|
174
|
|
|
175 The XEmacs regular expression syntax most closely resembles that of
|
|
|
176 @cite{ed}, or @cite{grep}, the GNU versions of which all utilize the GNU
|
|
|
177 @cite{regex} library. XEmacs' version of @cite{regex} has recently been
|
|
|
178 extended with some Perl--like capabilities, described in the next
|
|
|
179 section.
|
|
|
180
|
|
|
181 @menu
|
|
|
182 * Syntax of Regexps:: Rules for writing regular expressions.
|
|
|
183 * Regexp Example:: Illustrates regular expression syntax.
|
|
|
184 @end menu
|
|
|
185
|
|
|
186 @node Syntax of Regexps
|
|
|
187 @subsection Syntax of Regular Expressions
|
|
|
188
|
|
|
189 Regular expressions have a syntax in which a few characters are
|
|
|
190 special constructs and the rest are @dfn{ordinary}. An ordinary
|
|
|
191 character is a simple regular expression that matches that character and
|
|
|
192 nothing else. The special characters are @samp{.}, @samp{*}, @samp{+},
|
|
|
193 @samp{?}, @samp{[}, @samp{]}, @samp{^}, @samp{$}, and @samp{\}; no new
|
|
|
194 special characters will be defined in the future. Any other character
|
|
|
195 appearing in a regular expression is ordinary, unless a @samp{\}
|
|
|
196 precedes it.
|
|
|
197
|
|
|
198 For example, @samp{f} is not a special character, so it is ordinary, and
|
|
|
199 therefore @samp{f} is a regular expression that matches the string
|
|
|
200 @samp{f} and no other string. (It does @emph{not} match the string
|
|
|
201 @samp{ff}.) Likewise, @samp{o} is a regular expression that matches
|
|
|
202 only @samp{o}.@refill
|
|
|
203
|
|
|
204 Any two regular expressions @var{a} and @var{b} can be concatenated. The
|
|
|
205 result is a regular expression that matches a string if @var{a} matches
|
|
|
206 some amount of the beginning of that string and @var{b} matches the rest of
|
|
|
207 the string.@refill
|
|
|
208
|
|
|
209 As a simple example, we can concatenate the regular expressions @samp{f}
|
|
|
210 and @samp{o} to get the regular expression @samp{fo}, which matches only
|
|
|
211 the string @samp{fo}. Still trivial. To do something more powerful, you
|
|
|
212 need to use one of the special characters. Here is a list of them:
|
|
|
213
|
|
|
214 @need 1200
|
|
|
215 @table @kbd
|
|
|
216 @item .@: @r{(Period)}
|
|
|
217 @cindex @samp{.} in regexp
|
|
|
218 is a special character that matches any single character except a newline.
|
|
|
219 Using concatenation, we can make regular expressions like @samp{a.b}, which
|
|
|
220 matches any three-character string that begins with @samp{a} and ends with
|
|
|
221 @samp{b}.@refill
|
|
|
222
|
|
|
223 @item *
|
|
|
224 @cindex @samp{*} in regexp
|
|
|
225 is not a construct by itself; it is a quantifying suffix operator that
|
|
|
226 means to repeat the preceding regular expression as many times as
|
|
|
227 possible. In @samp{fo*}, the @samp{*} applies to the @samp{o}, so
|
|
|
228 @samp{fo*} matches one @samp{f} followed by any number of @samp{o}s.
|
|
|
229 The case of zero @samp{o}s is allowed: @samp{fo*} does match
|
|
|
230 @samp{f}.@refill
|
|
|
231
|
|
|
232 @samp{*} always applies to the @emph{smallest} possible preceding
|
|
|
233 expression. Thus, @samp{fo*} has a repeating @samp{o}, not a
|
|
|
234 repeating @samp{fo}.@refill
|
|
|
235
|
|
|
236 The matcher processes a @samp{*} construct by matching, immediately, as
|
|
|
237 many repetitions as can be found; it is "greedy". Then it continues
|
|
|
238 with the rest of the pattern. If that fails, backtracking occurs,
|
|
|
239 discarding some of the matches of the @samp{*}-modified construct in
|
|
|
240 case that makes it possible to match the rest of the pattern. For
|
|
|
241 example, in matching @samp{ca*ar} against the string @samp{caaar}, the
|
|
|
242 @samp{a*} first tries to match all three @samp{a}s; but the rest of the
|
|
|
243 pattern is @samp{ar} and there is only @samp{r} left to match, so this
|
|
|
244 try fails. The next alternative is for @samp{a*} to match only two
|
|
|
245 @samp{a}s. With this choice, the rest of the regexp matches
|
|
|
246 successfully.@refill
|
|
|
247
|
|
|
248 Nested repetition operators can be extremely slow if they specify
|
|
|
249 backtracking loops. For example, it could take hours for the regular
|
|
|
250 expression @samp{\(x+y*\)*a} to match the sequence
|
|
|
251 @samp{xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz}. The slowness is because
|
|
|
252 Emacs must try each imaginable way of grouping the 35 @samp{x}'s before
|
|
|
253 concluding that none of them can work. To make sure your regular
|
|
|
254 expressions run fast, check nested repetitions carefully.
|
|
|
255
|
|
|
256 @item +
|
|
|
257 @cindex @samp{+} in regexp
|
|
|
258 is a quantifying suffix operator similar to @samp{*} except that the
|
|
|
259 preceding expression must match at least once. It is also "greedy".
|
|
|
260 So, for example, @samp{ca+r} matches the strings @samp{car} and
|
|
|
261 @samp{caaaar} but not the string @samp{cr}, whereas @samp{ca*r} matches
|
|
|
262 all three strings.
|
|
|
263
|
|
|
264 @item ?
|
|
|
265 @cindex @samp{?} in regexp
|
|
|
266 is a quantifying suffix operator similar to @samp{*}, except that the
|
|
|
267 preceding expression can match either once or not at all. For example,
|
|
|
268 @samp{ca?r} matches @samp{car} or @samp{cr}, but does not match anything
|
|
|
269 else.
|
|
|
270
|
|
|
271 @item *?
|
|
|
272 @cindex @samp{*?} in regexp
|
|
|
273 works just like @samp{*}, except that rather than matching the longest
|
|
|
274 match, it matches the shortest match. @samp{*?} is known as a
|
|
|
275 @dfn{non-greedy} quantifier, a regexp construct borrowed from Perl.
|
|
|
276 @c Did perl get this from somewhere? What's the real history of *? ?
|
|
|
277
|
|
442
|
278 This construct is very useful for when you want to match the text inside
|
|
|
279 a pair of delimiters. For instance, @samp{/\*.*?\*/} will match C
|
|
|
280 comments in a string. This could not easily be achieved without the use
|
|
|
281 of a non-greedy quantifier.
|
|
428
|
282
|
|
|
283 This construct has not been available prior to XEmacs 20.4. It is not
|
|
|
284 available in FSF Emacs.
|
|
|
285
|
|
|
286 @item +?
|
|
|
287 @cindex @samp{+?} in regexp
|
|
442
|
288 is the non-greedy version of @samp{+}.
|
|
|
289
|
|
|
290 @item ??
|
|
|
291 @cindex @samp{??} in regexp
|
|
|
292 is the non-greedy version of @samp{?}.
|
|
428
|
293
|
|
|
294 @item \@{n,m\@}
|
|
|
295 @c Note the spacing after the close brace is deliberate.
|
|
|
296 @cindex @samp{\@{n,m\@} }in regexp
|
|
|
297 serves as an interval quantifier, analogous to @samp{*} or @samp{+}, but
|
|
|
298 specifies that the expression must match at least @var{n} times, but no
|
|
|
299 more than @var{m} times. This syntax is supported by most Unix regexp
|
|
|
300 utilities, and has been introduced to XEmacs for the version 20.3.
|
|
|
301
|
|
442
|
302 Unfortunately, the non-greedy version of this quantifier does not exist
|
|
|
303 currently, although it does in Perl.
|
|
|
304
|
|
428
|
305 @item [ @dots{} ]
|
|
|
306 @cindex character set (in regexp)
|
|
|
307 @cindex @samp{[} in regexp
|
|
|
308 @cindex @samp{]} in regexp
|
|
|
309 @samp{[} begins a @dfn{character set}, which is terminated by a
|
|
|
310 @samp{]}. In the simplest case, the characters between the two brackets
|
|
|
311 form the set. Thus, @samp{[ad]} matches either one @samp{a} or one
|
|
|
312 @samp{d}, and @samp{[ad]*} matches any string composed of just @samp{a}s
|
|
|
313 and @samp{d}s (including the empty string), from which it follows that
|
|
|
314 @samp{c[ad]*r} matches @samp{cr}, @samp{car}, @samp{cdr},
|
|
|
315 @samp{caddaar}, etc.@refill
|
|
|
316
|
|
|
317 The usual regular expression special characters are not special inside a
|
|
|
318 character set. A completely different set of special characters exists
|
|
|
319 inside character sets: @samp{]}, @samp{-} and @samp{^}.@refill
|
|
|
320
|
|
|
321 @samp{-} is used for ranges of characters. To write a range, write two
|
|
|
322 characters with a @samp{-} between them. Thus, @samp{[a-z]} matches any
|
|
|
323 lower case letter. Ranges may be intermixed freely with individual
|
|
|
324 characters, as in @samp{[a-z$%.]}, which matches any lower case letter
|
|
|
325 or @samp{$}, @samp{%}, or a period.@refill
|
|
|
326
|
|
|
327 To include a @samp{]} in a character set, make it the first character.
|
|
|
328 For example, @samp{[]a]} matches @samp{]} or @samp{a}. To include a
|
|
|
329 @samp{-}, write @samp{-} as the first character in the set, or put it
|
|
|
330 immediately after a range. (You can replace one individual character
|
|
|
331 @var{c} with the range @samp{@var{c}-@var{c}} to make a place to put the
|
|
|
332 @samp{-}.) There is no way to write a set containing just @samp{-} and
|
|
|
333 @samp{]}.
|
|
|
334
|
|
|
335 To include @samp{^} in a set, put it anywhere but at the beginning of
|
|
|
336 the set.
|
|
|
337
|
|
|
338 @item [^ @dots{} ]
|
|
|
339 @cindex @samp{^} in regexp
|
|
|
340 @samp{[^} begins a @dfn{complement character set}, which matches any
|
|
|
341 character except the ones specified. Thus, @samp{[^a-z0-9A-Z]}
|
|
|
342 matches all characters @emph{except} letters and digits.@refill
|
|
|
343
|
|
|
344 @samp{^} is not special in a character set unless it is the first
|
|
|
345 character. The character following the @samp{^} is treated as if it
|
|
|
346 were first (thus, @samp{-} and @samp{]} are not special there).
|
|
|
347
|
|
|
348 Note that a complement character set can match a newline, unless
|
|
|
349 newline is mentioned as one of the characters not to match.
|
|
|
350
|
|
|
351 @item ^
|
|
|
352 @cindex @samp{^} in regexp
|
|
|
353 @cindex beginning of line in regexp
|
|
|
354 is a special character that matches the empty string, but only at the
|
|
|
355 beginning of a line in the text being matched. Otherwise it fails to
|
|
|
356 match anything. Thus, @samp{^foo} matches a @samp{foo} that occurs at
|
|
|
357 the beginning of a line.
|
|
|
358
|
|
|
359 When matching a string instead of a buffer, @samp{^} matches at the
|
|
|
360 beginning of the string or after a newline character @samp{\n}.
|
|
|
361
|
|
|
362 @item $
|
|
|
363 @cindex @samp{$} in regexp
|
|
|
364 is similar to @samp{^} but matches only at the end of a line. Thus,
|
|
|
365 @samp{x+$} matches a string of one @samp{x} or more at the end of a line.
|
|
|
366
|
|
|
367 When matching a string instead of a buffer, @samp{$} matches at the end
|
|
|
368 of the string or before a newline character @samp{\n}.
|
|
|
369
|
|
|
370 @item \
|
|
|
371 @cindex @samp{\} in regexp
|
|
|
372 has two functions: it quotes the special characters (including
|
|
|
373 @samp{\}), and it introduces additional special constructs.
|
|
|
374
|
|
|
375 Because @samp{\} quotes special characters, @samp{\$} is a regular
|
|
|
376 expression that matches only @samp{$}, and @samp{\[} is a regular
|
|
|
377 expression that matches only @samp{[}, and so on.
|
|
|
378
|
|
|
379 Note that @samp{\} also has special meaning in the read syntax of Lisp
|
|
|
380 strings (@pxref{String Type}), and must be quoted with @samp{\}. For
|
|
|
381 example, the regular expression that matches the @samp{\} character is
|
|
|
382 @samp{\\}. To write a Lisp string that contains the characters
|
|
|
383 @samp{\\}, Lisp syntax requires you to quote each @samp{\} with another
|
|
|
384 @samp{\}. Therefore, the read syntax for a regular expression matching
|
|
|
385 @samp{\} is @code{"\\\\"}.@refill
|
|
|
386 @end table
|
|
|
387
|
|
|
388 @strong{Please note:} For historical compatibility, special characters
|
|
|
389 are treated as ordinary ones if they are in contexts where their special
|
|
|
390 meanings make no sense. For example, @samp{*foo} treats @samp{*} as
|
|
|
391 ordinary since there is no preceding expression on which the @samp{*}
|
|
|
392 can act. It is poor practice to depend on this behavior; quote the
|
|
|
393 special character anyway, regardless of where it appears.@refill
|
|
|
394
|
|
|
395 For the most part, @samp{\} followed by any character matches only
|
|
|
396 that character. However, there are several exceptions: characters
|
|
|
397 that, when preceded by @samp{\}, are special constructs. Such
|
|
|
398 characters are always ordinary when encountered on their own. Here
|
|
|
399 is a table of @samp{\} constructs:
|
|
|
400
|
|
|
401 @table @kbd
|
|
|
402 @item \|
|
|
|
403 @cindex @samp{|} in regexp
|
|
|
404 @cindex regexp alternative
|
|
|
405 specifies an alternative.
|
|
|
406 Two regular expressions @var{a} and @var{b} with @samp{\|} in
|
|
|
407 between form an expression that matches anything that either @var{a} or
|
|
|
408 @var{b} matches.@refill
|
|
|
409
|
|
|
410 Thus, @samp{foo\|bar} matches either @samp{foo} or @samp{bar}
|
|
|
411 but no other string.@refill
|
|
|
412
|
|
|
413 @samp{\|} applies to the largest possible surrounding expressions. Only a
|
|
|
414 surrounding @samp{\( @dots{} \)} grouping can limit the grouping power of
|
|
|
415 @samp{\|}.@refill
|
|
|
416
|
|
|
417 Full backtracking capability exists to handle multiple uses of @samp{\|}.
|
|
|
418
|
|
|
419 @item \( @dots{} \)
|
|
|
420 @cindex @samp{(} in regexp
|
|
|
421 @cindex @samp{)} in regexp
|
|
|
422 @cindex regexp grouping
|
|
|
423 is a grouping construct that serves three purposes:
|
|
|
424
|
|
|
425 @enumerate
|
|
|
426 @item
|
|
|
427 To enclose a set of @samp{\|} alternatives for other operations.
|
|
|
428 Thus, @samp{\(foo\|bar\)x} matches either @samp{foox} or @samp{barx}.
|
|
|
429
|
|
|
430 @item
|
|
|
431 To enclose an expression for a suffix operator such as @samp{*} to act
|
|
|
432 on. Thus, @samp{ba\(na\)*} matches @samp{bananana}, etc., with any
|
|
|
433 (zero or more) number of @samp{na} strings.@refill
|
|
|
434
|
|
|
435 @item
|
|
|
436 To record a matched substring for future reference.
|
|
|
437 @end enumerate
|
|
|
438
|
|
|
439 This last application is not a consequence of the idea of a
|
|
|
440 parenthetical grouping; it is a separate feature that happens to be
|
|
|
441 assigned as a second meaning to the same @samp{\( @dots{} \)} construct
|
|
|
442 because there is no conflict in practice between the two meanings.
|
|
|
443 Here is an explanation of this feature:
|
|
|
444
|
|
|
445 @item \@var{digit}
|
|
|
446 matches the same text that matched the @var{digit}th occurrence of a
|
|
|
447 @samp{\( @dots{} \)} construct.
|
|
|
448
|
|
|
449 In other words, after the end of a @samp{\( @dots{} \)} construct. the
|
|
|
450 matcher remembers the beginning and end of the text matched by that
|
|
|
451 construct. Then, later on in the regular expression, you can use
|
|
|
452 @samp{\} followed by @var{digit} to match that same text, whatever it
|
|
|
453 may have been.
|
|
|
454
|
|
|
455 The strings matching the first nine @samp{\( @dots{} \)} constructs
|
|
|
456 appearing in a regular expression are assigned numbers 1 through 9 in
|
|
|
457 the order that the open parentheses appear in the regular expression.
|
|
|
458 So you can use @samp{\1} through @samp{\9} to refer to the text matched
|
|
|
459 by the corresponding @samp{\( @dots{} \)} constructs.
|
|
|
460
|
|
|
461 For example, @samp{\(.*\)\1} matches any newline-free string that is
|
|
|
462 composed of two identical halves. The @samp{\(.*\)} matches the first
|
|
|
463 half, which may be anything, but the @samp{\1} that follows must match
|
|
|
464 the same exact text.
|
|
|
465
|
|
|
466 @item \(?: @dots{} \)
|
|
|
467 @cindex @samp{\(?:} in regexp
|
|
|
468 @cindex regexp grouping
|
|
|
469 is called a @dfn{shy} grouping operator, and it is used just like
|
|
|
470 @samp{\( @dots{} \)}, except that it does not cause the matched
|
|
|
471 substring to be recorded for future reference.
|
|
|
472
|
|
|
473 This is useful when you need a lot of grouping @samp{\( @dots{} \)}
|
|
442
|
474 constructs, but only want to remember one or two -- or if you have
|
|
|
475 more than nine groupings and need to use backreferences to refer to
|
|
|
476 the groupings at the end.
|
|
428
|
477
|
|
|
478 Using @samp{\(?: @dots{} \)} rather than @samp{\( @dots{} \)} when you
|
|
|
479 don't need the captured substrings ought to speed up your programs some,
|
|
|
480 since it shortens the code path followed by the regular expression
|
|
|
481 engine, as well as the amount of memory allocation and string copying it
|
|
|
482 must do. The actual performance gain to be observed has not been
|
|
|
483 measured or quantified as of this writing.
|
|
|
484 @c This is used to good advantage by the font-locking code, and by
|
|
442
|
485 @c `regexp-opt.el'.
|
|
428
|
486
|
|
|
487 The shy grouping operator has been borrowed from Perl, and has not been
|
|
|
488 available prior to XEmacs 20.3, nor is it available in FSF Emacs.
|
|
|
489
|
|
|
490 @item \w
|
|
|
491 @cindex @samp{\w} in regexp
|
|
|
492 matches any word-constituent character. The editor syntax table
|
|
|
493 determines which characters these are. @xref{Syntax Tables}.
|
|
|
494
|
|
|
495 @item \W
|
|
|
496 @cindex @samp{\W} in regexp
|
|
|
497 matches any character that is not a word constituent.
|
|
|
498
|
|
|
499 @item \s@var{code}
|
|
|
500 @cindex @samp{\s} in regexp
|
|
|
501 matches any character whose syntax is @var{code}. Here @var{code} is a
|
|
|
502 character that represents a syntax code: thus, @samp{w} for word
|
|
|
503 constituent, @samp{-} for whitespace, @samp{(} for open parenthesis,
|
|
|
504 etc. @xref{Syntax Tables}, for a list of syntax codes and the
|
|
|
505 characters that stand for them.
|
|
|
506
|
|
|
507 @item \S@var{code}
|
|
|
508 @cindex @samp{\S} in regexp
|
|
|
509 matches any character whose syntax is not @var{code}.
|
|
|
510 @end table
|
|
|
511
|
|
|
512 The following regular expression constructs match the empty string---that is,
|
|
|
513 they don't use up any characters---but whether they match depends on the
|
|
|
514 context.
|
|
|
515
|
|
|
516 @table @kbd
|
|
|
517 @item \`
|
|
|
518 @cindex @samp{\`} in regexp
|
|
|
519 matches the empty string, but only at the beginning
|
|
|
520 of the buffer or string being matched against.
|
|
|
521
|
|
|
522 @item \'
|
|
|
523 @cindex @samp{\'} in regexp
|
|
|
524 matches the empty string, but only at the end of
|
|
|
525 the buffer or string being matched against.
|
|
|
526
|
|
|
527 @item \=
|
|
|
528 @cindex @samp{\=} in regexp
|
|
|
529 matches the empty string, but only at point.
|
|
|
530 (This construct is not defined when matching against a string.)
|
|
|
531
|
|
|
532 @item \b
|
|
|
533 @cindex @samp{\b} in regexp
|
|
|
534 matches the empty string, but only at the beginning or
|
|
|
535 end of a word. Thus, @samp{\bfoo\b} matches any occurrence of
|
|
|
536 @samp{foo} as a separate word. @samp{\bballs?\b} matches
|
|
|
537 @samp{ball} or @samp{balls} as a separate word.@refill
|
|
|
538
|
|
|
539 @item \B
|
|
|
540 @cindex @samp{\B} in regexp
|
|
|
541 matches the empty string, but @emph{not} at the beginning or
|
|
|
542 end of a word.
|
|
|
543
|
|
|
544 @item \<
|
|
|
545 @cindex @samp{\<} in regexp
|
|
|
546 matches the empty string, but only at the beginning of a word.
|
|
|
547
|
|
|
548 @item \>
|
|
|
549 @cindex @samp{\>} in regexp
|
|
|
550 matches the empty string, but only at the end of a word.
|
|
|
551 @end table
|
|
|
552
|
|
|
553 @kindex invalid-regexp
|
|
|
554 Not every string is a valid regular expression. For example, a string
|
|
|
555 with unbalanced square brackets is invalid (with a few exceptions, such
|
|
|
556 as @samp{[]]}), and so is a string that ends with a single @samp{\}. If
|
|
|
557 an invalid regular expression is passed to any of the search functions,
|
|
|
558 an @code{invalid-regexp} error is signaled.
|
|
|
559
|
|
|
560 @defun regexp-quote string
|
|
|
561 This function returns a regular expression string that matches exactly
|
|
|
562 @var{string} and nothing else. This allows you to request an exact
|
|
|
563 string match when calling a function that wants a regular expression.
|
|
|
564
|
|
|
565 @example
|
|
|
566 @group
|
|
|
567 (regexp-quote "^The cat$")
|
|
|
568 @result{} "\\^The cat\\$"
|
|
|
569 @end group
|
|
|
570 @end example
|
|
|
571
|
|
|
572 One use of @code{regexp-quote} is to combine an exact string match with
|
|
|
573 context described as a regular expression. For example, this searches
|
|
|
574 for the string that is the value of @code{string}, surrounded by
|
|
|
575 whitespace:
|
|
|
576
|
|
|
577 @example
|
|
|
578 @group
|
|
|
579 (re-search-forward
|
|
|
580 (concat "\\s-" (regexp-quote string) "\\s-"))
|
|
|
581 @end group
|
|
|
582 @end example
|
|
|
583 @end defun
|
|
|
584
|
|
|
585 @node Regexp Example
|
|
|
586 @subsection Complex Regexp Example
|
|
|
587
|
|
|
588 Here is a complicated regexp, used by XEmacs to recognize the end of a
|
|
|
589 sentence together with any whitespace that follows. It is the value of
|
|
444
|
590 the variable @code{sentence-end}.
|
|
428
|
591
|
|
|
592 First, we show the regexp as a string in Lisp syntax to distinguish
|
|
|
593 spaces from tab characters. The string constant begins and ends with a
|
|
|
594 double-quote. @samp{\"} stands for a double-quote as part of the
|
|
|
595 string, @samp{\\} for a backslash as part of the string, @samp{\t} for a
|
|
|
596 tab and @samp{\n} for a newline.
|
|
|
597
|
|
|
598 @example
|
|
|
599 "[.?!][]\"')@}]*\\($\\| $\\|\t\\| \\)[ \t\n]*"
|
|
|
600 @end example
|
|
|
601
|
|
|
602 In contrast, if you evaluate the variable @code{sentence-end}, you
|
|
|
603 will see the following:
|
|
|
604
|
|
|
605 @example
|
|
|
606 @group
|
|
|
607 sentence-end
|
|
|
608 @result{}
|
|
444
|
609 "[.?!][]\"')@}]*\\($\\| $\\| \\| \\)[
|
|
428
|
610 ]*"
|
|
|
611 @end group
|
|
|
612 @end example
|
|
|
613
|
|
|
614 @noindent
|
|
|
615 In this output, tab and newline appear as themselves.
|
|
|
616
|
|
|
617 This regular expression contains four parts in succession and can be
|
|
|
618 deciphered as follows:
|
|
|
619
|
|
|
620 @table @code
|
|
|
621 @item [.?!]
|
|
|
622 The first part of the pattern is a character set that matches any one of
|
|
|
623 three characters: period, question mark, and exclamation mark. The
|
|
|
624 match must begin with one of these three characters.
|
|
|
625
|
|
|
626 @item []\"')@}]*
|
|
|
627 The second part of the pattern matches any closing braces and quotation
|
|
|
628 marks, zero or more of them, that may follow the period, question mark
|
|
|
629 or exclamation mark. The @code{\"} is Lisp syntax for a double-quote in
|
|
|
630 a string. The @samp{*} at the end indicates that the immediately
|
|
|
631 preceding regular expression (a character set, in this case) may be
|
|
|
632 repeated zero or more times.
|
|
|
633
|
|
|
634 @item \\($\\|@ $\\|\t\\|@ @ \\)
|
|
|
635 The third part of the pattern matches the whitespace that follows the
|
|
|
636 end of a sentence: the end of a line, or a tab, or two spaces. The
|
|
|
637 double backslashes mark the parentheses and vertical bars as regular
|
|
|
638 expression syntax; the parentheses delimit a group and the vertical bars
|
|
|
639 separate alternatives. The dollar sign is used to match the end of a
|
|
|
640 line.
|
|
|
641
|
|
|
642 @item [ \t\n]*
|
|
|
643 Finally, the last part of the pattern matches any additional whitespace
|
|
|
644 beyond the minimum needed to end a sentence.
|
|
|
645 @end table
|
|
|
646
|
|
|
647 @node Regexp Search
|
|
|
648 @section Regular Expression Searching
|
|
|
649 @cindex regular expression searching
|
|
|
650 @cindex regexp searching
|
|
|
651 @cindex searching for regexp
|
|
|
652
|
|
|
653 In XEmacs, you can search for the next match for a regexp either
|
|
|
654 incrementally or not. Incremental search commands are described in the
|
|
446
|
655 @cite{The XEmacs Lisp Reference Manual}. @xref{Regexp Search, , Regular Expression
|
|
|
656 Search, xemacs, The XEmacs Lisp Reference Manual}. Here we describe only the search
|
|
428
|
657 functions useful in programs. The principal one is
|
|
|
658 @code{re-search-forward}.
|
|
|
659
|
|
444
|
660 @deffn Command re-search-forward regexp &optional limit noerror count buffer
|
|
428
|
661 This function searches forward in the current buffer for a string of
|
|
|
662 text that is matched by the regular expression @var{regexp}. The
|
|
|
663 function skips over any amount of text that is not matched by
|
|
|
664 @var{regexp}, and leaves point at the end of the first match found.
|
|
|
665 It returns the new value of point.
|
|
|
666
|
|
|
667 If @var{limit} is non-@code{nil} (it must be a position in the current
|
|
|
668 buffer), then it is the upper bound to the search. No match extending
|
|
|
669 after that position is accepted.
|
|
|
670
|
|
|
671 What happens when the search fails depends on the value of
|
|
|
672 @var{noerror}. If @var{noerror} is @code{nil}, a @code{search-failed}
|
|
|
673 error is signaled. If @var{noerror} is @code{t},
|
|
|
674 @code{re-search-forward} does nothing and returns @code{nil}. If
|
|
|
675 @var{noerror} is neither @code{nil} nor @code{t}, then
|
|
|
676 @code{re-search-forward} moves point to @var{limit} (or the end of the
|
|
|
677 buffer) and returns @code{nil}.
|
|
|
678
|
|
444
|
679 If @var{count} is supplied (it must be a positive number), then the
|
|
428
|
680 search is repeated that many times (each time starting at the end of the
|
|
|
681 previous time's match). If these successive searches succeed, the
|
|
|
682 function succeeds, moving point and returning its new value. Otherwise
|
|
|
683 the search fails.
|
|
|
684
|
|
|
685 In the following example, point is initially before the @samp{T}.
|
|
|
686 Evaluating the search call moves point to the end of that line (between
|
|
|
687 the @samp{t} of @samp{hat} and the newline).
|
|
|
688
|
|
|
689 @example
|
|
|
690 @group
|
|
|
691 ---------- Buffer: foo ----------
|
|
|
692 I read "@point{}The cat in the hat
|
|
|
693 comes back" twice.
|
|
|
694 ---------- Buffer: foo ----------
|
|
|
695 @end group
|
|
|
696
|
|
|
697 @group
|
|
|
698 (re-search-forward "[a-z]+" nil t 5)
|
|
|
699 @result{} 27
|
|
|
700
|
|
|
701 ---------- Buffer: foo ----------
|
|
|
702 I read "The cat in the hat@point{}
|
|
|
703 comes back" twice.
|
|
|
704 ---------- Buffer: foo ----------
|
|
|
705 @end group
|
|
|
706 @end example
|
|
|
707 @end deffn
|
|
|
708
|
|
444
|
709 @deffn Command re-search-backward regexp &optional limit noerror count buffer
|
|
428
|
710 This function searches backward in the current buffer for a string of
|
|
|
711 text that is matched by the regular expression @var{regexp}, leaving
|
|
|
712 point at the beginning of the first text found.
|
|
|
713
|
|
|
714 This function is analogous to @code{re-search-forward}, but they are not
|
|
|
715 simple mirror images. @code{re-search-forward} finds the match whose
|
|
|
716 beginning is as close as possible to the starting point. If
|
|
|
717 @code{re-search-backward} were a perfect mirror image, it would find the
|
|
|
718 match whose end is as close as possible. However, in fact it finds the
|
|
|
719 match whose beginning is as close as possible. The reason is that
|
|
|
720 matching a regular expression at a given spot always works from
|
|
|
721 beginning to end, and starts at a specified beginning position.
|
|
|
722
|
|
|
723 A true mirror-image of @code{re-search-forward} would require a special
|
|
|
724 feature for matching regexps from end to beginning. It's not worth the
|
|
|
725 trouble of implementing that.
|
|
|
726 @end deffn
|
|
|
727
|
|
444
|
728 @defun string-match regexp string &optional start buffer
|
|
428
|
729 This function returns the index of the start of the first match for
|
|
|
730 the regular expression @var{regexp} in @var{string}, or @code{nil} if
|
|
|
731 there is no match. If @var{start} is non-@code{nil}, the search starts
|
|
|
732 at that index in @var{string}.
|
|
|
733
|
|
444
|
734
|
|
|
735 Optional arg @var{buffer} controls how case folding is done (according
|
|
|
736 to the value of @code{case-fold-search} in @var{buffer} and
|
|
|
737 @var{buffer}'s case tables) and defaults to the current buffer.
|
|
|
738
|
|
428
|
739 For example,
|
|
|
740
|
|
|
741 @example
|
|
|
742 @group
|
|
|
743 (string-match
|
|
|
744 "quick" "The quick brown fox jumped quickly.")
|
|
|
745 @result{} 4
|
|
|
746 @end group
|
|
|
747 @group
|
|
|
748 (string-match
|
|
|
749 "quick" "The quick brown fox jumped quickly." 8)
|
|
|
750 @result{} 27
|
|
|
751 @end group
|
|
|
752 @end example
|
|
|
753
|
|
|
754 @noindent
|
|
|
755 The index of the first character of the
|
|
|
756 string is 0, the index of the second character is 1, and so on.
|
|
|
757
|
|
|
758 After this function returns, the index of the first character beyond
|
|
|
759 the match is available as @code{(match-end 0)}. @xref{Match Data}.
|
|
|
760
|
|
|
761 @example
|
|
|
762 @group
|
|
|
763 (string-match
|
|
|
764 "quick" "The quick brown fox jumped quickly." 8)
|
|
|
765 @result{} 27
|
|
|
766 @end group
|
|
|
767
|
|
|
768 @group
|
|
|
769 (match-end 0)
|
|
|
770 @result{} 32
|
|
|
771 @end group
|
|
|
772 @end example
|
|
|
773 @end defun
|
|
|
774
|
|
|
775 @defun split-string string &optional pattern
|
|
|
776 This function splits @var{string} to substrings delimited by
|
|
|
777 @var{pattern}, and returns a list of substrings. If @var{pattern} is
|
|
|
778 omitted, it defaults to @samp{[ \f\t\n\r\v]+}, which means that it
|
|
|
779 splits @var{string} by white--space.
|
|
|
780
|
|
|
781 @example
|
|
|
782 @group
|
|
|
783 (split-string "foo bar")
|
|
|
784 @result{} ("foo" "bar")
|
|
|
785 @end group
|
|
|
786
|
|
|
787 @group
|
|
|
788 (split-string "something")
|
|
|
789 @result{} ("something")
|
|
|
790 @end group
|
|
|
791
|
|
|
792 @group
|
|
|
793 (split-string "a:b:c" ":")
|
|
|
794 @result{} ("a" "b" "c")
|
|
|
795 @end group
|
|
|
796
|
|
|
797 @group
|
|
|
798 (split-string ":a::b:c" ":")
|
|
|
799 @result{} ("" "a" "" "b" "c")
|
|
|
800 @end group
|
|
|
801 @end example
|
|
|
802 @end defun
|
|
|
803
|
|
|
804 @defun split-path path
|
|
|
805 This function splits a search path into a list of strings. The path
|
|
|
806 components are separated with the characters specified with
|
|
|
807 @code{path-separator}. Under Unix, @code{path-separator} will normally
|
|
|
808 be @samp{:}, while under Windows, it will be @samp{;}.
|
|
|
809 @end defun
|
|
|
810
|
|
444
|
811 @defun looking-at regexp &optional buffer
|
|
428
|
812 This function determines whether the text in the current buffer directly
|
|
|
813 following point matches the regular expression @var{regexp}. ``Directly
|
|
|
814 following'' means precisely that: the search is ``anchored'' and it can
|
|
|
815 succeed only starting with the first character following point. The
|
|
|
816 result is @code{t} if so, @code{nil} otherwise.
|
|
|
817
|
|
|
818 This function does not move point, but it updates the match data, which
|
|
|
819 you can access using @code{match-beginning} and @code{match-end}.
|
|
|
820 @xref{Match Data}.
|
|
|
821
|
|
|
822 In this example, point is located directly before the @samp{T}. If it
|
|
|
823 were anywhere else, the result would be @code{nil}.
|
|
|
824
|
|
|
825 @example
|
|
|
826 @group
|
|
|
827 ---------- Buffer: foo ----------
|
|
|
828 I read "@point{}The cat in the hat
|
|
|
829 comes back" twice.
|
|
|
830 ---------- Buffer: foo ----------
|
|
|
831
|
|
|
832 (looking-at "The cat in the hat$")
|
|
|
833 @result{} t
|
|
|
834 @end group
|
|
|
835 @end example
|
|
|
836 @end defun
|
|
|
837
|
|
|
838 @node POSIX Regexps
|
|
|
839 @section POSIX Regular Expression Searching
|
|
|
840
|
|
|
841 The usual regular expression functions do backtracking when necessary
|
|
|
842 to handle the @samp{\|} and repetition constructs, but they continue
|
|
|
843 this only until they find @emph{some} match. Then they succeed and
|
|
|
844 report the first match found.
|
|
|
845
|
|
|
846 This section describes alternative search functions which perform the
|
|
|
847 full backtracking specified by the POSIX standard for regular expression
|
|
|
848 matching. They continue backtracking until they have tried all
|
|
|
849 possibilities and found all matches, so they can report the longest
|
|
|
850 match, as required by POSIX. This is much slower, so use these
|
|
|
851 functions only when you really need the longest match.
|
|
|
852
|
|
|
853 In Emacs versions prior to 19.29, these functions did not exist, and
|
|
|
854 the functions described above implemented full POSIX backtracking.
|
|
|
855
|
|
444
|
856 @deffn Command posix-search-forward regexp &optional limit noerror count buffer
|
|
428
|
857 This is like @code{re-search-forward} except that it performs the full
|
|
|
858 backtracking specified by the POSIX standard for regular expression
|
|
|
859 matching.
|
|
444
|
860 @end deffn
|
|
428
|
861
|
|
444
|
862 @deffn Command posix-search-backward regexp &optional limit noerror count buffer
|
|
428
|
863 This is like @code{re-search-backward} except that it performs the full
|
|
|
864 backtracking specified by the POSIX standard for regular expression
|
|
|
865 matching.
|
|
444
|
866 @end deffn
|
|
428
|
867
|
|
444
|
868 @defun posix-looking-at regexp &optional buffer
|
|
428
|
869 This is like @code{looking-at} except that it performs the full
|
|
|
870 backtracking specified by the POSIX standard for regular expression
|
|
|
871 matching.
|
|
|
872 @end defun
|
|
|
873
|
|
444
|
874 @defun posix-string-match regexp string &optional start buffer
|
|
428
|
875 This is like @code{string-match} except that it performs the full
|
|
|
876 backtracking specified by the POSIX standard for regular expression
|
|
|
877 matching.
|
|
444
|
878
|
|
|
879 Optional arg @var{buffer} controls how case folding is done (according
|
|
|
880 to the value of @code{case-fold-search} in @var{buffer} and
|
|
|
881 @var{buffer}'s case tables) and defaults to the current buffer.
|
|
428
|
882 @end defun
|
|
|
883
|
|
|
884 @ignore
|
|
|
885 @deffn Command delete-matching-lines regexp
|
|
|
886 This function is identical to @code{delete-non-matching-lines}, save
|
|
|
887 that it deletes what @code{delete-non-matching-lines} keeps.
|
|
|
888
|
|
|
889 In the example below, point is located on the first line of text.
|
|
|
890
|
|
|
891 @example
|
|
|
892 @group
|
|
|
893 ---------- Buffer: foo ----------
|
|
|
894 We hold these truths
|
|
|
895 to be self-evident,
|
|
|
896 that all men are created
|
|
|
897 equal, and that they are
|
|
|
898 ---------- Buffer: foo ----------
|
|
|
899 @end group
|
|
|
900
|
|
|
901 @group
|
|
|
902 (delete-matching-lines "the")
|
|
|
903 @result{} nil
|
|
|
904
|
|
|
905 ---------- Buffer: foo ----------
|
|
|
906 to be self-evident,
|
|
|
907 that all men are created
|
|
|
908 ---------- Buffer: foo ----------
|
|
|
909 @end group
|
|
|
910 @end example
|
|
|
911 @end deffn
|
|
|
912
|
|
|
913 @deffn Command flush-lines regexp
|
|
444
|
914 This function is an alias of @code{delete-matching-lines}.
|
|
428
|
915 @end deffn
|
|
|
916
|
|
444
|
917 @deffn Command delete-non-matching-lines regexp
|
|
428
|
918 This function deletes all lines following point which don't
|
|
|
919 contain a match for the regular expression @var{regexp}.
|
|
444
|
920 @end deffn
|
|
428
|
921
|
|
|
922 @deffn Command keep-lines regexp
|
|
|
923 This function is the same as @code{delete-non-matching-lines}.
|
|
|
924 @end deffn
|
|
|
925
|
|
444
|
926 @deffn Command count-matches regexp
|
|
428
|
927 This function counts the number of matches for @var{regexp} there are in
|
|
|
928 the current buffer following point. It prints this number in
|
|
|
929 the echo area, returning the string printed.
|
|
|
930 @end deffn
|
|
|
931
|
|
444
|
932 @deffn Command how-many regexp
|
|
|
933 This function is an alias of @code{count-matches}.
|
|
428
|
934 @end deffn
|
|
|
935
|
|
444
|
936 @deffn Command list-matching-lines regexp &optional nlines
|
|
428
|
937 This function is a synonym of @code{occur}.
|
|
|
938 Show all lines following point containing a match for @var{regexp}.
|
|
|
939 Display each line with @var{nlines} lines before and after,
|
|
|
940 or @code{-}@var{nlines} before if @var{nlines} is negative.
|
|
|
941 @var{nlines} defaults to @code{list-matching-lines-default-context-lines}.
|
|
|
942 Interactively it is the prefix arg.
|
|
|
943
|
|
|
944 The lines are shown in a buffer named @samp{*Occur*}.
|
|
|
945 It serves as a menu to find any of the occurrences in this buffer.
|
|
|
946 @kbd{C-h m} (@code{describe-mode} in that buffer gives help.
|
|
|
947 @end deffn
|
|
|
948
|
|
|
949 @defopt list-matching-lines-default-context-lines
|
|
|
950 Default value is 0.
|
|
|
951 Default number of context lines to include around a @code{list-matching-lines}
|
|
|
952 match. A negative number means to include that many lines before the match.
|
|
|
953 A positive number means to include that many lines both before and after.
|
|
|
954 @end defopt
|
|
|
955 @end ignore
|
|
|
956
|
|
|
957 @node Search and Replace
|
|
|
958 @section Search and Replace
|
|
|
959 @cindex replacement
|
|
|
960
|
|
|
961 @defun perform-replace from-string replacements query-flag regexp-flag delimited-flag &optional repeat-count map
|
|
|
962 This function is the guts of @code{query-replace} and related commands.
|
|
|
963 It searches for occurrences of @var{from-string} and replaces some or
|
|
|
964 all of them. If @var{query-flag} is @code{nil}, it replaces all
|
|
|
965 occurrences; otherwise, it asks the user what to do about each one.
|
|
|
966
|
|
|
967 If @var{regexp-flag} is non-@code{nil}, then @var{from-string} is
|
|
|
968 considered a regular expression; otherwise, it must match literally. If
|
|
|
969 @var{delimited-flag} is non-@code{nil}, then only replacements
|
|
|
970 surrounded by word boundaries are considered.
|
|
|
971
|
|
|
972 The argument @var{replacements} specifies what to replace occurrences
|
|
|
973 with. If it is a string, that string is used. It can also be a list of
|
|
|
974 strings, to be used in cyclic order.
|
|
|
975
|
|
|
976 If @var{repeat-count} is non-@code{nil}, it should be an integer. Then
|
|
|
977 it specifies how many times to use each of the strings in the
|
|
|
978 @var{replacements} list before advancing cyclicly to the next one.
|
|
|
979
|
|
|
980 Normally, the keymap @code{query-replace-map} defines the possible user
|
|
|
981 responses for queries. The argument @var{map}, if non-@code{nil}, is a
|
|
|
982 keymap to use instead of @code{query-replace-map}.
|
|
|
983 @end defun
|
|
|
984
|
|
|
985 @defvar query-replace-map
|
|
|
986 This variable holds a special keymap that defines the valid user
|
|
|
987 responses for @code{query-replace} and related functions, as well as
|
|
|
988 @code{y-or-n-p} and @code{map-y-or-n-p}. It is unusual in two ways:
|
|
|
989
|
|
|
990 @itemize @bullet
|
|
|
991 @item
|
|
|
992 The ``key bindings'' are not commands, just symbols that are meaningful
|
|
|
993 to the functions that use this map.
|
|
|
994
|
|
|
995 @item
|
|
|
996 Prefix keys are not supported; each key binding must be for a single event
|
|
|
997 key sequence. This is because the functions don't use read key sequence to
|
|
|
998 get the input; instead, they read a single event and look it up ``by hand.''
|
|
|
999 @end itemize
|
|
|
1000 @end defvar
|
|
|
1001
|
|
|
1002 Here are the meaningful ``bindings'' for @code{query-replace-map}.
|
|
|
1003 Several of them are meaningful only for @code{query-replace} and
|
|
|
1004 friends.
|
|
|
1005
|
|
|
1006 @table @code
|
|
|
1007 @item act
|
|
|
1008 Do take the action being considered---in other words, ``yes.''
|
|
|
1009
|
|
|
1010 @item skip
|
|
|
1011 Do not take action for this question---in other words, ``no.''
|
|
|
1012
|
|
|
1013 @item exit
|
|
|
1014 Answer this question ``no,'' and give up on the entire series of
|
|
|
1015 questions, assuming that the answers will be ``no.''
|
|
|
1016
|
|
|
1017 @item act-and-exit
|
|
|
1018 Answer this question ``yes,'' and give up on the entire series of
|
|
|
1019 questions, assuming that subsequent answers will be ``no.''
|
|
|
1020
|
|
|
1021 @item act-and-show
|
|
|
1022 Answer this question ``yes,'' but show the results---don't advance yet
|
|
|
1023 to the next question.
|
|
|
1024
|
|
|
1025 @item automatic
|
|
|
1026 Answer this question and all subsequent questions in the series with
|
|
|
1027 ``yes,'' without further user interaction.
|
|
|
1028
|
|
|
1029 @item backup
|
|
|
1030 Move back to the previous place that a question was asked about.
|
|
|
1031
|
|
|
1032 @item edit
|
|
|
1033 Enter a recursive edit to deal with this question---instead of any
|
|
|
1034 other action that would normally be taken.
|
|
|
1035
|
|
|
1036 @item delete-and-edit
|
|
|
1037 Delete the text being considered, then enter a recursive edit to replace
|
|
|
1038 it.
|
|
|
1039
|
|
|
1040 @item recenter
|
|
|
1041 Redisplay and center the window, then ask the same question again.
|
|
|
1042
|
|
|
1043 @item quit
|
|
|
1044 Perform a quit right away. Only @code{y-or-n-p} and related functions
|
|
|
1045 use this answer.
|
|
|
1046
|
|
|
1047 @item help
|
|
|
1048 Display some help, then ask again.
|
|
|
1049 @end table
|
|
|
1050
|
|
|
1051 @node Match Data
|
|
|
1052 @section The Match Data
|
|
|
1053 @cindex match data
|
|
|
1054
|
|
|
1055 XEmacs keeps track of the positions of the start and end of segments of
|
|
|
1056 text found during a regular expression search. This means, for example,
|
|
|
1057 that you can search for a complex pattern, such as a date in an Rmail
|
|
|
1058 message, and then extract parts of the match under control of the
|
|
|
1059 pattern.
|
|
|
1060
|
|
|
1061 Because the match data normally describe the most recent search only,
|
|
|
1062 you must be careful not to do another search inadvertently between the
|
|
|
1063 search you wish to refer back to and the use of the match data. If you
|
|
|
1064 can't avoid another intervening search, you must save and restore the
|
|
|
1065 match data around it, to prevent it from being overwritten.
|
|
|
1066
|
|
|
1067 @menu
|
|
|
1068 * Simple Match Data:: Accessing single items of match data,
|
|
|
1069 such as where a particular subexpression started.
|
|
|
1070 * Replacing Match:: Replacing a substring that was matched.
|
|
|
1071 * Entire Match Data:: Accessing the entire match data at once, as a list.
|
|
|
1072 * Saving Match Data:: Saving and restoring the match data.
|
|
|
1073 @end menu
|
|
|
1074
|
|
|
1075 @node Simple Match Data
|
|
|
1076 @subsection Simple Match Data Access
|
|
|
1077
|
|
|
1078 This section explains how to use the match data to find out what was
|
|
|
1079 matched by the last search or match operation.
|
|
|
1080
|
|
|
1081 You can ask about the entire matching text, or about a particular
|
|
|
1082 parenthetical subexpression of a regular expression. The @var{count}
|
|
|
1083 argument in the functions below specifies which. If @var{count} is
|
|
|
1084 zero, you are asking about the entire match. If @var{count} is
|
|
|
1085 positive, it specifies which subexpression you want.
|
|
|
1086
|
|
|
1087 Recall that the subexpressions of a regular expression are those
|
|
|
1088 expressions grouped with escaped parentheses, @samp{\(@dots{}\)}. The
|
|
|
1089 @var{count}th subexpression is found by counting occurrences of
|
|
|
1090 @samp{\(} from the beginning of the whole regular expression. The first
|
|
|
1091 subexpression is numbered 1, the second 2, and so on. Only regular
|
|
|
1092 expressions can have subexpressions---after a simple string search, the
|
|
|
1093 only information available is about the entire match.
|
|
|
1094
|
|
|
1095 @defun match-string count &optional in-string
|
|
|
1096 This function returns, as a string, the text matched in the last search
|
|
|
1097 or match operation. It returns the entire text if @var{count} is zero,
|
|
|
1098 or just the portion corresponding to the @var{count}th parenthetical
|
|
|
1099 subexpression, if @var{count} is positive. If @var{count} is out of
|
|
|
1100 range, or if that subexpression didn't match anything, the value is
|
|
|
1101 @code{nil}.
|
|
|
1102
|
|
|
1103 If the last such operation was done against a string with
|
|
|
1104 @code{string-match}, then you should pass the same string as the
|
|
|
1105 argument @var{in-string}. Otherwise, after a buffer search or match,
|
|
|
1106 you should omit @var{in-string} or pass @code{nil} for it; but you
|
|
|
1107 should make sure that the current buffer when you call
|
|
|
1108 @code{match-string} is the one in which you did the searching or
|
|
|
1109 matching.
|
|
|
1110 @end defun
|
|
|
1111
|
|
|
1112 @defun match-beginning count
|
|
|
1113 This function returns the position of the start of text matched by the
|
|
|
1114 last regular expression searched for, or a subexpression of it.
|
|
|
1115
|
|
|
1116 If @var{count} is zero, then the value is the position of the start of
|
|
|
1117 the entire match. Otherwise, @var{count} specifies a subexpression in
|
|
|
1118 the regular expression, and the value of the function is the starting
|
|
|
1119 position of the match for that subexpression.
|
|
|
1120
|
|
|
1121 The value is @code{nil} for a subexpression inside a @samp{\|}
|
|
|
1122 alternative that wasn't used in the match.
|
|
|
1123 @end defun
|
|
|
1124
|
|
|
1125 @defun match-end count
|
|
|
1126 This function is like @code{match-beginning} except that it returns the
|
|
|
1127 position of the end of the match, rather than the position of the
|
|
|
1128 beginning.
|
|
|
1129 @end defun
|
|
|
1130
|
|
|
1131 Here is an example of using the match data, with a comment showing the
|
|
|
1132 positions within the text:
|
|
|
1133
|
|
|
1134 @example
|
|
|
1135 @group
|
|
|
1136 (string-match "\\(qu\\)\\(ick\\)"
|
|
|
1137 "The quick fox jumped quickly.")
|
|
444
|
1138 ;0123456789
|
|
428
|
1139 @result{} 4
|
|
|
1140 @end group
|
|
|
1141
|
|
|
1142 @group
|
|
|
1143 (match-string 0 "The quick fox jumped quickly.")
|
|
|
1144 @result{} "quick"
|
|
|
1145 (match-string 1 "The quick fox jumped quickly.")
|
|
|
1146 @result{} "qu"
|
|
|
1147 (match-string 2 "The quick fox jumped quickly.")
|
|
|
1148 @result{} "ick"
|
|
|
1149 @end group
|
|
|
1150
|
|
|
1151 @group
|
|
|
1152 (match-beginning 1) ; @r{The beginning of the match}
|
|
|
1153 @result{} 4 ; @r{with @samp{qu} is at index 4.}
|
|
|
1154 @end group
|
|
|
1155
|
|
|
1156 @group
|
|
|
1157 (match-beginning 2) ; @r{The beginning of the match}
|
|
|
1158 @result{} 6 ; @r{with @samp{ick} is at index 6.}
|
|
|
1159 @end group
|
|
|
1160
|
|
|
1161 @group
|
|
|
1162 (match-end 1) ; @r{The end of the match}
|
|
|
1163 @result{} 6 ; @r{with @samp{qu} is at index 6.}
|
|
|
1164
|
|
|
1165 (match-end 2) ; @r{The end of the match}
|
|
|
1166 @result{} 9 ; @r{with @samp{ick} is at index 9.}
|
|
|
1167 @end group
|
|
|
1168 @end example
|
|
|
1169
|
|
|
1170 Here is another example. Point is initially located at the beginning
|
|
|
1171 of the line. Searching moves point to between the space and the word
|
|
|
1172 @samp{in}. The beginning of the entire match is at the 9th character of
|
|
|
1173 the buffer (@samp{T}), and the beginning of the match for the first
|
|
|
1174 subexpression is at the 13th character (@samp{c}).
|
|
|
1175
|
|
|
1176 @example
|
|
|
1177 @group
|
|
|
1178 (list
|
|
|
1179 (re-search-forward "The \\(cat \\)")
|
|
|
1180 (match-beginning 0)
|
|
|
1181 (match-beginning 1))
|
|
|
1182 @result{} (9 9 13)
|
|
|
1183 @end group
|
|
|
1184
|
|
|
1185 @group
|
|
|
1186 ---------- Buffer: foo ----------
|
|
|
1187 I read "The cat @point{}in the hat comes back" twice.
|
|
|
1188 ^ ^
|
|
|
1189 9 13
|
|
|
1190 ---------- Buffer: foo ----------
|
|
|
1191 @end group
|
|
|
1192 @end example
|
|
|
1193
|
|
|
1194 @noindent
|
|
|
1195 (In this case, the index returned is a buffer position; the first
|
|
|
1196 character of the buffer counts as 1.)
|
|
|
1197
|
|
|
1198 @node Replacing Match
|
|
|
1199 @subsection Replacing the Text That Matched
|
|
|
1200
|
|
|
1201 This function replaces the text matched by the last search with
|
|
|
1202 @var{replacement}.
|
|
|
1203
|
|
|
1204 @cindex case in replacements
|
|
444
|
1205 @defun replace-match replacement &optional fixedcase literal string strbuffer
|
|
428
|
1206 This function replaces the text in the buffer (or in @var{string}) that
|
|
|
1207 was matched by the last search. It replaces that text with
|
|
|
1208 @var{replacement}.
|
|
|
1209
|
|
|
1210 If you did the last search in a buffer, you should specify @code{nil}
|
|
|
1211 for @var{string}. Then @code{replace-match} does the replacement by
|
|
|
1212 editing the buffer; it leaves point at the end of the replacement text,
|
|
|
1213 and returns @code{t}.
|
|
|
1214
|
|
|
1215 If you did the search in a string, pass the same string as @var{string}.
|
|
|
1216 Then @code{replace-match} does the replacement by constructing and
|
|
|
1217 returning a new string.
|
|
|
1218
|
|
444
|
1219 If the fourth argument @var{string} is a string, fifth argument
|
|
|
1220 @var{strbuffer} specifies the buffer to be used for syntax-table and
|
|
|
1221 case-table lookup and defaults to the current buffer. When @var{string}
|
|
|
1222 is not a string, the buffer that the match occurred in has automatically
|
|
|
1223 been remembered and you do not need to specify it.
|
|
|
1224
|
|
428
|
1225 If @var{fixedcase} is non-@code{nil}, then the case of the replacement
|
|
|
1226 text is not changed; otherwise, the replacement text is converted to a
|
|
|
1227 different case depending upon the capitalization of the text to be
|
|
|
1228 replaced. If the original text is all upper case, the replacement text
|
|
|
1229 is converted to upper case. If the first word of the original text is
|
|
|
1230 capitalized, then the first word of the replacement text is capitalized.
|
|
|
1231 If the original text contains just one word, and that word is a capital
|
|
|
1232 letter, @code{replace-match} considers this a capitalized first word
|
|
|
1233 rather than all upper case.
|
|
|
1234
|
|
|
1235 If @code{case-replace} is @code{nil}, then case conversion is not done,
|
|
444
|
1236 regardless of the value of @var{fixedcase}. @xref{Searching and Case}.
|
|
428
|
1237
|
|
|
1238 If @var{literal} is non-@code{nil}, then @var{replacement} is inserted
|
|
|
1239 exactly as it is, the only alterations being case changes as needed.
|
|
|
1240 If it is @code{nil} (the default), then the character @samp{\} is treated
|
|
|
1241 specially. If a @samp{\} appears in @var{replacement}, then it must be
|
|
|
1242 part of one of the following sequences:
|
|
|
1243
|
|
|
1244 @table @asis
|
|
|
1245 @item @samp{\&}
|
|
|
1246 @cindex @samp{&} in replacement
|
|
|
1247 @samp{\&} stands for the entire text being replaced.
|
|
|
1248
|
|
|
1249 @item @samp{\@var{n}}
|
|
|
1250 @cindex @samp{\@var{n}} in replacement
|
|
|
1251 @samp{\@var{n}}, where @var{n} is a digit, stands for the text that
|
|
|
1252 matched the @var{n}th subexpression in the original regexp.
|
|
|
1253 Subexpressions are those expressions grouped inside @samp{\(@dots{}\)}.
|
|
|
1254
|
|
|
1255 @item @samp{\\}
|
|
|
1256 @cindex @samp{\} in replacement
|
|
|
1257 @samp{\\} stands for a single @samp{\} in the replacement text.
|
|
|
1258 @end table
|
|
|
1259 @end defun
|
|
|
1260
|
|
|
1261 @node Entire Match Data
|
|
|
1262 @subsection Accessing the Entire Match Data
|
|
|
1263
|
|
|
1264 The functions @code{match-data} and @code{set-match-data} read or
|
|
|
1265 write the entire match data, all at once.
|
|
|
1266
|
|
444
|
1267 @defun match-data &optional integers reuse
|
|
428
|
1268 This function returns a newly constructed list containing all the
|
|
|
1269 information on what text the last search matched. Element zero is the
|
|
|
1270 position of the beginning of the match for the whole expression; element
|
|
|
1271 one is the position of the end of the match for the expression. The
|
|
|
1272 next two elements are the positions of the beginning and end of the
|
|
|
1273 match for the first subexpression, and so on. In general, element
|
|
|
1274 @ifinfo
|
|
|
1275 number 2@var{n}
|
|
|
1276 @end ifinfo
|
|
|
1277 @tex
|
|
|
1278 number {\mathsurround=0pt $2n$}
|
|
|
1279 @end tex
|
|
|
1280 corresponds to @code{(match-beginning @var{n})}; and
|
|
|
1281 element
|
|
|
1282 @ifinfo
|
|
|
1283 number 2@var{n} + 1
|
|
|
1284 @end ifinfo
|
|
|
1285 @tex
|
|
|
1286 number {\mathsurround=0pt $2n+1$}
|
|
|
1287 @end tex
|
|
|
1288 corresponds to @code{(match-end @var{n})}.
|
|
|
1289
|
|
|
1290 All the elements are markers or @code{nil} if matching was done on a
|
|
|
1291 buffer, and all are integers or @code{nil} if matching was done on a
|
|
444
|
1292 string with @code{string-match}. However, if the optional first
|
|
|
1293 argument @var{integers} is non-@code{nil}, always use integers (rather
|
|
|
1294 than markers) to represent buffer positions.
|
|
|
1295
|
|
|
1296 If the optional second argument @var{reuse} is a list, reuse it as part
|
|
|
1297 of the value. If @var{reuse} is long enough to hold all the values, and if
|
|
|
1298 @var{integers} is non-@code{nil}, no new lisp objects are created.
|
|
428
|
1299
|
|
|
1300 As always, there must be no possibility of intervening searches between
|
|
|
1301 the call to a search function and the call to @code{match-data} that is
|
|
|
1302 intended to access the match data for that search.
|
|
|
1303
|
|
|
1304 @example
|
|
|
1305 @group
|
|
|
1306 (match-data)
|
|
|
1307 @result{} (#<marker at 9 in foo>
|
|
|
1308 #<marker at 17 in foo>
|
|
|
1309 #<marker at 13 in foo>
|
|
|
1310 #<marker at 17 in foo>)
|
|
|
1311 @end group
|
|
|
1312 @end example
|
|
|
1313 @end defun
|
|
|
1314
|
|
|
1315 @defun set-match-data match-list
|
|
|
1316 This function sets the match data from the elements of @var{match-list},
|
|
|
1317 which should be a list that was the value of a previous call to
|
|
|
1318 @code{match-data}.
|
|
|
1319
|
|
|
1320 If @var{match-list} refers to a buffer that doesn't exist, you don't get
|
|
|
1321 an error; that sets the match data in a meaningless but harmless way.
|
|
|
1322
|
|
|
1323 @findex store-match-data
|
|
|
1324 @code{store-match-data} is an alias for @code{set-match-data}.
|
|
|
1325 @end defun
|
|
|
1326
|
|
|
1327 @node Saving Match Data
|
|
|
1328 @subsection Saving and Restoring the Match Data
|
|
|
1329
|
|
|
1330 When you call a function that may do a search, you may need to save
|
|
|
1331 and restore the match data around that call, if you want to preserve the
|
|
|
1332 match data from an earlier search for later use. Here is an example
|
|
|
1333 that shows the problem that arises if you fail to save the match data:
|
|
|
1334
|
|
|
1335 @example
|
|
|
1336 @group
|
|
|
1337 (re-search-forward "The \\(cat \\)")
|
|
|
1338 @result{} 48
|
|
|
1339 (foo) ; @r{Perhaps @code{foo} does}
|
|
|
1340 ; @r{more searching.}
|
|
|
1341 (match-end 0)
|
|
|
1342 @result{} 61 ; @r{Unexpected result---not 48!}
|
|
|
1343 @end group
|
|
|
1344 @end example
|
|
|
1345
|
|
|
1346 You can save and restore the match data with @code{save-match-data}:
|
|
|
1347
|
|
444
|
1348 @defspec save-match-data body@dots{}
|
|
428
|
1349 This special form executes @var{body}, saving and restoring the match
|
|
|
1350 data around it.
|
|
444
|
1351 @end defspec
|
|
428
|
1352
|
|
|
1353 You can use @code{set-match-data} together with @code{match-data} to
|
|
|
1354 imitate the effect of the special form @code{save-match-data}. This is
|
|
|
1355 useful for writing code that can run in Emacs 18. Here is how:
|
|
|
1356
|
|
|
1357 @example
|
|
|
1358 @group
|
|
|
1359 (let ((data (match-data)))
|
|
|
1360 (unwind-protect
|
|
|
1361 @dots{} ; @r{May change the original match data.}
|
|
|
1362 (set-match-data data)))
|
|
|
1363 @end group
|
|
|
1364 @end example
|
|
|
1365
|
|
|
1366 Emacs automatically saves and restores the match data when it runs
|
|
|
1367 process filter functions (@pxref{Filter Functions}) and process
|
|
|
1368 sentinels (@pxref{Sentinels}).
|
|
|
1369
|
|
|
1370 @ignore
|
|
|
1371 Here is a function which restores the match data provided the buffer
|
|
|
1372 associated with it still exists.
|
|
|
1373
|
|
|
1374 @smallexample
|
|
|
1375 @group
|
|
|
1376 (defun restore-match-data (data)
|
|
|
1377 @c It is incorrect to split the first line of a doc string.
|
|
|
1378 @c If there's a problem here, it should be solved in some other way.
|
|
|
1379 "Restore the match data DATA unless the buffer is missing."
|
|
|
1380 (catch 'foo
|
|
|
1381 (let ((d data))
|
|
|
1382 @end group
|
|
|
1383 (while d
|
|
|
1384 (and (car d)
|
|
|
1385 (null (marker-buffer (car d)))
|
|
|
1386 @group
|
|
|
1387 ;; @file{match-data} @r{buffer is deleted.}
|
|
|
1388 (throw 'foo nil))
|
|
|
1389 (setq d (cdr d)))
|
|
|
1390 (set-match-data data))))
|
|
|
1391 @end group
|
|
|
1392 @end smallexample
|
|
|
1393 @end ignore
|
|
|
1394
|
|
|
1395 @node Searching and Case
|
|
|
1396 @section Searching and Case
|
|
|
1397 @cindex searching and case
|
|
|
1398
|
|
|
1399 By default, searches in Emacs ignore the case of the text they are
|
|
|
1400 searching through; if you specify searching for @samp{FOO}, then
|
|
|
1401 @samp{Foo} or @samp{foo} is also considered a match. Regexps, and in
|
|
|
1402 particular character sets, are included: thus, @samp{[aB]} would match
|
|
|
1403 @samp{a} or @samp{A} or @samp{b} or @samp{B}.
|
|
|
1404
|
|
|
1405 If you do not want this feature, set the variable
|
|
|
1406 @code{case-fold-search} to @code{nil}. Then all letters must match
|
|
|
1407 exactly, including case. This is a buffer-local variable; altering the
|
|
|
1408 variable affects only the current buffer. (@xref{Intro to
|
|
|
1409 Buffer-Local}.) Alternatively, you may change the value of
|
|
|
1410 @code{default-case-fold-search}, which is the default value of
|
|
|
1411 @code{case-fold-search} for buffers that do not override it.
|
|
|
1412
|
|
|
1413 Note that the user-level incremental search feature handles case
|
|
|
1414 distinctions differently. When given a lower case letter, it looks for
|
|
|
1415 a match of either case, but when given an upper case letter, it looks
|
|
|
1416 for an upper case letter only. But this has nothing to do with the
|
|
|
1417 searching functions Lisp functions use.
|
|
|
1418
|
|
|
1419 @defopt case-replace
|
|
|
1420 This variable determines whether the replacement functions should
|
|
|
1421 preserve case. If the variable is @code{nil}, that means to use the
|
|
|
1422 replacement text verbatim. A non-@code{nil} value means to convert the
|
|
|
1423 case of the replacement text according to the text being replaced.
|
|
|
1424
|
|
|
1425 The function @code{replace-match} is where this variable actually has
|
|
|
1426 its effect. @xref{Replacing Match}.
|
|
|
1427 @end defopt
|
|
|
1428
|
|
|
1429 @defopt case-fold-search
|
|
|
1430 This buffer-local variable determines whether searches should ignore
|
|
|
1431 case. If the variable is @code{nil} they do not ignore case; otherwise
|
|
|
1432 they do ignore case.
|
|
|
1433 @end defopt
|
|
|
1434
|
|
|
1435 @defvar default-case-fold-search
|
|
|
1436 The value of this variable is the default value for
|
|
|
1437 @code{case-fold-search} in buffers that do not override it. This is the
|
|
|
1438 same as @code{(default-value 'case-fold-search)}.
|
|
|
1439 @end defvar
|
|
|
1440
|
|
|
1441 @node Standard Regexps
|
|
|
1442 @section Standard Regular Expressions Used in Editing
|
|
|
1443 @cindex regexps used standardly in editing
|
|
|
1444 @cindex standard regexps used in editing
|
|
|
1445
|
|
|
1446 This section describes some variables that hold regular expressions
|
|
|
1447 used for certain purposes in editing:
|
|
|
1448
|
|
|
1449 @defvar page-delimiter
|
|
|
1450 This is the regexp describing line-beginnings that separate pages. The
|
|
|
1451 default value is @code{"^\014"} (i.e., @code{"^^L"} or @code{"^\C-l"});
|
|
|
1452 this matches a line that starts with a formfeed character.
|
|
|
1453 @end defvar
|
|
|
1454
|
|
|
1455 The following two regular expressions should @emph{not} assume the
|
|
|
1456 match always starts at the beginning of a line; they should not use
|
|
|
1457 @samp{^} to anchor the match. Most often, the paragraph commands do
|
|
|
1458 check for a match only at the beginning of a line, which means that
|
|
|
1459 @samp{^} would be superfluous. When there is a nonzero left margin,
|
|
|
1460 they accept matches that start after the left margin. In that case, a
|
|
|
1461 @samp{^} would be incorrect. However, a @samp{^} is harmless in modes
|
|
|
1462 where a left margin is never used.
|
|
|
1463
|
|
|
1464 @defvar paragraph-separate
|
|
|
1465 This is the regular expression for recognizing the beginning of a line
|
|
|
1466 that separates paragraphs. (If you change this, you may have to
|
|
|
1467 change @code{paragraph-start} also.) The default value is
|
|
|
1468 @w{@code{"[@ \t\f]*$"}}, which matches a line that consists entirely of
|
|
|
1469 spaces, tabs, and form feeds (after its left margin).
|
|
|
1470 @end defvar
|
|
|
1471
|
|
|
1472 @defvar paragraph-start
|
|
|
1473 This is the regular expression for recognizing the beginning of a line
|
|
|
1474 that starts @emph{or} separates paragraphs. The default value is
|
|
|
1475 @w{@code{"[@ \t\n\f]"}}, which matches a line starting with a space, tab,
|
|
|
1476 newline, or form feed (after its left margin).
|
|
|
1477 @end defvar
|
|
|
1478
|
|
|
1479 @defvar sentence-end
|
|
|
1480 This is the regular expression describing the end of a sentence. (All
|
|
|
1481 paragraph boundaries also end sentences, regardless.) The default value
|
|
|
1482 is:
|
|
|
1483
|
|
|
1484 @example
|
|
|
1485 "[.?!][]\"')@}]*\\($\\| $\\|\t\\| \\)[ \t\n]*"
|
|
|
1486 @end example
|
|
|
1487
|
|
|
1488 This means a period, question mark or exclamation mark, followed
|
|
|
1489 optionally by a closing parenthetical character, followed by tabs,
|
|
|
1490 spaces or new lines.
|
|
|
1491
|
|
|
1492 For a detailed explanation of this regular expression, see @ref{Regexp
|
|
|
1493 Example}.
|
|
|
1494 @end defvar
|
