Mercurial > hg > xemacs-beta
diff etc/NEWS @ 422:95016f13131a r21-2-19
Import from CVS: tag r21-2-19
author | cvs |
---|---|
date | Mon, 13 Aug 2007 11:25:01 +0200 |
parents | 41dbb7a9d5f2 |
children | 11054d720c21 |
line wrap: on
line diff
--- a/etc/NEWS Mon Aug 13 11:24:10 2007 +0200 +++ b/etc/NEWS Mon Aug 13 11:25:01 2007 +0200 @@ -33,6 +33,26 @@ * Changes in XEmacs 21.2 ======================== +** The functions in rect.el have been almost completely rewritten... +to avoid inserting undesirable spaces, notably at the end of lines. +Two typical examples of this old behavior are `string-rectangle', which filled +all lines up to the right side of the rectangle, and `clear-rectangle', which +filled even empty lines up to the left side. + +This is not the case any more. All these functions have been rewritten to +avoid inserting unwanted spaces, and an optional prefix now allows them to +behave the old way. + +As a side effect, `move-to-column' now also accepts 'coerce as its second +argument, meaning that the line shouldn't be filled if its too short to reach +the desired column. + +** You can now customize and save comments for faces and variables. + +In Custom buffers, a new menu entry allows you to add and edit a comment. +Comments for variables can also be assigned by calling +`customize-set-(value|variable)' with a prefix argument. + ** XEmacs now locates the early package hierarchy at ~/.xemacs/packages. This has changed from simply ~/.xemacs. @@ -45,11 +65,11 @@ backward. If set to non-nil, the "Delete" key will delete forward, except on keyboards where a "Backspace" key is not provided. -Unless our implementation has bugs, the only reason why you would want +Unless our implementation has bugs, the only reason why you would want to set `delete-key-deletes-forward' to nil is if you want to use the Delete key to delete backwards, despite the presence (according to Xlib) of a BackSpace key on the keyboard. - + ** Interactive searching and matching case improvements. Case sensitiveness in searching operations is normally controlled by @@ -57,7 +77,7 @@ searching). This mechanism has now been slightly improved for interactive searches: if the search string (or regexp) contains uppercase characters, the searching is forced to be case-sensitive, -`case-fold-search'. +`case-fold-search'. The new behavior affects all functions performing interactive searches, like `zap-to-char', `list-matching-lines', `tags-search'