Mercurial > hg > xemacs-beta
comparison etc/NEWS @ 116:9f59509498e1 r20-1b10
Import from CVS: tag r20-1b10
author | cvs |
---|---|
date | Mon, 13 Aug 2007 09:23:06 +0200 |
parents | cf808b4c4290 |
children | 9b50b4588a93 |
comparison
equal
deleted
inserted
replaced
115:f109f7dabbe2 | 116:9f59509498e1 |
---|---|
18 | 18 |
19 XEmacs Release Notes........details of the changes between releases | 19 XEmacs Release Notes........details of the changes between releases |
20 | 20 |
21 New users should look at the next section on "Using Outline Mode". You will | 21 New users should look at the next section on "Using Outline Mode". You will |
22 be more efficient when you can navigate quickly through this file. Users | 22 be more efficient when you can navigate quickly through this file. Users |
23 interested in some of the details of how XEmacs differs from FSF GNU Emacs | 23 interested in some of the details of how XEmacs differs from GNU Emacs |
24 should read the section "What's Different?". Users who would to know which | 24 should read the section "What's Different?". Users who would to know which |
25 capabilities have been introduced in each release should look at the | 25 capabilities have been introduced in each release should look at the |
26 appropriate subsection of the "XEmacs Release Notes." | 26 appropriate subsection of the "XEmacs Release Notes." |
27 | 27 |
28 N.B. The term "FSF GNU Emacs" refers to any release of Emacs Version 19 | 28 N.B. The term "FSF GNU Emacs" refers to any release of Emacs Version 19 |
101 | 101 |
102 * What's Different? | 102 * What's Different? |
103 =================== | 103 =================== |
104 | 104 |
105 | 105 |
106 ** Differences between XEmacs and FSF GNU Emacs 19 | 106 ** Differences between XEmacs and GNU Emacs 19 |
107 ================================================== | 107 ================================================== |
108 In XEmacs 20, characters are first-class objects. Characters can be | 108 In XEmacs 20, characters are first-class objects. Characters can be |
109 converted to integers, but are not integers. FSF 19, XEmacs 19, and Mule | 109 converted to integers, but are not integers. FSF 19, XEmacs 19, and Mule |
110 represent them as integers. | 110 represent them as integers. |
111 | 111 |
114 ancient ASCII code used to represent a particular overlapping subset of them. | 114 ancient ASCII code used to represent a particular overlapping subset of them. |
115 | 115 |
116 In XEmacs, keymaps are first-class opaque objects. FSF 19 represents them as | 116 In XEmacs, keymaps are first-class opaque objects. FSF 19 represents them as |
117 complicated combinations of association lists and vectors. If you use the | 117 complicated combinations of association lists and vectors. If you use the |
118 advertised functional interface to manipulation of keymaps, the same code | 118 advertised functional interface to manipulation of keymaps, the same code |
119 will work in XEmacs, Emacs 18, and FSF GNU Emacs 19; if your code depends | 119 will work in XEmacs, Emacs 18, and GNU Emacs 19; if your code depends |
120 on the underlying implementation of keymaps, it will not. | 120 on the underlying implementation of keymaps, it will not. |
121 | 121 |
122 XEmacs uses "extents" to represent all non-textual aspects of buffers; | 122 XEmacs uses "extents" to represent all non-textual aspects of buffers; |
123 FSF 19 uses two distinct objects, "text properties" and "overlays", | 123 FSF 19 uses two distinct objects, "text properties" and "overlays", |
124 which divide up the functionality between them. Extents are a | 124 which divide up the functionality between them. Extents are a |
1584 and `end-closed' now work correctly w.r.t. text properties. | 1584 and `end-closed' now work correctly w.r.t. text properties. |
1585 | 1585 |
1586 -- The `face' property of extents and text properties can now | 1586 -- The `face' property of extents and text properties can now |
1587 be a list. | 1587 be a list. |
1588 | 1588 |
1589 -- The `mouse-face' property from FSF GNU Emacs is now supported. | 1589 -- The `mouse-face' property from GNU Emacs is now supported. |
1590 It supersedes the `highlight' property. | 1590 It supersedes the `highlight' property. |
1591 | 1591 |
1592 -- `enriched' and `facemenu' packages from FSF GNU Emacs have been ported. | 1592 -- `enriched' and `facemenu' packages from GNU Emacs have been ported. |
1593 | 1593 |
1594 -- New functions for easier creation of dialog boxes: | 1594 -- New functions for easier creation of dialog boxes: |
1595 `get-dialog-box-response', `message-box', and `message-or-box'. | 1595 `get-dialog-box-response', `message-box', and `message-or-box'. |
1596 | 1596 |
1597 -- `function-min-args' and `function-max-args' allow you to determine | 1597 -- `function-min-args' and `function-max-args' allow you to determine |
2482 | 2482 |
2483 | 2483 |
2484 *** Keymaps | 2484 *** Keymaps |
2485 ----------- | 2485 ----------- |
2486 | 2486 |
2487 The FSF GNU Emacs concept of `function-key-map' is now partially | 2487 The GNU Emacs concept of `function-key-map' is now partially |
2488 implemented. This allows conversion of function-key escape sequences | 2488 implemented. This allows conversion of function-key escape sequences |
2489 such as `ESC [ 1 1 ~' into an equivalent human-readable keysym such as | 2489 such as `ESC [ 1 1 ~' into an equivalent human-readable keysym such as |
2490 `F1'. This work will be completed in 19.14. The function-key map is | 2490 `F1'. This work will be completed in 19.14. The function-key map is |
2491 device-local and controllable through the functions | 2491 device-local and controllable through the functions |
2492 `device-function-key-map' and `set-device-function-key-map'. | 2492 `device-function-key-map' and `set-device-function-key-map'. |
2511 The mouse internals in mouse.el have been rewritten. Hooks have been | 2511 The mouse internals in mouse.el have been rewritten. Hooks have been |
2512 provided for easier customization of mouse behavior. For example, you | 2512 provided for easier customization of mouse behavior. For example, you |
2513 can now easily specify an action to be invoked on single-click | 2513 can now easily specify an action to be invoked on single-click |
2514 (i.e. down-up without appreciable motion), double-click, drag-up, etc. | 2514 (i.e. down-up without appreciable motion), double-click, drag-up, etc. |
2515 | 2515 |
2516 Some code from FSF GNU Emacs has been ported over, generalizing some of | 2516 Some code from GNU Emacs has been ported over, generalizing some of |
2517 the X-specific mouse stuff. | 2517 the X-specific mouse stuff. |
2518 | 2518 |
2519 ** INCOMPATIBLE CHANGE **: The function `set-mouse-position' accepts | 2519 ** INCOMPATIBLE CHANGE **: The function `set-mouse-position' accepts |
2520 a window instead of a frame. | 2520 a window instead of a frame. |
2521 | 2521 |