Mercurial > emacs
annotate man/search.texi @ 28447:ec699636f83a
(Other Repeating Search): Mention tags-based search.
author | Dave Love <fx@gnu.org> |
---|---|
date | Fri, 31 Mar 2000 17:13:44 +0000 |
parents | 60b77d9b88ec |
children | 65af0f27a892 |
rev | line source |
---|---|
25829 | 1 @c This is part of the Emacs manual. |
28126 | 2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 97, 2000 |
3 @c Free Software Foundation, Inc. | |
25829 | 4 @c See file emacs.texi for copying conditions. |
5 @node Search, Fixit, Display, Top | |
6 @chapter Searching and Replacement | |
7 @cindex searching | |
8 @cindex finding strings within text | |
9 | |
10 Like other editors, Emacs has commands for searching for occurrences of | |
11 a string. The principal search command is unusual in that it is | |
12 @dfn{incremental}; it begins to search before you have finished typing the | |
13 search string. There are also nonincremental search commands more like | |
14 those of other editors. | |
15 | |
16 Besides the usual @code{replace-string} command that finds all | |
17 occurrences of one string and replaces them with another, Emacs has a fancy | |
18 replacement command called @code{query-replace} which asks interactively | |
19 which occurrences to replace. | |
20 | |
21 @menu | |
22 * Incremental Search:: Search happens as you type the string. | |
23 * Nonincremental Search:: Specify entire string and then search. | |
24 * Word Search:: Search for sequence of words. | |
25 * Regexp Search:: Search for match for a regexp. | |
26 * Regexps:: Syntax of regular expressions. | |
27 * Search Case:: To ignore case while searching, or not. | |
28 * Replace:: Search, and replace some or all matches. | |
29 * Other Repeating Search:: Operating on all matches for some regexp. | |
30 @end menu | |
31 | |
32 @node Incremental Search, Nonincremental Search, Search, Search | |
33 @section Incremental Search | |
34 | |
35 @cindex incremental search | |
36 An incremental search begins searching as soon as you type the first | |
37 character of the search string. As you type in the search string, Emacs | |
38 shows you where the string (as you have typed it so far) would be | |
39 found. When you have typed enough characters to identify the place you | |
40 want, you can stop. Depending on what you plan to do next, you may or | |
41 may not need to terminate the search explicitly with @key{RET}. | |
42 | |
43 @c WideCommands | |
44 @table @kbd | |
45 @item C-s | |
46 Incremental search forward (@code{isearch-forward}). | |
47 @item C-r | |
48 Incremental search backward (@code{isearch-backward}). | |
49 @end table | |
50 | |
51 @kindex C-s | |
52 @findex isearch-forward | |
53 @kbd{C-s} starts an incremental search. @kbd{C-s} reads characters from | |
54 the keyboard and positions the cursor at the first occurrence of the | |
55 characters that you have typed. If you type @kbd{C-s} and then @kbd{F}, | |
56 the cursor moves right after the first @samp{F}. Type an @kbd{O}, and see | |
57 the cursor move to after the first @samp{FO}. After another @kbd{O}, the | |
58 cursor is after the first @samp{FOO} after the place where you started the | |
59 search. At each step, the buffer text that matches the search string is | |
60 highlighted, if the terminal can do that; at each step, the current search | |
61 string is updated in the echo area. | |
62 | |
63 If you make a mistake in typing the search string, you can cancel | |
64 characters with @key{DEL}. Each @key{DEL} cancels the last character of | |
65 search string. This does not happen until Emacs is ready to read another | |
66 input character; first it must either find, or fail to find, the character | |
67 you want to erase. If you do not want to wait for this to happen, use | |
68 @kbd{C-g} as described below. | |
69 | |
70 When you are satisfied with the place you have reached, you can type | |
71 @key{RET}, which stops searching, leaving the cursor where the search | |
72 brought it. Also, any command not specially meaningful in searches | |
73 stops the searching and is then executed. Thus, typing @kbd{C-a} would | |
74 exit the search and then move to the beginning of the line. @key{RET} | |
75 is necessary only if the next command you want to type is a printing | |
76 character, @key{DEL}, @key{RET}, or another control character that is | |
77 special within searches (@kbd{C-q}, @kbd{C-w}, @kbd{C-r}, @kbd{C-s}, | |
78 @kbd{C-y}, @kbd{M-y}, @kbd{M-r}, or @kbd{M-s}). | |
79 | |
80 Sometimes you search for @samp{FOO} and find it, but not the one you | |
81 expected to find. There was a second @samp{FOO} that you forgot about, | |
82 before the one you were aiming for. In this event, type another @kbd{C-s} | |
83 to move to the next occurrence of the search string. This can be done any | |
84 number of times. If you overshoot, you can cancel some @kbd{C-s} | |
85 characters with @key{DEL}. | |
86 | |
87 After you exit a search, you can search for the same string again by | |
88 typing just @kbd{C-s C-s}: the first @kbd{C-s} is the key that invokes | |
89 incremental search, and the second @kbd{C-s} means ``search again.'' | |
90 | |
91 To reuse earlier search strings, use the @dfn{search ring}. The | |
92 commands @kbd{M-p} and @kbd{M-n} move through the ring to pick a search | |
93 string to reuse. These commands leave the selected search ring element | |
94 in the minibuffer, where you can edit it. Type @kbd{C-s} or @kbd{C-r} | |
95 to terminate editing the string and search for it. | |
96 | |
97 If your string is not found at all, the echo area says @samp{Failing | |
98 I-Search}. The cursor is after the place where Emacs found as much of your | |
99 string as it could. Thus, if you search for @samp{FOOT}, and there is no | |
100 @samp{FOOT}, you might see the cursor after the @samp{FOO} in @samp{FOOL}. | |
101 At this point there are several things you can do. If your string was | |
102 mistyped, you can rub some of it out and correct it. If you like the place | |
103 you have found, you can type @key{RET} or some other Emacs command to | |
104 ``accept what the search offered.'' Or you can type @kbd{C-g}, which | |
105 removes from the search string the characters that could not be found (the | |
106 @samp{T} in @samp{FOOT}), leaving those that were found (the @samp{FOO} in | |
107 @samp{FOOT}). A second @kbd{C-g} at that point cancels the search | |
108 entirely, returning point to where it was when the search started. | |
109 | |
110 An upper-case letter in the search string makes the search | |
111 case-sensitive. If you delete the upper-case character from the search | |
112 string, it ceases to have this effect. @xref{Search Case}. | |
113 | |
114 If a search is failing and you ask to repeat it by typing another | |
115 @kbd{C-s}, it starts again from the beginning of the buffer. Repeating | |
116 a failing reverse search with @kbd{C-r} starts again from the end. This | |
117 is called @dfn{wrapping around}. @samp{Wrapped} appears in the search | |
118 prompt once this has happened. If you keep on going past the original | |
119 starting point of the search, it changes to @samp{Overwrapped}, which | |
120 means that you are revisiting matches that you have already seen. | |
121 | |
122 @cindex quitting (in search) | |
123 The @kbd{C-g} ``quit'' character does special things during searches; | |
124 just what it does depends on the status of the search. If the search has | |
125 found what you specified and is waiting for input, @kbd{C-g} cancels the | |
126 entire search. The cursor moves back to where you started the search. If | |
127 @kbd{C-g} is typed when there are characters in the search string that have | |
128 not been found---because Emacs is still searching for them, or because it | |
129 has failed to find them---then the search string characters which have not | |
130 been found are discarded from the search string. With them gone, the | |
131 search is now successful and waiting for more input, so a second @kbd{C-g} | |
132 will cancel the entire search. | |
133 | |
134 To search for a newline, type @kbd{C-j}. To search for another | |
135 control character, such as control-S or carriage return, you must quote | |
136 it by typing @kbd{C-q} first. This function of @kbd{C-q} is analogous | |
137 to its use for insertion (@pxref{Inserting Text}): it causes the | |
138 following character to be treated the way any ``ordinary'' character is | |
139 treated in the same context. You can also specify a character by its | |
140 octal code: enter @kbd{C-q} followed by a sequence of octal digits. | |
141 | |
142 You can change to searching backwards with @kbd{C-r}. If a search fails | |
143 because the place you started was too late in the file, you should do this. | |
144 Repeated @kbd{C-r} keeps looking for more occurrences backwards. A | |
145 @kbd{C-s} starts going forwards again. @kbd{C-r} in a search can be canceled | |
146 with @key{DEL}. | |
147 | |
148 @kindex C-r | |
149 @findex isearch-backward | |
150 If you know initially that you want to search backwards, you can use | |
151 @kbd{C-r} instead of @kbd{C-s} to start the search, because @kbd{C-r} as | |
152 a key runs a command (@code{isearch-backward}) to search backward. A | |
153 backward search finds matches that are entirely before the starting | |
154 point, just as a forward search finds matches that begin after it. | |
155 | |
156 The characters @kbd{C-y} and @kbd{C-w} can be used in incremental | |
157 search to grab text from the buffer into the search string. This makes | |
158 it convenient to search for another occurrence of text at point. | |
159 @kbd{C-w} copies the word after point as part of the search string, | |
160 advancing point over that word. Another @kbd{C-s} to repeat the search | |
161 will then search for a string including that word. @kbd{C-y} is similar | |
162 to @kbd{C-w} but copies all the rest of the current line into the search | |
163 string. Both @kbd{C-y} and @kbd{C-w} convert the text they copy to | |
164 lower case if the search is currently not case-sensitive; this is so the | |
165 search remains case-insensitive. | |
166 | |
167 The character @kbd{M-y} copies text from the kill ring into the search | |
168 string. It uses the same text that @kbd{C-y} as a command would yank. | |
27217 | 169 @kbd{mouse-2} in the echo area does the same. |
25829 | 170 @xref{Yanking}. |
171 | |
172 When you exit the incremental search, it sets the mark to where point | |
173 @emph{was}, before the search. That is convenient for moving back | |
174 there. In Transient Mark mode, incremental search sets the mark without | |
175 activating it, and does so only if the mark is not already active. | |
176 | |
27217 | 177 @cindex lazy search highlighting |
178 By default, Isearch uses @dfn{lazy highlighting}. All matches for | |
179 the current search string in the buffer after the point where searching | |
180 starts are highlighted. The extra highlighting makes it easier to | |
181 anticipate where the cursor will end up each time you press @kbd{C-s} or | |
182 @kbd{C-r} to repeat a pending search. Highlighting of these additional | |
183 matches happens in a deferred fashion so as not to rob Isearch of its | |
184 usual snappy response. | |
185 @vindex isearch-lazy-highlight-cleanup | |
186 By default the highlighting of matches is cleared when you end the | |
187 search. Customize the variable @code{isearch-lazy-highlight-cleanup} to | |
188 avoid cleaning up automatically. The command @kbd{M-x | |
189 isearch-lazy-highlight-cleanup} can be used to clean up manually. | |
190 @vindex isearch-lazy-highlight | |
191 Customize the variable @code{isearch-lazy-highlight} to turn off this | |
192 feature. | |
193 | |
25829 | 194 @vindex isearch-mode-map |
195 To customize the special characters that incremental search understands, | |
196 alter their bindings in the keymap @code{isearch-mode-map}. For a list | |
197 of bindings, look at the documentation of @code{isearch-mode} with | |
198 @kbd{C-h f isearch-mode @key{RET}}. | |
199 | |
200 @subsection Slow Terminal Incremental Search | |
201 | |
202 Incremental search on a slow terminal uses a modified style of display | |
203 that is designed to take less time. Instead of redisplaying the buffer at | |
204 each place the search gets to, it creates a new single-line window and uses | |
205 that to display the line that the search has found. The single-line window | |
206 comes into play as soon as point gets outside of the text that is already | |
207 on the screen. | |
208 | |
209 When you terminate the search, the single-line window is removed. | |
210 Then Emacs redisplays the window in which the search was done, to show | |
211 its new position of point. | |
212 | |
213 @ignore | |
214 The three dots at the end of the search string, normally used to indicate | |
215 that searching is going on, are not displayed in slow style display. | |
216 @end ignore | |
217 | |
218 @vindex search-slow-speed | |
219 The slow terminal style of display is used when the terminal baud rate is | |
220 less than or equal to the value of the variable @code{search-slow-speed}, | |
221 initially 1200. | |
222 | |
223 @vindex search-slow-window-lines | |
224 The number of lines to use in slow terminal search display is controlled | |
225 by the variable @code{search-slow-window-lines}. Its normal value is 1. | |
226 | |
227 @node Nonincremental Search, Word Search, Incremental Search, Search | |
228 @section Nonincremental Search | |
229 @cindex nonincremental search | |
230 | |
231 Emacs also has conventional nonincremental search commands, which require | |
232 you to type the entire search string before searching begins. | |
233 | |
234 @table @kbd | |
235 @item C-s @key{RET} @var{string} @key{RET} | |
236 Search for @var{string}. | |
237 @item C-r @key{RET} @var{string} @key{RET} | |
238 Search backward for @var{string}. | |
239 @end table | |
240 | |
241 To do a nonincremental search, first type @kbd{C-s @key{RET}}. This | |
242 enters the minibuffer to read the search string; terminate the string | |
243 with @key{RET}, and then the search takes place. If the string is not | |
244 found, the search command gets an error. | |
245 | |
246 The way @kbd{C-s @key{RET}} works is that the @kbd{C-s} invokes | |
247 incremental search, which is specially programmed to invoke nonincremental | |
248 search if the argument you give it is empty. (Such an empty argument would | |
249 otherwise be useless.) @kbd{C-r @key{RET}} also works this way. | |
250 | |
251 However, nonincremental searches performed using @kbd{C-s @key{RET}} do | |
252 not call @code{search-forward} right away. The first thing done is to see | |
253 if the next character is @kbd{C-w}, which requests a word search. | |
254 @ifinfo | |
255 @xref{Word Search}. | |
256 @end ifinfo | |
257 | |
258 @findex search-forward | |
259 @findex search-backward | |
260 Forward and backward nonincremental searches are implemented by the | |
261 commands @code{search-forward} and @code{search-backward}. These | |
262 commands may be bound to keys in the usual manner. The feature that you | |
263 can get to them via the incremental search commands exists for | |
264 historical reasons, and to avoid the need to find suitable key sequences | |
265 for them. | |
266 | |
267 @node Word Search, Regexp Search, Nonincremental Search, Search | |
268 @section Word Search | |
269 @cindex word search | |
270 | |
271 Word search searches for a sequence of words without regard to how the | |
272 words are separated. More precisely, you type a string of many words, | |
273 using single spaces to separate them, and the string can be found even if | |
274 there are multiple spaces, newlines or other punctuation between the words. | |
275 | |
276 Word search is useful for editing a printed document made with a text | |
277 formatter. If you edit while looking at the printed, formatted version, | |
278 you can't tell where the line breaks are in the source file. With word | |
279 search, you can search without having to know them. | |
280 | |
281 @table @kbd | |
282 @item C-s @key{RET} C-w @var{words} @key{RET} | |
283 Search for @var{words}, ignoring details of punctuation. | |
284 @item C-r @key{RET} C-w @var{words} @key{RET} | |
285 Search backward for @var{words}, ignoring details of punctuation. | |
286 @end table | |
287 | |
288 Word search is a special case of nonincremental search and is invoked | |
289 with @kbd{C-s @key{RET} C-w}. This is followed by the search string, | |
290 which must always be terminated with @key{RET}. Being nonincremental, | |
291 this search does not start until the argument is terminated. It works | |
292 by constructing a regular expression and searching for that; see | |
293 @ref{Regexp Search}. | |
294 | |
295 Use @kbd{C-r @key{RET} C-w} to do backward word search. | |
296 | |
297 @findex word-search-forward | |
298 @findex word-search-backward | |
299 Forward and backward word searches are implemented by the commands | |
300 @code{word-search-forward} and @code{word-search-backward}. These | |
301 commands may be bound to keys in the usual manner. The feature that you | |
302 can get to them via the incremental search commands exists for historical | |
303 reasons, and to avoid the need to find suitable key sequences for them. | |
304 | |
305 @node Regexp Search, Regexps, Word Search, Search | |
306 @section Regular Expression Search | |
307 @cindex regular expression | |
308 @cindex regexp | |
309 | |
310 A @dfn{regular expression} (@dfn{regexp}, for short) is a pattern that | |
311 denotes a class of alternative strings to match, possibly infinitely | |
312 many. In GNU Emacs, you can search for the next match for a regexp | |
313 either incrementally or not. | |
314 | |
315 @kindex C-M-s | |
316 @findex isearch-forward-regexp | |
317 @kindex C-M-r | |
318 @findex isearch-backward-regexp | |
319 Incremental search for a regexp is done by typing @kbd{C-M-s} | |
320 (@code{isearch-forward-regexp}). This command reads a search string | |
321 incrementally just like @kbd{C-s}, but it treats the search string as a | |
322 regexp rather than looking for an exact match against the text in the | |
323 buffer. Each time you add text to the search string, you make the | |
324 regexp longer, and the new regexp is searched for. Invoking @kbd{C-s} | |
325 with a prefix argument (its value does not matter) is another way to do | |
326 a forward incremental regexp search. To search backward for a regexp, | |
327 use @kbd{C-M-r} (@code{isearch-backward-regexp}), or @kbd{C-r} with a | |
328 prefix argument. | |
329 | |
330 All of the control characters that do special things within an | |
331 ordinary incremental search have the same function in incremental regexp | |
332 search. Typing @kbd{C-s} or @kbd{C-r} immediately after starting the | |
333 search retrieves the last incremental search regexp used; that is to | |
334 say, incremental regexp and non-regexp searches have independent | |
335 defaults. They also have separate search rings that you can access with | |
336 @kbd{M-p} and @kbd{M-n}. | |
337 | |
338 If you type @key{SPC} in incremental regexp search, it matches any | |
339 sequence of whitespace characters, including newlines. If you want | |
340 to match just a space, type @kbd{C-q @key{SPC}}. | |
341 | |
342 Note that adding characters to the regexp in an incremental regexp | |
343 search can make the cursor move back and start again. For example, if | |
344 you have searched for @samp{foo} and you add @samp{\|bar}, the cursor | |
345 backs up in case the first @samp{bar} precedes the first @samp{foo}. | |
346 | |
347 @findex re-search-forward | |
348 @findex re-search-backward | |
349 Nonincremental search for a regexp is done by the functions | |
350 @code{re-search-forward} and @code{re-search-backward}. You can invoke | |
351 these with @kbd{M-x}, or bind them to keys, or invoke them by way of | |
352 incremental regexp search with @kbd{C-M-s @key{RET}} and @kbd{C-M-r | |
353 @key{RET}}. | |
354 | |
355 If you use the incremental regexp search commands with a prefix | |
356 argument, they perform ordinary string search, like | |
357 @code{isearch-forward} and @code{isearch-backward}. @xref{Incremental | |
358 Search}. | |
359 | |
360 @node Regexps, Search Case, Regexp Search, Search | |
361 @section Syntax of Regular Expressions | |
362 @cindex regexp syntax | |
363 | |
364 Regular expressions have a syntax in which a few characters are | |
365 special constructs and the rest are @dfn{ordinary}. An ordinary | |
366 character is a simple regular expression which matches that same | |
367 character and nothing else. The special characters are @samp{$}, | |
368 @samp{^}, @samp{.}, @samp{*}, @samp{+}, @samp{?}, @samp{[}, @samp{]} and | |
369 @samp{\}. Any other character appearing in a regular expression is | |
370 ordinary, unless a @samp{\} precedes it. | |
371 | |
372 For example, @samp{f} is not a special character, so it is ordinary, and | |
373 therefore @samp{f} is a regular expression that matches the string | |
374 @samp{f} and no other string. (It does @emph{not} match the string | |
375 @samp{ff}.) Likewise, @samp{o} is a regular expression that matches | |
376 only @samp{o}. (When case distinctions are being ignored, these regexps | |
377 also match @samp{F} and @samp{O}, but we consider this a generalization | |
378 of ``the same string,'' rather than an exception.) | |
379 | |
380 Any two regular expressions @var{a} and @var{b} can be concatenated. The | |
381 result is a regular expression which matches a string if @var{a} matches | |
382 some amount of the beginning of that string and @var{b} matches the rest of | |
383 the string.@refill | |
384 | |
385 As a simple example, we can concatenate the regular expressions @samp{f} | |
386 and @samp{o} to get the regular expression @samp{fo}, which matches only | |
387 the string @samp{fo}. Still trivial. To do something nontrivial, you | |
388 need to use one of the special characters. Here is a list of them. | |
389 | |
390 @table @kbd | |
391 @item .@: @r{(Period)} | |
392 is a special character that matches any single character except a newline. | |
393 Using concatenation, we can make regular expressions like @samp{a.b}, which | |
394 matches any three-character string that begins with @samp{a} and ends with | |
395 @samp{b}.@refill | |
396 | |
397 @item * | |
398 is not a construct by itself; it is a postfix operator that means to | |
399 match the preceding regular expression repetitively as many times as | |
400 possible. Thus, @samp{o*} matches any number of @samp{o}s (including no | |
401 @samp{o}s). | |
402 | |
403 @samp{*} always applies to the @emph{smallest} possible preceding | |
404 expression. Thus, @samp{fo*} has a repeating @samp{o}, not a repeating | |
405 @samp{fo}. It matches @samp{f}, @samp{fo}, @samp{foo}, and so on. | |
406 | |
407 The matcher processes a @samp{*} construct by matching, immediately, | |
408 as many repetitions as can be found. Then it continues with the rest | |
409 of the pattern. If that fails, backtracking occurs, discarding some | |
410 of the matches of the @samp{*}-modified construct in case that makes | |
411 it possible to match the rest of the pattern. For example, in matching | |
412 @samp{ca*ar} against the string @samp{caaar}, the @samp{a*} first | |
413 tries to match all three @samp{a}s; but the rest of the pattern is | |
414 @samp{ar} and there is only @samp{r} left to match, so this try fails. | |
415 The next alternative is for @samp{a*} to match only two @samp{a}s. | |
416 With this choice, the rest of the regexp matches successfully.@refill | |
417 | |
418 @item + | |
419 is a postfix operator, similar to @samp{*} except that it must match | |
420 the preceding expression at least once. So, for example, @samp{ca+r} | |
421 matches the strings @samp{car} and @samp{caaaar} but not the string | |
422 @samp{cr}, whereas @samp{ca*r} matches all three strings. | |
423 | |
424 @item ? | |
425 is a postfix operator, similar to @samp{*} except that it can match the | |
426 preceding expression either once or not at all. For example, | |
427 @samp{ca?r} matches @samp{car} or @samp{cr}; nothing else. | |
428 | |
27094
6500fd0a7d8e
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
25829
diff
changeset
|
429 @item *?, +?, ?? |
27139
a9508422287d
Improve markup for the description of non-greedy operators.
Eli Zaretskii <eliz@gnu.org>
parents:
27094
diff
changeset
|
430 @cindex non-greedy regexp matching |
27094
6500fd0a7d8e
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
25829
diff
changeset
|
431 are non-greedy variants of the operators above. The normal operators |
27139
a9508422287d
Improve markup for the description of non-greedy operators.
Eli Zaretskii <eliz@gnu.org>
parents:
27094
diff
changeset
|
432 @samp{*}, @samp{+}, @samp{?} are @dfn{greedy} in that they match as much |
a9508422287d
Improve markup for the description of non-greedy operators.
Eli Zaretskii <eliz@gnu.org>
parents:
27094
diff
changeset
|
433 as they can, while if you append a @samp{?} after them, it makes them |
a9508422287d
Improve markup for the description of non-greedy operators.
Eli Zaretskii <eliz@gnu.org>
parents:
27094
diff
changeset
|
434 non-greedy: they will match as little as possible. |
27094
6500fd0a7d8e
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
25829
diff
changeset
|
435 |
28063
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
436 @item \@{@var{n},@var{m}\@} |
27694
5c14849aee4c
documented \{n,m\} intervals
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27217
diff
changeset
|
437 is another postfix operator that specifies an interval of iteration: |
28063
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
438 the preceding regular expression must match between @var{n} and |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
439 @var{m} times. If @var{m} is omitted, then there is no upper bound |
28134
60b77d9b88ec
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
28126
diff
changeset
|
440 and if @samp{,@var{m}} is omitted, then the regular expression must match |
28063
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
441 exactly @var{n} times. @* |
27694
5c14849aee4c
documented \{n,m\} intervals
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27217
diff
changeset
|
442 @samp{\@{0,1\@}} is equivalent to @samp{?}. @* |
5c14849aee4c
documented \{n,m\} intervals
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27217
diff
changeset
|
443 @samp{\@{0,\@}} is equivalent to @samp{*}. @* |
5c14849aee4c
documented \{n,m\} intervals
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27217
diff
changeset
|
444 @samp{\@{1,\@}} is equivalent to @samp{+}. @* |
28063
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
445 @samp{\@{@var{n}\@}} is equivalent to @samp{\@{@var{n},@var{n}\@}}. |
27694
5c14849aee4c
documented \{n,m\} intervals
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27217
diff
changeset
|
446 |
25829 | 447 @item [ @dots{} ] |
448 is a @dfn{character set}, which begins with @samp{[} and is terminated | |
449 by @samp{]}. In the simplest case, the characters between the two | |
450 brackets are what this set can match. | |
451 | |
452 Thus, @samp{[ad]} matches either one @samp{a} or one @samp{d}, and | |
453 @samp{[ad]*} matches any string composed of just @samp{a}s and @samp{d}s | |
454 (including the empty string), from which it follows that @samp{c[ad]*r} | |
455 matches @samp{cr}, @samp{car}, @samp{cdr}, @samp{caddaar}, etc. | |
456 | |
457 You can also include character ranges in a character set, by writing the | |
458 starting and ending characters with a @samp{-} between them. Thus, | |
459 @samp{[a-z]} matches any lower-case ASCII letter. Ranges may be | |
460 intermixed freely with individual characters, as in @samp{[a-z$%.]}, | |
461 which matches any lower-case ASCII letter or @samp{$}, @samp{%} or | |
462 period. | |
463 | |
464 Note that the usual regexp special characters are not special inside a | |
465 character set. A completely different set of special characters exists | |
466 inside character sets: @samp{]}, @samp{-} and @samp{^}. | |
467 | |
468 To include a @samp{]} in a character set, you must make it the first | |
469 character. For example, @samp{[]a]} matches @samp{]} or @samp{a}. To | |
470 include a @samp{-}, write @samp{-} as the first or last character of the | |
471 set, or put it after a range. Thus, @samp{[]-]} matches both @samp{]} | |
472 and @samp{-}. | |
473 | |
474 To include @samp{^} in a set, put it anywhere but at the beginning of | |
475 the set. | |
476 | |
477 When you use a range in case-insensitive search, you should write both | |
478 ends of the range in upper case, or both in lower case, or both should | |
479 be non-letters. The behavior of a mixed-case range such as @samp{A-z} | |
480 is somewhat ill-defined, and it may change in future Emacs versions. | |
481 | |
482 @item [^ @dots{} ] | |
483 @samp{[^} begins a @dfn{complemented character set}, which matches any | |
484 character except the ones specified. Thus, @samp{[^a-z0-9A-Z]} matches | |
485 all characters @emph{except} letters and digits. | |
486 | |
487 @samp{^} is not special in a character set unless it is the first | |
488 character. The character following the @samp{^} is treated as if it | |
489 were first (in other words, @samp{-} and @samp{]} are not special there). | |
490 | |
491 A complemented character set can match a newline, unless newline is | |
492 mentioned as one of the characters not to match. This is in contrast to | |
493 the handling of regexps in programs such as @code{grep}. | |
494 | |
495 @item ^ | |
496 is a special character that matches the empty string, but only at the | |
497 beginning of a line in the text being matched. Otherwise it fails to | |
498 match anything. Thus, @samp{^foo} matches a @samp{foo} that occurs at | |
499 the beginning of a line. | |
500 | |
501 @item $ | |
502 is similar to @samp{^} but matches only at the end of a line. Thus, | |
503 @samp{x+$} matches a string of one @samp{x} or more at the end of a line. | |
504 | |
505 @item \ | |
506 has two functions: it quotes the special characters (including | |
507 @samp{\}), and it introduces additional special constructs. | |
508 | |
509 Because @samp{\} quotes special characters, @samp{\$} is a regular | |
510 expression that matches only @samp{$}, and @samp{\[} is a regular | |
511 expression that matches only @samp{[}, and so on. | |
512 @end table | |
513 | |
514 Note: for historical compatibility, special characters are treated as | |
515 ordinary ones if they are in contexts where their special meanings make no | |
516 sense. For example, @samp{*foo} treats @samp{*} as ordinary since there is | |
517 no preceding expression on which the @samp{*} can act. It is poor practice | |
518 to depend on this behavior; it is better to quote the special character anyway, | |
519 regardless of where it appears.@refill | |
520 | |
521 For the most part, @samp{\} followed by any character matches only that | |
522 character. However, there are several exceptions: two-character | |
523 sequences starting with @samp{\} that have special meanings. The second | |
524 character in the sequence is always an ordinary character when used on | |
525 its own. Here is a table of @samp{\} constructs. | |
526 | |
527 @table @kbd | |
528 @item \| | |
529 specifies an alternative. Two regular expressions @var{a} and @var{b} | |
530 with @samp{\|} in between form an expression that matches some text if | |
531 either @var{a} matches it or @var{b} matches it. It works by trying to | |
532 match @var{a}, and if that fails, by trying to match @var{b}. | |
533 | |
534 Thus, @samp{foo\|bar} matches either @samp{foo} or @samp{bar} | |
535 but no other string.@refill | |
536 | |
537 @samp{\|} applies to the largest possible surrounding expressions. Only a | |
538 surrounding @samp{\( @dots{} \)} grouping can limit the grouping power of | |
539 @samp{\|}.@refill | |
540 | |
541 Full backtracking capability exists to handle multiple uses of @samp{\|}. | |
542 | |
543 @item \( @dots{} \) | |
544 is a grouping construct that serves three purposes: | |
545 | |
546 @enumerate | |
547 @item | |
548 To enclose a set of @samp{\|} alternatives for other operations. | |
549 Thus, @samp{\(foo\|bar\)x} matches either @samp{foox} or @samp{barx}. | |
550 | |
551 @item | |
552 To enclose a complicated expression for the postfix operators @samp{*}, | |
553 @samp{+} and @samp{?} to operate on. Thus, @samp{ba\(na\)*} matches | |
554 @samp{bananana}, etc., with any (zero or more) number of @samp{na} | |
555 strings.@refill | |
556 | |
557 @item | |
558 To record a matched substring for future reference. | |
559 @end enumerate | |
560 | |
561 This last application is not a consequence of the idea of a | |
562 parenthetical grouping; it is a separate feature that is assigned as a | |
563 second meaning to the same @samp{\( @dots{} \)} construct. In practice | |
28063
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
564 there is almost no conflict between the two meanings. |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
565 |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
566 @item \(?: @dots{} \) |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
567 is another grouping construct (often called ``shy'') that serves the same |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
568 first two purposes, but not the third: |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
569 it cannot be referred to later on by number. This is only useful |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
570 for mechanically constructed regular expressions where grouping |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
571 constructs need to be introduced implicitly and hence risk changing the |
f1b33463506d
*** empty log message ***
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
27694
diff
changeset
|
572 numbering of subsequent groups. |
25829 | 573 |
574 @item \@var{d} | |
575 matches the same text that matched the @var{d}th occurrence of a | |
576 @samp{\( @dots{} \)} construct. | |
577 | |
578 After the end of a @samp{\( @dots{} \)} construct, the matcher remembers | |
579 the beginning and end of the text matched by that construct. Then, | |
580 later on in the regular expression, you can use @samp{\} followed by the | |
581 digit @var{d} to mean ``match the same text matched the @var{d}th time | |
582 by the @samp{\( @dots{} \)} construct.'' | |
583 | |
584 The strings matching the first nine @samp{\( @dots{} \)} constructs | |
585 appearing in a regular expression are assigned numbers 1 through 9 in | |
586 the order that the open-parentheses appear in the regular expression. | |
587 So you can use @samp{\1} through @samp{\9} to refer to the text matched | |
588 by the corresponding @samp{\( @dots{} \)} constructs. | |
589 | |
590 For example, @samp{\(.*\)\1} matches any newline-free string that is | |
591 composed of two identical halves. The @samp{\(.*\)} matches the first | |
592 half, which may be anything, but the @samp{\1} that follows must match | |
593 the same exact text. | |
594 | |
595 If a particular @samp{\( @dots{} \)} construct matches more than once | |
596 (which can easily happen if it is followed by @samp{*}), only the last | |
597 match is recorded. | |
598 | |
599 @item \` | |
600 matches the empty string, but only at the beginning | |
601 of the buffer or string being matched against. | |
602 | |
603 @item \' | |
604 matches the empty string, but only at the end of | |
605 the buffer or string being matched against. | |
606 | |
607 @item \= | |
608 matches the empty string, but only at point. | |
609 | |
610 @item \b | |
611 matches the empty string, but only at the beginning or | |
612 end of a word. Thus, @samp{\bfoo\b} matches any occurrence of | |
613 @samp{foo} as a separate word. @samp{\bballs?\b} matches | |
614 @samp{ball} or @samp{balls} as a separate word.@refill | |
615 | |
616 @samp{\b} matches at the beginning or end of the buffer | |
617 regardless of what text appears next to it. | |
618 | |
619 @item \B | |
620 matches the empty string, but @emph{not} at the beginning or | |
621 end of a word. | |
622 | |
623 @item \< | |
624 matches the empty string, but only at the beginning of a word. | |
625 @samp{\<} matches at the beginning of the buffer only if a | |
626 word-constituent character follows. | |
627 | |
628 @item \> | |
629 matches the empty string, but only at the end of a word. @samp{\>} | |
630 matches at the end of the buffer only if the contents end with a | |
631 word-constituent character. | |
632 | |
633 @item \w | |
634 matches any word-constituent character. The syntax table | |
635 determines which characters these are. @xref{Syntax}. | |
636 | |
637 @item \W | |
638 matches any character that is not a word-constituent. | |
639 | |
640 @item \s@var{c} | |
641 matches any character whose syntax is @var{c}. Here @var{c} is a | |
642 character that represents a syntax code: thus, @samp{w} for word | |
643 constituent, @samp{-} for whitespace, @samp{(} for open parenthesis, | |
644 etc. Represent a character of whitespace (which can be a newline) by | |
645 either @samp{-} or a space character. | |
646 | |
647 @item \S@var{c} | |
648 matches any character whose syntax is not @var{c}. | |
649 @end table | |
650 | |
651 The constructs that pertain to words and syntax are controlled by the | |
652 setting of the syntax table (@pxref{Syntax}). | |
653 | |
654 Here is a complicated regexp, used by Emacs to recognize the end of a | |
655 sentence together with any whitespace that follows. It is given in Lisp | |
656 syntax to enable you to distinguish the spaces from the tab characters. In | |
657 Lisp syntax, the string constant begins and ends with a double-quote. | |
658 @samp{\"} stands for a double-quote as part of the regexp, @samp{\\} for a | |
659 backslash as part of the regexp, @samp{\t} for a tab and @samp{\n} for a | |
660 newline. | |
661 | |
662 @example | |
663 "[.?!][]\"')]*\\($\\|\t\\| \\)[ \t\n]*" | |
664 @end example | |
665 | |
666 @noindent | |
667 This contains four parts in succession: a character set matching period, | |
668 @samp{?}, or @samp{!}; a character set matching close-brackets, quotes, | |
669 or parentheses, repeated any number of times; an alternative in | |
670 backslash-parentheses that matches end-of-line, a tab, or two spaces; | |
671 and a character set matching whitespace characters, repeated any number | |
672 of times. | |
673 | |
674 To enter the same regexp interactively, you would type @key{TAB} to | |
675 enter a tab, and @kbd{C-j} to enter a newline. You would also type | |
676 single backslashes as themselves, instead of doubling them for Lisp syntax. | |
677 | |
678 @node Search Case, Replace, Regexps, Search | |
679 @section Searching and Case | |
680 | |
681 @vindex case-fold-search | |
682 Incremental searches in Emacs normally ignore the case of the text | |
683 they are searching through, if you specify the text in lower case. | |
684 Thus, if you specify searching for @samp{foo}, then @samp{Foo} and | |
685 @samp{foo} are also considered a match. Regexps, and in particular | |
686 character sets, are included: @samp{[ab]} would match @samp{a} or | |
687 @samp{A} or @samp{b} or @samp{B}.@refill | |
688 | |
689 An upper-case letter anywhere in the incremental search string makes | |
690 the search case-sensitive. Thus, searching for @samp{Foo} does not find | |
691 @samp{foo} or @samp{FOO}. This applies to regular expression search as | |
692 well as to string search. The effect ceases if you delete the | |
693 upper-case letter from the search string. | |
694 | |
695 If you set the variable @code{case-fold-search} to @code{nil}, then | |
696 all letters must match exactly, including case. This is a per-buffer | |
697 variable; altering the variable affects only the current buffer, but | |
698 there is a default value which you can change as well. @xref{Locals}. | |
699 This variable applies to nonincremental searches also, including those | |
700 performed by the replace commands (@pxref{Replace}) and the minibuffer | |
701 history matching commands (@pxref{Minibuffer History}). | |
702 | |
703 @node Replace, Other Repeating Search, Search Case, Search | |
704 @section Replacement Commands | |
705 @cindex replacement | |
706 @cindex search-and-replace commands | |
707 @cindex string substitution | |
708 @cindex global substitution | |
709 | |
710 Global search-and-replace operations are not needed as often in Emacs | |
711 as they are in other editors@footnote{In some editors, | |
712 search-and-replace operations are the only convenient way to make a | |
713 single change in the text.}, but they are available. In addition to the | |
714 simple @kbd{M-x replace-string} command which is like that found in most | |
715 editors, there is a @kbd{M-x query-replace} command which asks you, for | |
716 each occurrence of the pattern, whether to replace it. | |
717 | |
718 The replace commands normally operate on the text from point to the | |
719 end of the buffer; however, in Transient Mark mode, when the mark is | |
720 active, they operate on the region. The replace commands all replace | |
721 one string (or regexp) with one replacement string. It is possible to | |
722 perform several replacements in parallel using the command | |
723 @code{expand-region-abbrevs} (@pxref{Expanding Abbrevs}). | |
724 | |
725 @menu | |
726 * Unconditional Replace:: Replacing all matches for a string. | |
727 * Regexp Replace:: Replacing all matches for a regexp. | |
728 * Replacement and Case:: How replacements preserve case of letters. | |
729 * Query Replace:: How to use querying. | |
730 @end menu | |
731 | |
732 @node Unconditional Replace, Regexp Replace, Replace, Replace | |
733 @subsection Unconditional Replacement | |
734 @findex replace-string | |
735 @findex replace-regexp | |
736 | |
737 @table @kbd | |
738 @item M-x replace-string @key{RET} @var{string} @key{RET} @var{newstring} @key{RET} | |
739 Replace every occurrence of @var{string} with @var{newstring}. | |
740 @item M-x replace-regexp @key{RET} @var{regexp} @key{RET} @var{newstring} @key{RET} | |
741 Replace every match for @var{regexp} with @var{newstring}. | |
742 @end table | |
743 | |
744 To replace every instance of @samp{foo} after point with @samp{bar}, | |
745 use the command @kbd{M-x replace-string} with the two arguments | |
746 @samp{foo} and @samp{bar}. Replacement happens only in the text after | |
747 point, so if you want to cover the whole buffer you must go to the | |
748 beginning first. All occurrences up to the end of the buffer are | |
749 replaced; to limit replacement to part of the buffer, narrow to that | |
750 part of the buffer before doing the replacement (@pxref{Narrowing}). | |
751 In Transient Mark mode, when the region is active, replacement is | |
752 limited to the region (@pxref{Transient Mark}). | |
753 | |
754 When @code{replace-string} exits, it leaves point at the last | |
755 occurrence replaced. It sets the mark to the prior position of point | |
756 (where the @code{replace-string} command was issued); use @kbd{C-u | |
757 C-@key{SPC}} to move back there. | |
758 | |
759 A numeric argument restricts replacement to matches that are surrounded | |
760 by word boundaries. The argument's value doesn't matter. | |
761 | |
762 @node Regexp Replace, Replacement and Case, Unconditional Replace, Replace | |
763 @subsection Regexp Replacement | |
764 | |
765 The @kbd{M-x replace-string} command replaces exact matches for a | |
766 single string. The similar command @kbd{M-x replace-regexp} replaces | |
767 any match for a specified pattern. | |
768 | |
769 In @code{replace-regexp}, the @var{newstring} need not be constant: it | |
770 can refer to all or part of what is matched by the @var{regexp}. | |
771 @samp{\&} in @var{newstring} stands for the entire match being replaced. | |
772 @samp{\@var{d}} in @var{newstring}, where @var{d} is a digit, stands for | |
773 whatever matched the @var{d}th parenthesized grouping in @var{regexp}. | |
774 To include a @samp{\} in the text to replace with, you must enter | |
775 @samp{\\}. For example, | |
776 | |
777 @example | |
778 M-x replace-regexp @key{RET} c[ad]+r @key{RET} \&-safe @key{RET} | |
779 @end example | |
780 | |
781 @noindent | |
782 replaces (for example) @samp{cadr} with @samp{cadr-safe} and @samp{cddr} | |
783 with @samp{cddr-safe}. | |
784 | |
785 @example | |
786 M-x replace-regexp @key{RET} \(c[ad]+r\)-safe @key{RET} \1 @key{RET} | |
787 @end example | |
788 | |
789 @noindent | |
790 performs the inverse transformation. | |
791 | |
792 @node Replacement and Case, Query Replace, Regexp Replace, Replace | |
793 @subsection Replace Commands and Case | |
794 | |
795 If the first argument of a replace command is all lower case, the | |
796 commands ignores case while searching for occurrences to | |
797 replace---provided @code{case-fold-search} is non-@code{nil}. If | |
798 @code{case-fold-search} is set to @code{nil}, case is always significant | |
799 in all searches. | |
800 | |
801 @vindex case-replace | |
802 In addition, when the @var{newstring} argument is all or partly lower | |
803 case, replacement commands try to preserve the case pattern of each | |
804 occurrence. Thus, the command | |
805 | |
806 @example | |
807 M-x replace-string @key{RET} foo @key{RET} bar @key{RET} | |
808 @end example | |
809 | |
810 @noindent | |
811 replaces a lower case @samp{foo} with a lower case @samp{bar}, an | |
812 all-caps @samp{FOO} with @samp{BAR}, and a capitalized @samp{Foo} with | |
813 @samp{Bar}. (These three alternatives---lower case, all caps, and | |
814 capitalized, are the only ones that @code{replace-string} can | |
815 distinguish.) | |
816 | |
817 If upper-case letters are used in the replacement string, they remain | |
818 upper case every time that text is inserted. If upper-case letters are | |
819 used in the first argument, the second argument is always substituted | |
820 exactly as given, with no case conversion. Likewise, if either | |
821 @code{case-replace} or @code{case-fold-search} is set to @code{nil}, | |
822 replacement is done without case conversion. | |
823 | |
824 @node Query Replace,, Replacement and Case, Replace | |
825 @subsection Query Replace | |
826 @cindex query replace | |
827 | |
828 @table @kbd | |
829 @item M-% @var{string} @key{RET} @var{newstring} @key{RET} | |
830 @itemx M-x query-replace @key{RET} @var{string} @key{RET} @var{newstring} @key{RET} | |
831 Replace some occurrences of @var{string} with @var{newstring}. | |
832 @item C-M-% @var{regexp} @key{RET} @var{newstring} @key{RET} | |
833 @itemx M-x query-replace-regexp @key{RET} @var{regexp} @key{RET} @var{newstring} @key{RET} | |
834 Replace some matches for @var{regexp} with @var{newstring}. | |
835 @end table | |
836 | |
837 @kindex M-% | |
838 @findex query-replace | |
839 If you want to change only some of the occurrences of @samp{foo} to | |
840 @samp{bar}, not all of them, then you cannot use an ordinary | |
841 @code{replace-string}. Instead, use @kbd{M-%} (@code{query-replace}). | |
842 This command finds occurrences of @samp{foo} one by one, displays each | |
843 occurrence and asks you whether to replace it. A numeric argument to | |
844 @code{query-replace} tells it to consider only occurrences that are | |
845 bounded by word-delimiter characters. This preserves case, just like | |
846 @code{replace-string}, provided @code{case-replace} is non-@code{nil}, | |
847 as it normally is. | |
848 | |
849 @kindex C-M-% | |
850 @findex query-replace-regexp | |
851 Aside from querying, @code{query-replace} works just like | |
852 @code{replace-string}, and @code{query-replace-regexp} works just like | |
853 @code{replace-regexp}. This command is run by @kbd{C-M-%}. | |
854 | |
855 The things you can type when you are shown an occurrence of @var{string} | |
856 or a match for @var{regexp} are: | |
857 | |
858 @ignore @c Not worth it. | |
859 @kindex SPC @r{(query-replace)} | |
860 @kindex DEL @r{(query-replace)} | |
861 @kindex , @r{(query-replace)} | |
862 @kindex RET @r{(query-replace)} | |
863 @kindex . @r{(query-replace)} | |
864 @kindex ! @r{(query-replace)} | |
865 @kindex ^ @r{(query-replace)} | |
866 @kindex C-r @r{(query-replace)} | |
867 @kindex C-w @r{(query-replace)} | |
868 @kindex C-l @r{(query-replace)} | |
869 @end ignore | |
870 | |
871 @c WideCommands | |
872 @table @kbd | |
873 @item @key{SPC} | |
874 to replace the occurrence with @var{newstring}. | |
875 | |
876 @item @key{DEL} | |
877 to skip to the next occurrence without replacing this one. | |
878 | |
879 @item , @r{(Comma)} | |
880 to replace this occurrence and display the result. You are then asked | |
881 for another input character to say what to do next. Since the | |
882 replacement has already been made, @key{DEL} and @key{SPC} are | |
883 equivalent in this situation; both move to the next occurrence. | |
884 | |
885 You can type @kbd{C-r} at this point (see below) to alter the replaced | |
886 text. You can also type @kbd{C-x u} to undo the replacement; this exits | |
887 the @code{query-replace}, so if you want to do further replacement you | |
888 must use @kbd{C-x @key{ESC} @key{ESC} @key{RET}} to restart | |
889 (@pxref{Repetition}). | |
890 | |
891 @item @key{RET} | |
892 to exit without doing any more replacements. | |
893 | |
894 @item .@: @r{(Period)} | |
895 to replace this occurrence and then exit without searching for more | |
896 occurrences. | |
897 | |
898 @item ! | |
899 to replace all remaining occurrences without asking again. | |
900 | |
901 @item ^ | |
902 to go back to the position of the previous occurrence (or what used to | |
903 be an occurrence), in case you changed it by mistake. This works by | |
904 popping the mark ring. Only one @kbd{^} in a row is meaningful, because | |
905 only one previous replacement position is kept during @code{query-replace}. | |
906 | |
907 @item C-r | |
908 to enter a recursive editing level, in case the occurrence needs to be | |
909 edited rather than just replaced with @var{newstring}. When you are | |
910 done, exit the recursive editing level with @kbd{C-M-c} to proceed to | |
911 the next occurrence. @xref{Recursive Edit}. | |
912 | |
913 @item C-w | |
914 to delete the occurrence, and then enter a recursive editing level as in | |
915 @kbd{C-r}. Use the recursive edit to insert text to replace the deleted | |
916 occurrence of @var{string}. When done, exit the recursive editing level | |
917 with @kbd{C-M-c} to proceed to the next occurrence. | |
918 | |
919 @item C-l | |
920 to redisplay the screen. Then you must type another character to | |
921 specify what to do with this occurrence. | |
922 | |
923 @item C-h | |
924 to display a message summarizing these options. Then you must type | |
925 another character to specify what to do with this occurrence. | |
926 @end table | |
927 | |
928 Some other characters are aliases for the ones listed above: @kbd{y}, | |
929 @kbd{n} and @kbd{q} are equivalent to @key{SPC}, @key{DEL} and | |
930 @key{RET}. | |
931 | |
932 Aside from this, any other character exits the @code{query-replace}, | |
933 and is then reread as part of a key sequence. Thus, if you type | |
934 @kbd{C-k}, it exits the @code{query-replace} and then kills to end of | |
935 line. | |
936 | |
937 To restart a @code{query-replace} once it is exited, use @kbd{C-x | |
938 @key{ESC} @key{ESC}}, which repeats the @code{query-replace} because it | |
939 used the minibuffer to read its arguments. @xref{Repetition, C-x ESC | |
940 ESC}. | |
941 | |
942 See also @ref{Transforming File Names}, for Dired commands to rename, | |
943 copy, or link files by replacing regexp matches in file names. | |
944 | |
945 @node Other Repeating Search,, Replace, Search | |
946 @section Other Search-and-Loop Commands | |
947 | |
948 Here are some other commands that find matches for a regular | |
949 expression. They all operate from point to the end of the buffer, and | |
950 all ignore case in matching, if the pattern contains no upper-case | |
951 letters and @code{case-fold-search} is non-@code{nil}. | |
952 | |
953 @findex list-matching-lines | |
954 @findex occur | |
955 @findex count-matches | |
956 @findex delete-non-matching-lines | |
957 @findex delete-matching-lines | |
958 @findex flush-lines | |
959 @findex keep-lines | |
960 | |
961 @table @kbd | |
962 @item M-x occur @key{RET} @var{regexp} @key{RET} | |
963 Display a list showing each line in the buffer that contains a match for | |
964 @var{regexp}. A numeric argument specifies the number of context lines | |
965 to print before and after each matching line; the default is none. | |
966 To limit the search to part of the buffer, narrow to that part | |
967 (@pxref{Narrowing}). | |
968 | |
969 @kindex RET @r{(Occur mode)} | |
970 The buffer @samp{*Occur*} containing the output serves as a menu for | |
971 finding the occurrences in their original context. Click @kbd{Mouse-2} | |
972 on an occurrence listed in @samp{*Occur*}, or position point there and | |
973 type @key{RET}; this switches to the buffer that was searched and | |
974 moves point to the original of the chosen occurrence. | |
975 | |
976 @item M-x list-matching-lines | |
977 Synonym for @kbd{M-x occur}. | |
978 | |
979 @item M-x count-matches @key{RET} @var{regexp} @key{RET} | |
980 Print the number of matches for @var{regexp} after point. | |
981 | |
982 @item M-x flush-lines @key{RET} @var{regexp} @key{RET} | |
983 Delete each line that follows point and contains a match for | |
984 @var{regexp}. | |
985 | |
986 @item M-x keep-lines @key{RET} @var{regexp} @key{RET} | |
987 Delete each line that follows point and @emph{does not} contain a match | |
988 for @var{regexp}. | |
989 @end table | |
990 | |
28447
ec699636f83a
(Other Repeating Search): Mention tags-based search.
Dave Love <fx@gnu.org>
parents:
28134
diff
changeset
|
991 Searching and replacing can be performed under the control of tags |
ec699636f83a
(Other Repeating Search): Mention tags-based search.
Dave Love <fx@gnu.org>
parents:
28134
diff
changeset
|
992 files (@pxref{Tags Search}) and Dired (@pxref{Operating on Files}). |
ec699636f83a
(Other Repeating Search): Mention tags-based search.
Dave Love <fx@gnu.org>
parents:
28134
diff
changeset
|
993 |
25829 | 994 In addition, you can use @code{grep} from Emacs to search a collection |
995 of files for matches for a regular expression, then visit the matches | |
996 either sequentially or in arbitrary order. @xref{Grep Searching}. |