Mercurial > hg > xemacs-beta
comparison etc/NEWS @ 414:da8ed4261e83 r21-2-15
Import from CVS: tag r21-2-15
author | cvs |
---|---|
date | Mon, 13 Aug 2007 11:21:38 +0200 |
parents | 697ef44129c6 |
children | e804706bfb8c |
comparison
equal
deleted
inserted
replaced
413:901169e5ca31 | 414:da8ed4261e83 |
---|---|
83 ** User names following the tilde character can now be completed at | 83 ** User names following the tilde character can now be completed at |
84 file name prompts; e.g. `C-x C-f ~hni<TAB>' will complete to | 84 file name prompts; e.g. `C-x C-f ~hni<TAB>' will complete to |
85 `~hniksic/'. To make this operation faster, a cache of user names is | 85 `~hniksic/'. To make this operation faster, a cache of user names is |
86 maintained internally. | 86 maintained internally. |
87 | 87 |
88 The new primitives available for this purpose are functions named | |
89 `user-name-completion' and `user-name-all-completions'. | |
90 | |
88 | 91 |
89 * Lisp and internal changes in XEmacs 21.2 | 92 * Lisp and internal changes in XEmacs 21.2 |
90 ========================================== | 93 ========================================== |
91 | 94 |
92 ** Much effort has been invested to make XEmacs Lisp faster: | 95 ** Much effort has been invested to make XEmacs Lisp faster: |
173 supported) instead of an integer code. See the documentation for | 176 supported) instead of an integer code. See the documentation for |
174 details. | 177 details. |
175 | 178 |
176 Of course, the old form is still accepted for backward compatibility. | 179 Of course, the old form is still accepted for backward compatibility. |
177 | 180 |
181 ** `translate-region' has been improved in several ways. Its TABLE | |
182 argument used to be a 256-character string. In addition to this, it | |
183 can now also be a vector or a char-table (which is useful for Mule.) | |
184 If TABLE a vector or a generic char-table, you can map characters to | |
185 strings instead of to other characters. For instance: | |
186 | |
187 (let ((table (make-char-table 'generic))) | |
188 (put-char-table ?a "the letter a" table) | |
189 (put-char-table ?b "" table) | |
190 (put-char-table ?c ?\n table) | |
191 (translate-region (point-min) (point-max) table)) | |
192 | |
178 ** The `keywordp' function now returns non-nil only on symbols | 193 ** The `keywordp' function now returns non-nil only on symbols |
179 interned in the global obarray. For example: | 194 interned in the global obarray. For example: |
180 | 195 |
181 (keywordp (intern ":foo" [0])) | 196 (keywordp (intern ":foo" [0])) |
182 => nil | 197 => nil |
183 (keywordp (intern ":foo")) ; The same as (keywordp :foo) | 198 (keywordp (intern ":foo")) ; The same as (keywordp :foo) |
184 => t | 199 => t |
185 | 200 |
186 This behaviour is compatible with other code which treats symbols | 201 This behaviour is compatible with other code which treats symbols |
187 beginning with colon as keywords only if they are interned in the | 202 beginning with colon as keywords only if they are interned in the |
188 global obarray. `keyword' used to wrongly return t in both cases | 203 global obarray. `keywordp' used to wrongly return t in both cases |
189 above. | 204 above. |
190 | 205 |
191 ** The first argument to `intern-soft' may now also be a symbol, like | 206 ** The first argument to `intern-soft' may now also be a symbol, like |
192 with `unintern'. If given a symbol, `intern-soft' will look for that | 207 with `unintern'. If given a symbol, `intern-soft' will look for that |
193 exact symbol rather than for any string. This is useful when you want | 208 exact symbol rather than for any string. This is useful when you want |