Commit | Line | Data |
---|---|---|
b8d4c8d0 GM |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
acaf905b | 3 | @c Copyright (C) 1990-1995, 1998-1999, 2001-2012 |
d24880de | 4 | @c Free Software Foundation, Inc. |
b8d4c8d0 | 5 | @c See the file elisp.texi for copying conditions. |
6336d8c3 | 6 | @setfilename ../../info/strings |
b8d4c8d0 GM |
7 | @node Strings and Characters, Lists, Numbers, Top |
8 | @comment node-name, next, previous, up | |
9 | @chapter Strings and Characters | |
10 | @cindex strings | |
11 | @cindex character arrays | |
12 | @cindex characters | |
13 | @cindex bytes | |
14 | ||
15 | A string in Emacs Lisp is an array that contains an ordered sequence | |
16 | of characters. Strings are used as names of symbols, buffers, and | |
17 | files; to send messages to users; to hold text being copied between | |
18 | buffers; and for many other purposes. Because strings are so important, | |
19 | Emacs Lisp has many functions expressly for manipulating them. Emacs | |
20 | Lisp programs use strings more often than individual characters. | |
21 | ||
22 | @xref{Strings of Events}, for special considerations for strings of | |
23 | keyboard character events. | |
24 | ||
25 | @menu | |
26 | * Basics: String Basics. Basic properties of strings and characters. | |
27 | * Predicates for Strings:: Testing whether an object is a string or char. | |
28 | * Creating Strings:: Functions to allocate new strings. | |
29 | * Modifying Strings:: Altering the contents of an existing string. | |
30 | * Text Comparison:: Comparing characters or strings. | |
31 | * String Conversion:: Converting to and from characters and strings. | |
32 | * Formatting Strings:: @code{format}: Emacs's analogue of @code{printf}. | |
33 | * Case Conversion:: Case conversion functions. | |
d24880de | 34 | * Case Tables:: Customizing case conversion. |
b8d4c8d0 GM |
35 | @end menu |
36 | ||
37 | @node String Basics | |
38 | @section String and Character Basics | |
39 | ||
40 | Characters are represented in Emacs Lisp as integers; | |
41 | whether an integer is a character or not is determined only by how it is | |
b5173574 EZ |
42 | used. Thus, strings really contain integers. @xref{Character Codes}, |
43 | for details about character representation in Emacs. | |
b8d4c8d0 GM |
44 | |
45 | The length of a string (like any array) is fixed, and cannot be | |
46 | altered once the string exists. Strings in Lisp are @emph{not} | |
47 | terminated by a distinguished character code. (By contrast, strings in | |
48 | C are terminated by a character with @acronym{ASCII} code 0.) | |
49 | ||
50 | Since strings are arrays, and therefore sequences as well, you can | |
51 | operate on them with the general array and sequence functions. | |
52 | (@xref{Sequences Arrays Vectors}.) For example, you can access or | |
53 | change individual characters in a string using the functions @code{aref} | |
54 | and @code{aset} (@pxref{Array Functions}). | |
55 | ||
56 | There are two text representations for non-@acronym{ASCII} characters in | |
57 | Emacs strings (and in buffers): unibyte and multibyte (@pxref{Text | |
b5173574 EZ |
58 | Representations}). For most Lisp programming, you don't need to be |
59 | concerned with these two representations. | |
b8d4c8d0 | 60 | |
5dedd9b5 EZ |
61 | Sometimes key sequences are represented as unibyte strings. When a |
62 | unibyte string is a key sequence, string elements in the range 128 to | |
63 | 255 represent meta characters (which are large integers) rather than | |
8f88eb24 CY |
64 | character codes in the range 128 to 255. Strings cannot hold |
65 | characters that have the hyper, super or alt modifiers; they can hold | |
66 | @acronym{ASCII} control characters, but no other control characters. | |
67 | They do not distinguish case in @acronym{ASCII} control characters. | |
68 | If you want to store such characters in a sequence, such as a key | |
69 | sequence, you must use a vector instead of a string. @xref{Character | |
70 | Type}, for more information about keyboard input characters. | |
b8d4c8d0 GM |
71 | |
72 | Strings are useful for holding regular expressions. You can also | |
73 | match regular expressions against strings with @code{string-match} | |
74 | (@pxref{Regexp Search}). The functions @code{match-string} | |
75 | (@pxref{Simple Match Data}) and @code{replace-match} (@pxref{Replacing | |
76 | Match}) are useful for decomposing and modifying strings after | |
77 | matching regular expressions against them. | |
78 | ||
79 | Like a buffer, a string can contain text properties for the characters | |
80 | in it, as well as the characters themselves. @xref{Text Properties}. | |
81 | All the Lisp primitives that copy text from strings to buffers or other | |
82 | strings also copy the properties of the characters being copied. | |
83 | ||
84 | @xref{Text}, for information about functions that display strings or | |
85 | copy them into buffers. @xref{Character Type}, and @ref{String Type}, | |
86 | for information about the syntax of characters and strings. | |
87 | @xref{Non-ASCII Characters}, for functions to convert between text | |
88 | representations and to encode and decode character codes. | |
89 | ||
90 | @node Predicates for Strings | |
91 | @section The Predicates for Strings | |
92 | ||
93 | For more information about general sequence and array predicates, | |
94 | see @ref{Sequences Arrays Vectors}, and @ref{Arrays}. | |
95 | ||
96 | @defun stringp object | |
97 | This function returns @code{t} if @var{object} is a string, @code{nil} | |
98 | otherwise. | |
99 | @end defun | |
100 | ||
101 | @defun string-or-null-p object | |
8c641f06 | 102 | This function returns @code{t} if @var{object} is a string or |
638a2457 | 103 | @code{nil}. It returns @code{nil} otherwise. |
b8d4c8d0 GM |
104 | @end defun |
105 | ||
106 | @defun char-or-string-p object | |
107 | This function returns @code{t} if @var{object} is a string or a | |
108 | character (i.e., an integer), @code{nil} otherwise. | |
109 | @end defun | |
110 | ||
111 | @node Creating Strings | |
112 | @section Creating Strings | |
113 | ||
114 | The following functions create strings, either from scratch, or by | |
115 | putting strings together, or by taking them apart. | |
116 | ||
117 | @defun make-string count character | |
118 | This function returns a string made up of @var{count} repetitions of | |
119 | @var{character}. If @var{count} is negative, an error is signaled. | |
120 | ||
121 | @example | |
122 | (make-string 5 ?x) | |
123 | @result{} "xxxxx" | |
124 | (make-string 0 ?x) | |
125 | @result{} "" | |
126 | @end example | |
127 | ||
3e99b825 CY |
128 | Other functions to compare with this one include @code{make-vector} |
129 | (@pxref{Vectors}) and @code{make-list} (@pxref{Building Lists}). | |
b8d4c8d0 GM |
130 | @end defun |
131 | ||
132 | @defun string &rest characters | |
133 | This returns a string containing the characters @var{characters}. | |
134 | ||
135 | @example | |
136 | (string ?a ?b ?c) | |
137 | @result{} "abc" | |
138 | @end example | |
139 | @end defun | |
140 | ||
141 | @defun substring string start &optional end | |
142 | This function returns a new string which consists of those characters | |
143 | from @var{string} in the range from (and including) the character at the | |
144 | index @var{start} up to (but excluding) the character at the index | |
145 | @var{end}. The first character is at index zero. | |
146 | ||
147 | @example | |
148 | @group | |
149 | (substring "abcdefg" 0 3) | |
150 | @result{} "abc" | |
151 | @end group | |
152 | @end example | |
153 | ||
154 | @noindent | |
8f88eb24 CY |
155 | In the above example, the index for @samp{a} is 0, the index for |
156 | @samp{b} is 1, and the index for @samp{c} is 2. The index 3---which | |
a86cd395 JB |
157 | is the fourth character in the string---marks the character position |
158 | up to which the substring is copied. Thus, @samp{abc} is copied from | |
159 | the string @code{"abcdefg"}. | |
b8d4c8d0 GM |
160 | |
161 | A negative number counts from the end of the string, so that @minus{}1 | |
162 | signifies the index of the last character of the string. For example: | |
163 | ||
164 | @example | |
165 | @group | |
166 | (substring "abcdefg" -3 -1) | |
167 | @result{} "ef" | |
168 | @end group | |
169 | @end example | |
170 | ||
171 | @noindent | |
172 | In this example, the index for @samp{e} is @minus{}3, the index for | |
173 | @samp{f} is @minus{}2, and the index for @samp{g} is @minus{}1. | |
174 | Therefore, @samp{e} and @samp{f} are included, and @samp{g} is excluded. | |
175 | ||
176 | When @code{nil} is used for @var{end}, it stands for the length of the | |
177 | string. Thus, | |
178 | ||
179 | @example | |
180 | @group | |
181 | (substring "abcdefg" -3 nil) | |
182 | @result{} "efg" | |
183 | @end group | |
184 | @end example | |
185 | ||
186 | Omitting the argument @var{end} is equivalent to specifying @code{nil}. | |
187 | It follows that @code{(substring @var{string} 0)} returns a copy of all | |
188 | of @var{string}. | |
189 | ||
190 | @example | |
191 | @group | |
192 | (substring "abcdefg" 0) | |
193 | @result{} "abcdefg" | |
194 | @end group | |
195 | @end example | |
196 | ||
197 | @noindent | |
198 | But we recommend @code{copy-sequence} for this purpose (@pxref{Sequence | |
199 | Functions}). | |
200 | ||
201 | If the characters copied from @var{string} have text properties, the | |
202 | properties are copied into the new string also. @xref{Text Properties}. | |
203 | ||
204 | @code{substring} also accepts a vector for the first argument. | |
205 | For example: | |
206 | ||
207 | @example | |
208 | (substring [a b (c) "d"] 1 3) | |
209 | @result{} [b (c)] | |
210 | @end example | |
211 | ||
212 | A @code{wrong-type-argument} error is signaled if @var{start} is not | |
213 | an integer or if @var{end} is neither an integer nor @code{nil}. An | |
214 | @code{args-out-of-range} error is signaled if @var{start} indicates a | |
215 | character following @var{end}, or if either integer is out of range | |
216 | for @var{string}. | |
217 | ||
218 | Contrast this function with @code{buffer-substring} (@pxref{Buffer | |
219 | Contents}), which returns a string containing a portion of the text in | |
220 | the current buffer. The beginning of a string is at index 0, but the | |
221 | beginning of a buffer is at index 1. | |
222 | @end defun | |
223 | ||
224 | @defun substring-no-properties string &optional start end | |
225 | This works like @code{substring} but discards all text properties from | |
226 | the value. Also, @var{start} may be omitted or @code{nil}, which is | |
227 | equivalent to 0. Thus, @w{@code{(substring-no-properties | |
228 | @var{string})}} returns a copy of @var{string}, with all text | |
229 | properties removed. | |
230 | @end defun | |
231 | ||
232 | @defun concat &rest sequences | |
233 | @cindex copying strings | |
234 | @cindex concatenating strings | |
235 | This function returns a new string consisting of the characters in the | |
236 | arguments passed to it (along with their text properties, if any). The | |
237 | arguments may be strings, lists of numbers, or vectors of numbers; they | |
238 | are not themselves changed. If @code{concat} receives no arguments, it | |
239 | returns an empty string. | |
240 | ||
241 | @example | |
242 | (concat "abc" "-def") | |
243 | @result{} "abc-def" | |
244 | (concat "abc" (list 120 121) [122]) | |
245 | @result{} "abcxyz" | |
246 | ;; @r{@code{nil} is an empty sequence.} | |
247 | (concat "abc" nil "-def") | |
248 | @result{} "abc-def" | |
249 | (concat "The " "quick brown " "fox.") | |
250 | @result{} "The quick brown fox." | |
251 | (concat) | |
252 | @result{} "" | |
253 | @end example | |
254 | ||
255 | @noindent | |
8f88eb24 CY |
256 | This function always constructs a new string that is not @code{eq} to |
257 | any existing string, except when the result is the empty string (to | |
258 | save space, Emacs makes only one empty multibyte string). | |
b8d4c8d0 GM |
259 | |
260 | For information about other concatenation functions, see the | |
261 | description of @code{mapconcat} in @ref{Mapping Functions}, | |
262 | @code{vconcat} in @ref{Vector Functions}, and @code{append} in @ref{Building | |
fd6f900c EZ |
263 | Lists}. For concatenating individual command-line arguments into a |
264 | string to be used as a shell command, see @ref{Shell Arguments, | |
265 | combine-and-quote-strings}. | |
b8d4c8d0 GM |
266 | @end defun |
267 | ||
268 | @defun split-string string &optional separators omit-nulls | |
8f88eb24 CY |
269 | This function splits @var{string} into substrings based on the regular |
270 | expression @var{separators} (@pxref{Regular Expressions}). Each match | |
271 | for @var{separators} defines a splitting point; the substrings between | |
272 | splitting points are made into a list, which is returned. | |
b8d4c8d0 | 273 | |
8f88eb24 CY |
274 | If @var{omit-nulls} is @code{nil} (or omitted), the result contains |
275 | null strings whenever there are two consecutive matches for | |
276 | @var{separators}, or a match is adjacent to the beginning or end of | |
277 | @var{string}. If @var{omit-nulls} is @code{t}, these null strings are | |
278 | omitted from the result. | |
b8d4c8d0 | 279 | |
8f88eb24 CY |
280 | If @var{separators} is @code{nil} (or omitted), the default is the |
281 | value of @code{split-string-default-separators}. | |
b8d4c8d0 GM |
282 | |
283 | As a special case, when @var{separators} is @code{nil} (or omitted), | |
284 | null strings are always omitted from the result. Thus: | |
285 | ||
286 | @example | |
287 | (split-string " two words ") | |
288 | @result{} ("two" "words") | |
289 | @end example | |
290 | ||
291 | The result is not @code{("" "two" "words" "")}, which would rarely be | |
292 | useful. If you need such a result, use an explicit value for | |
293 | @var{separators}: | |
294 | ||
295 | @example | |
296 | (split-string " two words " | |
297 | split-string-default-separators) | |
298 | @result{} ("" "two" "words" "") | |
299 | @end example | |
300 | ||
301 | More examples: | |
302 | ||
303 | @example | |
304 | (split-string "Soup is good food" "o") | |
305 | @result{} ("S" "up is g" "" "d f" "" "d") | |
306 | (split-string "Soup is good food" "o" t) | |
307 | @result{} ("S" "up is g" "d f" "d") | |
308 | (split-string "Soup is good food" "o+") | |
309 | @result{} ("S" "up is g" "d f" "d") | |
310 | @end example | |
311 | ||
312 | Empty matches do count, except that @code{split-string} will not look | |
313 | for a final empty match when it already reached the end of the string | |
314 | using a non-empty match or when @var{string} is empty: | |
315 | ||
316 | @example | |
317 | (split-string "aooob" "o*") | |
318 | @result{} ("" "a" "" "b" "") | |
319 | (split-string "ooaboo" "o*") | |
320 | @result{} ("" "" "a" "b" "") | |
321 | (split-string "" "") | |
322 | @result{} ("") | |
323 | @end example | |
324 | ||
325 | However, when @var{separators} can match the empty string, | |
326 | @var{omit-nulls} is usually @code{t}, so that the subtleties in the | |
327 | three previous examples are rarely relevant: | |
328 | ||
329 | @example | |
330 | (split-string "Soup is good food" "o*" t) | |
331 | @result{} ("S" "u" "p" " " "i" "s" " " "g" "d" " " "f" "d") | |
332 | (split-string "Nice doggy!" "" t) | |
333 | @result{} ("N" "i" "c" "e" " " "d" "o" "g" "g" "y" "!") | |
334 | (split-string "" "" t) | |
335 | @result{} nil | |
336 | @end example | |
337 | ||
338 | Somewhat odd, but predictable, behavior can occur for certain | |
339 | ``non-greedy'' values of @var{separators} that can prefer empty | |
340 | matches over non-empty matches. Again, such values rarely occur in | |
341 | practice: | |
342 | ||
343 | @example | |
344 | (split-string "ooo" "o*" t) | |
345 | @result{} nil | |
346 | (split-string "ooo" "\\|o+" t) | |
347 | @result{} ("o" "o" "o") | |
348 | @end example | |
fd6f900c | 349 | |
4bb49a92 EZ |
350 | If you need to split a string into a list of individual command-line |
351 | arguments suitable for @code{call-process} or @code{start-process}, | |
352 | see @ref{Shell Arguments, split-string-and-unquote}. | |
b8d4c8d0 GM |
353 | @end defun |
354 | ||
355 | @defvar split-string-default-separators | |
356 | The default value of @var{separators} for @code{split-string}. Its | |
357 | usual value is @w{@code{"[ \f\t\n\r\v]+"}}. | |
358 | @end defvar | |
359 | ||
360 | @node Modifying Strings | |
361 | @section Modifying Strings | |
362 | ||
363 | The most basic way to alter the contents of an existing string is with | |
364 | @code{aset} (@pxref{Array Functions}). @code{(aset @var{string} | |
365 | @var{idx} @var{char})} stores @var{char} into @var{string} at index | |
366 | @var{idx}. Each character occupies one or more bytes, and if @var{char} | |
367 | needs a different number of bytes from the character already present at | |
368 | that index, @code{aset} signals an error. | |
369 | ||
370 | A more powerful function is @code{store-substring}: | |
371 | ||
372 | @defun store-substring string idx obj | |
373 | This function alters part of the contents of the string @var{string}, by | |
374 | storing @var{obj} starting at index @var{idx}. The argument @var{obj} | |
375 | may be either a character or a (smaller) string. | |
376 | ||
377 | Since it is impossible to change the length of an existing string, it is | |
378 | an error if @var{obj} doesn't fit within @var{string}'s actual length, | |
379 | or if any new character requires a different number of bytes from the | |
380 | character currently present at that point in @var{string}. | |
381 | @end defun | |
382 | ||
383 | To clear out a string that contained a password, use | |
384 | @code{clear-string}: | |
385 | ||
386 | @defun clear-string string | |
387 | This makes @var{string} a unibyte string and clears its contents to | |
388 | zeros. It may also change @var{string}'s length. | |
389 | @end defun | |
390 | ||
391 | @need 2000 | |
392 | @node Text Comparison | |
393 | @section Comparison of Characters and Strings | |
394 | @cindex string equality | |
395 | ||
396 | @defun char-equal character1 character2 | |
397 | This function returns @code{t} if the arguments represent the same | |
398 | character, @code{nil} otherwise. This function ignores differences | |
399 | in case if @code{case-fold-search} is non-@code{nil}. | |
400 | ||
401 | @example | |
402 | (char-equal ?x ?x) | |
403 | @result{} t | |
404 | (let ((case-fold-search nil)) | |
405 | (char-equal ?x ?X)) | |
406 | @result{} nil | |
407 | @end example | |
408 | @end defun | |
409 | ||
410 | @defun string= string1 string2 | |
411 | This function returns @code{t} if the characters of the two strings | |
412 | match exactly. Symbols are also allowed as arguments, in which case | |
413 | their print names are used. | |
414 | Case is always significant, regardless of @code{case-fold-search}. | |
415 | ||
416 | @example | |
417 | (string= "abc" "abc") | |
418 | @result{} t | |
419 | (string= "abc" "ABC") | |
420 | @result{} nil | |
421 | (string= "ab" "ABC") | |
422 | @result{} nil | |
423 | @end example | |
424 | ||
425 | The function @code{string=} ignores the text properties of the two | |
426 | strings. When @code{equal} (@pxref{Equality Predicates}) compares two | |
427 | strings, it uses @code{string=}. | |
428 | ||
429 | For technical reasons, a unibyte and a multibyte string are | |
430 | @code{equal} if and only if they contain the same sequence of | |
431 | character codes and all these codes are either in the range 0 through | |
432 | 127 (@acronym{ASCII}) or 160 through 255 (@code{eight-bit-graphic}). | |
8f88eb24 CY |
433 | However, when a unibyte string is converted to a multibyte string, all |
434 | characters with codes in the range 160 through 255 are converted to | |
435 | characters with higher codes, whereas @acronym{ASCII} characters | |
b8d4c8d0 GM |
436 | remain unchanged. Thus, a unibyte string and its conversion to |
437 | multibyte are only @code{equal} if the string is all @acronym{ASCII}. | |
438 | Character codes 160 through 255 are not entirely proper in multibyte | |
439 | text, even though they can occur. As a consequence, the situation | |
440 | where a unibyte and a multibyte string are @code{equal} without both | |
441 | being all @acronym{ASCII} is a technical oddity that very few Emacs | |
442 | Lisp programmers ever get confronted with. @xref{Text | |
443 | Representations}. | |
444 | @end defun | |
445 | ||
446 | @defun string-equal string1 string2 | |
447 | @code{string-equal} is another name for @code{string=}. | |
448 | @end defun | |
449 | ||
450 | @cindex lexical comparison | |
451 | @defun string< string1 string2 | |
452 | @c (findex string< causes problems for permuted index!!) | |
453 | This function compares two strings a character at a time. It | |
454 | scans both the strings at the same time to find the first pair of corresponding | |
455 | characters that do not match. If the lesser character of these two is | |
456 | the character from @var{string1}, then @var{string1} is less, and this | |
457 | function returns @code{t}. If the lesser character is the one from | |
458 | @var{string2}, then @var{string1} is greater, and this function returns | |
459 | @code{nil}. If the two strings match entirely, the value is @code{nil}. | |
460 | ||
461 | Pairs of characters are compared according to their character codes. | |
462 | Keep in mind that lower case letters have higher numeric values in the | |
463 | @acronym{ASCII} character set than their upper case counterparts; digits and | |
464 | many punctuation characters have a lower numeric value than upper case | |
465 | letters. An @acronym{ASCII} character is less than any non-@acronym{ASCII} | |
466 | character; a unibyte non-@acronym{ASCII} character is always less than any | |
467 | multibyte non-@acronym{ASCII} character (@pxref{Text Representations}). | |
468 | ||
469 | @example | |
470 | @group | |
471 | (string< "abc" "abd") | |
472 | @result{} t | |
473 | (string< "abd" "abc") | |
474 | @result{} nil | |
475 | (string< "123" "abc") | |
476 | @result{} t | |
477 | @end group | |
478 | @end example | |
479 | ||
480 | When the strings have different lengths, and they match up to the | |
481 | length of @var{string1}, then the result is @code{t}. If they match up | |
482 | to the length of @var{string2}, the result is @code{nil}. A string of | |
483 | no characters is less than any other string. | |
484 | ||
485 | @example | |
486 | @group | |
487 | (string< "" "abc") | |
488 | @result{} t | |
489 | (string< "ab" "abc") | |
490 | @result{} t | |
491 | (string< "abc" "") | |
492 | @result{} nil | |
493 | (string< "abc" "ab") | |
494 | @result{} nil | |
495 | (string< "" "") | |
496 | @result{} nil | |
497 | @end group | |
498 | @end example | |
499 | ||
500 | Symbols are also allowed as arguments, in which case their print names | |
501 | are used. | |
502 | @end defun | |
503 | ||
504 | @defun string-lessp string1 string2 | |
505 | @code{string-lessp} is another name for @code{string<}. | |
506 | @end defun | |
507 | ||
508 | @defun compare-strings string1 start1 end1 string2 start2 end2 &optional ignore-case | |
509 | This function compares the specified part of @var{string1} with the | |
510 | specified part of @var{string2}. The specified part of @var{string1} | |
511 | runs from index @var{start1} up to index @var{end1} (@code{nil} means | |
512 | the end of the string). The specified part of @var{string2} runs from | |
513 | index @var{start2} up to index @var{end2} (@code{nil} means the end of | |
514 | the string). | |
515 | ||
516 | The strings are both converted to multibyte for the comparison | |
517 | (@pxref{Text Representations}) so that a unibyte string and its | |
518 | conversion to multibyte are always regarded as equal. If | |
519 | @var{ignore-case} is non-@code{nil}, then case is ignored, so that | |
520 | upper case letters can be equal to lower case letters. | |
521 | ||
522 | If the specified portions of the two strings match, the value is | |
523 | @code{t}. Otherwise, the value is an integer which indicates how many | |
524 | leading characters agree, and which string is less. Its absolute value | |
525 | is one plus the number of characters that agree at the beginning of the | |
526 | two strings. The sign is negative if @var{string1} (or its specified | |
527 | portion) is less. | |
528 | @end defun | |
529 | ||
530 | @defun assoc-string key alist &optional case-fold | |
531 | This function works like @code{assoc}, except that @var{key} must be a | |
532 | string or symbol, and comparison is done using @code{compare-strings}. | |
533 | Symbols are converted to strings before testing. | |
534 | If @var{case-fold} is non-@code{nil}, it ignores case differences. | |
535 | Unlike @code{assoc}, this function can also match elements of the alist | |
536 | that are strings or symbols rather than conses. In particular, @var{alist} can | |
537 | be a list of strings or symbols rather than an actual alist. | |
538 | @xref{Association Lists}. | |
539 | @end defun | |
540 | ||
8f88eb24 | 541 | See also the function @code{compare-buffer-substrings} in |
b8d4c8d0 GM |
542 | @ref{Comparing Text}, for a way to compare text in buffers. The |
543 | function @code{string-match}, which matches a regular expression | |
544 | against a string, can be used for a kind of string comparison; see | |
545 | @ref{Regexp Search}. | |
546 | ||
547 | @node String Conversion | |
548 | @comment node-name, next, previous, up | |
549 | @section Conversion of Characters and Strings | |
550 | @cindex conversion of strings | |
551 | ||
8f88eb24 CY |
552 | This section describes functions for converting between characters, |
553 | strings and integers. @code{format} (@pxref{Formatting Strings}) and | |
554 | @code{prin1-to-string} (@pxref{Output Functions}) can also convert | |
555 | Lisp objects into strings. @code{read-from-string} (@pxref{Input | |
556 | Functions}) can ``convert'' a string representation of a Lisp object | |
e4021ec1 SM |
557 | into an object. The functions @code{string-to-multibyte} and |
558 | @code{string-to-unibyte} convert the text representation of a string | |
8f88eb24 | 559 | (@pxref{Converting Representations}). |
b8d4c8d0 GM |
560 | |
561 | @xref{Documentation}, for functions that produce textual descriptions | |
562 | of text characters and general input events | |
563 | (@code{single-key-description} and @code{text-char-description}). These | |
564 | are used primarily for making help messages. | |
565 | ||
b8d4c8d0 GM |
566 | @defun number-to-string number |
567 | @cindex integer to string | |
568 | @cindex integer to decimal | |
569 | This function returns a string consisting of the printed base-ten | |
570 | representation of @var{number}, which may be an integer or a floating | |
571 | point number. The returned value starts with a minus sign if the argument is | |
572 | negative. | |
573 | ||
574 | @example | |
575 | (number-to-string 256) | |
576 | @result{} "256" | |
577 | @group | |
578 | (number-to-string -23) | |
579 | @result{} "-23" | |
580 | @end group | |
581 | (number-to-string -23.5) | |
582 | @result{} "-23.5" | |
583 | @end example | |
584 | ||
585 | @cindex int-to-string | |
586 | @code{int-to-string} is a semi-obsolete alias for this function. | |
587 | ||
588 | See also the function @code{format} in @ref{Formatting Strings}. | |
589 | @end defun | |
590 | ||
591 | @defun string-to-number string &optional base | |
592 | @cindex string to number | |
593 | This function returns the numeric value of the characters in | |
594 | @var{string}. If @var{base} is non-@code{nil}, it must be an integer | |
595 | between 2 and 16 (inclusive), and integers are converted in that base. | |
596 | If @var{base} is @code{nil}, then base ten is used. Floating point | |
597 | conversion only works in base ten; we have not implemented other | |
598 | radices for floating point numbers, because that would be much more | |
599 | work and does not seem useful. If @var{string} looks like an integer | |
600 | but its value is too large to fit into a Lisp integer, | |
601 | @code{string-to-number} returns a floating point result. | |
602 | ||
603 | The parsing skips spaces and tabs at the beginning of @var{string}, | |
604 | then reads as much of @var{string} as it can interpret as a number in | |
605 | the given base. (On some systems it ignores other whitespace at the | |
606 | beginning, not just spaces and tabs.) If the first character after | |
607 | the ignored whitespace is neither a digit in the given base, nor a | |
608 | plus or minus sign, nor the leading dot of a floating point number, | |
609 | this function returns 0. | |
610 | ||
611 | @example | |
612 | (string-to-number "256") | |
613 | @result{} 256 | |
614 | (string-to-number "25 is a perfect square.") | |
615 | @result{} 25 | |
616 | (string-to-number "X256") | |
617 | @result{} 0 | |
618 | (string-to-number "-4.5") | |
619 | @result{} -4.5 | |
620 | (string-to-number "1e5") | |
621 | @result{} 100000.0 | |
622 | @end example | |
623 | ||
624 | @findex string-to-int | |
625 | @code{string-to-int} is an obsolete alias for this function. | |
3e99b825 CY |
626 | @end defun |
627 | ||
628 | @defun char-to-string character | |
629 | @cindex character to string | |
630 | This function returns a new string containing one character, | |
631 | @var{character}. This function is semi-obsolete because the function | |
632 | @code{string} is more general. @xref{Creating Strings}. | |
633 | @end defun | |
634 | ||
635 | @defun string-to-char string | |
636 | This function returns the first character in @var{string}. This | |
637 | mostly identical to @code{(aref string 0)}, except that it returns 0 | |
638 | if the string is empty. (The value is also 0 when the first character | |
639 | of @var{string} is the null character, @acronym{ASCII} code 0.) This | |
640 | function may be eliminated in the future if it does not seem useful | |
641 | enough to retain. | |
b8d4c8d0 GM |
642 | @end defun |
643 | ||
644 | Here are some other functions that can convert to or from a string: | |
645 | ||
646 | @table @code | |
647 | @item concat | |
3e99b825 | 648 | This function converts a vector or a list into a string. |
b8d4c8d0 GM |
649 | @xref{Creating Strings}. |
650 | ||
651 | @item vconcat | |
3e99b825 | 652 | This function converts a string into a vector. @xref{Vector |
b8d4c8d0 GM |
653 | Functions}. |
654 | ||
655 | @item append | |
3e99b825 CY |
656 | This function converts a string into a list. @xref{Building Lists}. |
657 | ||
658 | @item byte-to-string | |
659 | This function converts a byte of character data into a unibyte string. | |
660 | @xref{Converting Representations}. | |
b8d4c8d0 GM |
661 | @end table |
662 | ||
663 | @node Formatting Strings | |
664 | @comment node-name, next, previous, up | |
665 | @section Formatting Strings | |
666 | @cindex formatting strings | |
667 | @cindex strings, formatting them | |
668 | ||
8f88eb24 CY |
669 | @dfn{Formatting} means constructing a string by substituting |
670 | computed values at various places in a constant string. This constant | |
671 | string controls how the other values are printed, as well as where | |
672 | they appear; it is called a @dfn{format string}. | |
b8d4c8d0 GM |
673 | |
674 | Formatting is often useful for computing messages to be displayed. In | |
675 | fact, the functions @code{message} and @code{error} provide the same | |
676 | formatting feature described here; they differ from @code{format} only | |
677 | in how they use the result of formatting. | |
678 | ||
679 | @defun format string &rest objects | |
680 | This function returns a new string that is made by copying | |
681 | @var{string} and then replacing any format specification | |
682 | in the copy with encodings of the corresponding @var{objects}. The | |
683 | arguments @var{objects} are the computed values to be formatted. | |
684 | ||
685 | The characters in @var{string}, other than the format specifications, | |
686 | are copied directly into the output, including their text properties, | |
687 | if any. | |
688 | @end defun | |
689 | ||
690 | @cindex @samp{%} in format | |
691 | @cindex format specification | |
692 | A format specification is a sequence of characters beginning with a | |
693 | @samp{%}. Thus, if there is a @samp{%d} in @var{string}, the | |
694 | @code{format} function replaces it with the printed representation of | |
695 | one of the values to be formatted (one of the arguments @var{objects}). | |
696 | For example: | |
697 | ||
698 | @example | |
699 | @group | |
700 | (format "The value of fill-column is %d." fill-column) | |
701 | @result{} "The value of fill-column is 72." | |
702 | @end group | |
703 | @end example | |
704 | ||
705 | Since @code{format} interprets @samp{%} characters as format | |
706 | specifications, you should @emph{never} pass an arbitrary string as | |
707 | the first argument. This is particularly true when the string is | |
708 | generated by some Lisp code. Unless the string is @emph{known} to | |
709 | never include any @samp{%} characters, pass @code{"%s"}, described | |
710 | below, as the first argument, and the string as the second, like this: | |
711 | ||
712 | @example | |
713 | (format "%s" @var{arbitrary-string}) | |
714 | @end example | |
715 | ||
716 | If @var{string} contains more than one format specification, the | |
717 | format specifications correspond to successive values from | |
718 | @var{objects}. Thus, the first format specification in @var{string} | |
719 | uses the first such value, the second format specification uses the | |
720 | second such value, and so on. Any extra format specifications (those | |
721 | for which there are no corresponding values) cause an error. Any | |
722 | extra values to be formatted are ignored. | |
723 | ||
724 | Certain format specifications require values of particular types. If | |
725 | you supply a value that doesn't fit the requirements, an error is | |
726 | signaled. | |
727 | ||
728 | Here is a table of valid format specifications: | |
729 | ||
730 | @table @samp | |
731 | @item %s | |
732 | Replace the specification with the printed representation of the object, | |
733 | made without quoting (that is, using @code{princ}, not | |
734 | @code{prin1}---@pxref{Output Functions}). Thus, strings are represented | |
735 | by their contents alone, with no @samp{"} characters, and symbols appear | |
736 | without @samp{\} characters. | |
737 | ||
738 | If the object is a string, its text properties are | |
739 | copied into the output. The text properties of the @samp{%s} itself | |
740 | are also copied, but those of the object take priority. | |
741 | ||
742 | @item %S | |
743 | Replace the specification with the printed representation of the object, | |
744 | made with quoting (that is, using @code{prin1}---@pxref{Output | |
745 | Functions}). Thus, strings are enclosed in @samp{"} characters, and | |
746 | @samp{\} characters appear where necessary before special characters. | |
747 | ||
748 | @item %o | |
749 | @cindex integer to octal | |
750 | Replace the specification with the base-eight representation of an | |
751 | integer. | |
752 | ||
753 | @item %d | |
754 | Replace the specification with the base-ten representation of an | |
755 | integer. | |
756 | ||
757 | @item %x | |
758 | @itemx %X | |
759 | @cindex integer to hexadecimal | |
760 | Replace the specification with the base-sixteen representation of an | |
761 | integer. @samp{%x} uses lower case and @samp{%X} uses upper case. | |
762 | ||
763 | @item %c | |
764 | Replace the specification with the character which is the value given. | |
765 | ||
766 | @item %e | |
767 | Replace the specification with the exponential notation for a floating | |
768 | point number. | |
769 | ||
770 | @item %f | |
771 | Replace the specification with the decimal-point notation for a floating | |
772 | point number. | |
773 | ||
774 | @item %g | |
775 | Replace the specification with notation for a floating point number, | |
776 | using either exponential notation or decimal-point notation, whichever | |
777 | is shorter. | |
778 | ||
779 | @item %% | |
780 | Replace the specification with a single @samp{%}. This format | |
781 | specification is unusual in that it does not use a value. For example, | |
782 | @code{(format "%% %d" 30)} returns @code{"% 30"}. | |
783 | @end table | |
784 | ||
785 | Any other format character results in an @samp{Invalid format | |
786 | operation} error. | |
787 | ||
788 | Here are several examples: | |
789 | ||
790 | @example | |
791 | @group | |
792 | (format "The name of this buffer is %s." (buffer-name)) | |
793 | @result{} "The name of this buffer is strings.texi." | |
794 | ||
795 | (format "The buffer object prints as %s." (current-buffer)) | |
796 | @result{} "The buffer object prints as strings.texi." | |
797 | ||
798 | (format "The octal value of %d is %o, | |
799 | and the hex value is %x." 18 18 18) | |
800 | @result{} "The octal value of 18 is 22, | |
801 | and the hex value is 12." | |
802 | @end group | |
803 | @end example | |
804 | ||
805 | @cindex field width | |
806 | @cindex padding | |
b20e7c7d CY |
807 | A specification can have a @dfn{width}, which is a decimal number |
808 | between the @samp{%} and the specification character. If the printed | |
809 | representation of the object contains fewer characters than this | |
810 | width, @code{format} extends it with padding. The width specifier is | |
811 | ignored for the @samp{%%} specification. Any padding introduced by | |
812 | the width specifier normally consists of spaces inserted on the left: | |
b8d4c8d0 GM |
813 | |
814 | @example | |
b20e7c7d CY |
815 | (format "%5d is padded on the left with spaces" 123) |
816 | @result{} " 123 is padded on the left with spaces" | |
b8d4c8d0 GM |
817 | @end example |
818 | ||
819 | @noindent | |
820 | If the width is too small, @code{format} does not truncate the | |
821 | object's printed representation. Thus, you can use a width to specify | |
822 | a minimum spacing between columns with no risk of losing information. | |
b20e7c7d CY |
823 | In the following three examples, @samp{%7s} specifies a minimum width |
824 | of 7. In the first case, the string inserted in place of @samp{%7s} | |
825 | has only 3 letters, and needs 4 blank spaces as padding. In the | |
826 | second case, the string @code{"specification"} is 13 letters wide but | |
827 | is not truncated. | |
b8d4c8d0 | 828 | |
b20e7c7d | 829 | @example |
b8d4c8d0 | 830 | @group |
049bcbcb | 831 | (format "The word `%7s' has %d letters in it." |
b8d4c8d0 | 832 | "foo" (length "foo")) |
049bcbcb CY |
833 | @result{} "The word ` foo' has 3 letters in it." |
834 | (format "The word `%7s' has %d letters in it." | |
b8d4c8d0 | 835 | "specification" (length "specification")) |
049bcbcb | 836 | @result{} "The word `specification' has 13 letters in it." |
b8d4c8d0 | 837 | @end group |
b20e7c7d CY |
838 | @end example |
839 | ||
840 | @cindex flags in format specifications | |
841 | Immediately after the @samp{%} and before the optional width | |
842 | specifier, you can also put certain @dfn{flag characters}. | |
843 | ||
844 | The flag @samp{+} inserts a plus sign before a positive number, so | |
845 | that it always has a sign. A space character as flag inserts a space | |
846 | before a positive number. (Otherwise, positive numbers start with the | |
847 | first digit.) These flags are useful for ensuring that positive | |
848 | numbers and negative numbers use the same number of columns. They are | |
849 | ignored except for @samp{%d}, @samp{%e}, @samp{%f}, @samp{%g}, and if | |
850 | both flags are used, @samp{+} takes precedence. | |
851 | ||
852 | The flag @samp{#} specifies an ``alternate form'' which depends on | |
853 | the format in use. For @samp{%o}, it ensures that the result begins | |
854 | with a @samp{0}. For @samp{%x} and @samp{%X}, it prefixes the result | |
855 | with @samp{0x} or @samp{0X}. For @samp{%e}, @samp{%f}, and @samp{%g}, | |
856 | the @samp{#} flag means include a decimal point even if the precision | |
857 | is zero. | |
858 | ||
a9ab721e LMI |
859 | The flag @samp{0} ensures that the padding consists of @samp{0} |
860 | characters instead of spaces. This flag is ignored for non-numerical | |
861 | specification characters like @samp{%s}, @samp{%S} and @samp{%c}. | |
862 | These specification characters accept the @samp{0} flag, but still pad | |
863 | with @emph{spaces}. | |
864 | ||
b20e7c7d CY |
865 | The flag @samp{-} causes the padding inserted by the width |
866 | specifier, if any, to be inserted on the right rather than the left. | |
a9ab721e LMI |
867 | If both @samp{-} and @samp{0} are present, the @samp{0} flag is |
868 | ignored. | |
b8d4c8d0 | 869 | |
b20e7c7d | 870 | @example |
b8d4c8d0 | 871 | @group |
b20e7c7d CY |
872 | (format "%06d is padded on the left with zeros" 123) |
873 | @result{} "000123 is padded on the left with zeros" | |
874 | ||
875 | (format "%-6d is padded on the right" 123) | |
876 | @result{} "123 is padded on the right" | |
877 | ||
b8d4c8d0 GM |
878 | (format "The word `%-7s' actually has %d letters in it." |
879 | "foo" (length "foo")) | |
880 | @result{} "The word `foo ' actually has 3 letters in it." | |
881 | @end group | |
b20e7c7d | 882 | @end example |
b8d4c8d0 GM |
883 | |
884 | @cindex precision in format specifications | |
885 | All the specification characters allow an optional @dfn{precision} | |
886 | before the character (after the width, if present). The precision is | |
887 | a decimal-point @samp{.} followed by a digit-string. For the | |
888 | floating-point specifications (@samp{%e}, @samp{%f}, @samp{%g}), the | |
889 | precision specifies how many decimal places to show; if zero, the | |
890 | decimal-point itself is also omitted. For @samp{%s} and @samp{%S}, | |
891 | the precision truncates the string to the given width, so @samp{%.3s} | |
892 | shows only the first three characters of the representation for | |
893 | @var{object}. Precision has no effect for other specification | |
894 | characters. | |
895 | ||
b8d4c8d0 GM |
896 | @node Case Conversion |
897 | @comment node-name, next, previous, up | |
898 | @section Case Conversion in Lisp | |
899 | @cindex upper case | |
900 | @cindex lower case | |
901 | @cindex character case | |
902 | @cindex case conversion in Lisp | |
903 | ||
904 | The character case functions change the case of single characters or | |
905 | of the contents of strings. The functions normally convert only | |
906 | alphabetic characters (the letters @samp{A} through @samp{Z} and | |
907 | @samp{a} through @samp{z}, as well as non-@acronym{ASCII} letters); other | |
908 | characters are not altered. You can specify a different case | |
909 | conversion mapping by specifying a case table (@pxref{Case Tables}). | |
910 | ||
911 | These functions do not modify the strings that are passed to them as | |
912 | arguments. | |
913 | ||
914 | The examples below use the characters @samp{X} and @samp{x} which have | |
915 | @acronym{ASCII} codes 88 and 120 respectively. | |
916 | ||
917 | @defun downcase string-or-char | |
8f88eb24 CY |
918 | This function converts @var{string-or-char}, which should be either a |
919 | character or a string, to lower case. | |
b8d4c8d0 | 920 | |
8f88eb24 CY |
921 | When @var{string-or-char} is a string, this function returns a new |
922 | string in which each letter in the argument that is upper case is | |
923 | converted to lower case. When @var{string-or-char} is a character, | |
924 | this function returns the corresponding lower case character (an | |
925 | integer); if the original character is lower case, or is not a letter, | |
926 | the return value is equal to the original character. | |
b8d4c8d0 GM |
927 | |
928 | @example | |
929 | (downcase "The cat in the hat") | |
930 | @result{} "the cat in the hat" | |
931 | ||
932 | (downcase ?X) | |
933 | @result{} 120 | |
934 | @end example | |
935 | @end defun | |
936 | ||
937 | @defun upcase string-or-char | |
8f88eb24 CY |
938 | This function converts @var{string-or-char}, which should be either a |
939 | character or a string, to upper case. | |
b8d4c8d0 | 940 | |
8f88eb24 CY |
941 | When @var{string-or-char} is a string, this function returns a new |
942 | string in which each letter in the argument that is lower case is | |
943 | converted to upper case. When @var{string-or-char} is a character, | |
a86cd395 | 944 | this function returns the corresponding upper case character (an |
8f88eb24 CY |
945 | integer); if the original character is upper case, or is not a letter, |
946 | the return value is equal to the original character. | |
b8d4c8d0 GM |
947 | |
948 | @example | |
949 | (upcase "The cat in the hat") | |
950 | @result{} "THE CAT IN THE HAT" | |
951 | ||
952 | (upcase ?x) | |
953 | @result{} 88 | |
954 | @end example | |
955 | @end defun | |
956 | ||
957 | @defun capitalize string-or-char | |
958 | @cindex capitalization | |
959 | This function capitalizes strings or characters. If | |
8f88eb24 CY |
960 | @var{string-or-char} is a string, the function returns a new string |
961 | whose contents are a copy of @var{string-or-char} in which each word | |
962 | has been capitalized. This means that the first character of each | |
b8d4c8d0 GM |
963 | word is converted to upper case, and the rest are converted to lower |
964 | case. | |
965 | ||
966 | The definition of a word is any sequence of consecutive characters that | |
967 | are assigned to the word constituent syntax class in the current syntax | |
968 | table (@pxref{Syntax Class Table}). | |
969 | ||
8f88eb24 CY |
970 | When @var{string-or-char} is a character, this function does the same |
971 | thing as @code{upcase}. | |
b8d4c8d0 GM |
972 | |
973 | @example | |
974 | @group | |
975 | (capitalize "The cat in the hat") | |
976 | @result{} "The Cat In The Hat" | |
977 | @end group | |
978 | ||
979 | @group | |
980 | (capitalize "THE 77TH-HATTED CAT") | |
981 | @result{} "The 77th-Hatted Cat" | |
982 | @end group | |
983 | ||
984 | @group | |
985 | (capitalize ?x) | |
986 | @result{} 88 | |
987 | @end group | |
988 | @end example | |
989 | @end defun | |
990 | ||
991 | @defun upcase-initials string-or-char | |
992 | If @var{string-or-char} is a string, this function capitalizes the | |
993 | initials of the words in @var{string-or-char}, without altering any | |
994 | letters other than the initials. It returns a new string whose | |
995 | contents are a copy of @var{string-or-char}, in which each word has | |
996 | had its initial letter converted to upper case. | |
997 | ||
998 | The definition of a word is any sequence of consecutive characters that | |
999 | are assigned to the word constituent syntax class in the current syntax | |
1000 | table (@pxref{Syntax Class Table}). | |
1001 | ||
1002 | When the argument to @code{upcase-initials} is a character, | |
1003 | @code{upcase-initials} has the same result as @code{upcase}. | |
1004 | ||
1005 | @example | |
1006 | @group | |
1007 | (upcase-initials "The CAT in the hAt") | |
1008 | @result{} "The CAT In The HAt" | |
1009 | @end group | |
1010 | @end example | |
1011 | @end defun | |
1012 | ||
1013 | @xref{Text Comparison}, for functions that compare strings; some of | |
1014 | them ignore case differences, or can optionally ignore case differences. | |
1015 | ||
1016 | @node Case Tables | |
1017 | @section The Case Table | |
1018 | ||
1019 | You can customize case conversion by installing a special @dfn{case | |
1020 | table}. A case table specifies the mapping between upper case and lower | |
1021 | case letters. It affects both the case conversion functions for Lisp | |
1022 | objects (see the previous section) and those that apply to text in the | |
1023 | buffer (@pxref{Case Changes}). Each buffer has a case table; there is | |
1024 | also a standard case table which is used to initialize the case table | |
1025 | of new buffers. | |
1026 | ||
1027 | A case table is a char-table (@pxref{Char-Tables}) whose subtype is | |
1028 | @code{case-table}. This char-table maps each character into the | |
1029 | corresponding lower case character. It has three extra slots, which | |
1030 | hold related tables: | |
1031 | ||
1032 | @table @var | |
1033 | @item upcase | |
1034 | The upcase table maps each character into the corresponding upper | |
1035 | case character. | |
1036 | @item canonicalize | |
1037 | The canonicalize table maps all of a set of case-related characters | |
1038 | into a particular member of that set. | |
1039 | @item equivalences | |
1040 | The equivalences table maps each one of a set of case-related characters | |
1041 | into the next character in that set. | |
1042 | @end table | |
1043 | ||
1044 | In simple cases, all you need to specify is the mapping to lower-case; | |
1045 | the three related tables will be calculated automatically from that one. | |
1046 | ||
1047 | For some languages, upper and lower case letters are not in one-to-one | |
1048 | correspondence. There may be two different lower case letters with the | |
1049 | same upper case equivalent. In these cases, you need to specify the | |
1050 | maps for both lower case and upper case. | |
1051 | ||
1052 | The extra table @var{canonicalize} maps each character to a canonical | |
1053 | equivalent; any two characters that are related by case-conversion have | |
1054 | the same canonical equivalent character. For example, since @samp{a} | |
1055 | and @samp{A} are related by case-conversion, they should have the same | |
1056 | canonical equivalent character (which should be either @samp{a} for both | |
1057 | of them, or @samp{A} for both of them). | |
1058 | ||
1059 | The extra table @var{equivalences} is a map that cyclically permutes | |
1060 | each equivalence class (of characters with the same canonical | |
1061 | equivalent). (For ordinary @acronym{ASCII}, this would map @samp{a} into | |
1062 | @samp{A} and @samp{A} into @samp{a}, and likewise for each set of | |
1063 | equivalent characters.) | |
1064 | ||
8f88eb24 | 1065 | When constructing a case table, you can provide @code{nil} for |
b8d4c8d0 GM |
1066 | @var{canonicalize}; then Emacs fills in this slot from the lower case |
1067 | and upper case mappings. You can also provide @code{nil} for | |
1068 | @var{equivalences}; then Emacs fills in this slot from | |
1069 | @var{canonicalize}. In a case table that is actually in use, those | |
8f88eb24 CY |
1070 | components are non-@code{nil}. Do not try to specify |
1071 | @var{equivalences} without also specifying @var{canonicalize}. | |
b8d4c8d0 GM |
1072 | |
1073 | Here are the functions for working with case tables: | |
1074 | ||
1075 | @defun case-table-p object | |
1076 | This predicate returns non-@code{nil} if @var{object} is a valid case | |
1077 | table. | |
1078 | @end defun | |
1079 | ||
1080 | @defun set-standard-case-table table | |
1081 | This function makes @var{table} the standard case table, so that it will | |
1082 | be used in any buffers created subsequently. | |
1083 | @end defun | |
1084 | ||
1085 | @defun standard-case-table | |
1086 | This returns the standard case table. | |
1087 | @end defun | |
1088 | ||
1089 | @defun current-case-table | |
1090 | This function returns the current buffer's case table. | |
1091 | @end defun | |
1092 | ||
1093 | @defun set-case-table table | |
1094 | This sets the current buffer's case table to @var{table}. | |
1095 | @end defun | |
1096 | ||
1097 | @defmac with-case-table table body@dots{} | |
1098 | The @code{with-case-table} macro saves the current case table, makes | |
1099 | @var{table} the current case table, evaluates the @var{body} forms, | |
1100 | and finally restores the case table. The return value is the value of | |
1101 | the last form in @var{body}. The case table is restored even in case | |
1102 | of an abnormal exit via @code{throw} or error (@pxref{Nonlocal | |
1103 | Exits}). | |
1104 | @end defmac | |
1105 | ||
8f88eb24 | 1106 | Some language environments modify the case conversions of |
b8d4c8d0 GM |
1107 | @acronym{ASCII} characters; for example, in the Turkish language |
1108 | environment, the @acronym{ASCII} character @samp{I} is downcased into | |
1109 | a Turkish ``dotless i''. This can interfere with code that requires | |
1110 | ordinary ASCII case conversion, such as implementations of | |
1111 | @acronym{ASCII}-based network protocols. In that case, use the | |
1112 | @code{with-case-table} macro with the variable @var{ascii-case-table}, | |
1113 | which stores the unmodified case table for the @acronym{ASCII} | |
1114 | character set. | |
1115 | ||
1116 | @defvar ascii-case-table | |
1117 | The case table for the @acronym{ASCII} character set. This should not be | |
1118 | modified by any language environment settings. | |
1119 | @end defvar | |
1120 | ||
1121 | The following three functions are convenient subroutines for packages | |
1122 | that define non-@acronym{ASCII} character sets. They modify the specified | |
1123 | case table @var{case-table}; they also modify the standard syntax table. | |
1124 | @xref{Syntax Tables}. Normally you would use these functions to change | |
1125 | the standard case table. | |
1126 | ||
1127 | @defun set-case-syntax-pair uc lc case-table | |
1128 | This function specifies a pair of corresponding letters, one upper case | |
1129 | and one lower case. | |
1130 | @end defun | |
1131 | ||
1132 | @defun set-case-syntax-delims l r case-table | |
1133 | This function makes characters @var{l} and @var{r} a matching pair of | |
1134 | case-invariant delimiters. | |
1135 | @end defun | |
1136 | ||
1137 | @defun set-case-syntax char syntax case-table | |
1138 | This function makes @var{char} case-invariant, with syntax | |
1139 | @var{syntax}. | |
1140 | @end defun | |
1141 | ||
1142 | @deffn Command describe-buffer-case-table | |
1143 | This command displays a description of the contents of the current | |
1144 | buffer's case table. | |
1145 | @end deffn |