Mercurial > hg > xemacs-beta

comparison etc/NEWS @ 404:2f8bb876ab1d r21-2-32

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-32
author cvs
date Mon, 13 Aug 2007 11:16:07 +0200
parents 74fd4e045ea6
children b8cc9ab3f761
comparison
equal deleted inserted replaced
403:9f011ab08d48 404:2f8bb876ab1d
45 Unless our implementation has bugs, the only reason why you would want 45 Unless our implementation has bugs, the only reason why you would want
46 to set `delete-key-deletes-forward' to nil is if you want to use the 46 to set `delete-key-deletes-forward' to nil is if you want to use the
47 Delete key to delete backwards, despite the presence (according to 47 Delete key to delete backwards, despite the presence (according to
48 Xlib) of a BackSpace key on the keyboard. 48 Xlib) of a BackSpace key on the keyboard.
49 49
50 ** Shifted motion keys now select text by default. You can turn this
51 off by setting `shifted-motion-keys-select-region' to nil.
52
53 ** You can now set the variable `kill-whole-line' to `always', which
54 makes `kill-line' (C-k) delete the entire line always, not just when
55 the cursor is at the beginning of the line. This behavior, as well as
56 the existing kill-whole-line behavior, now only take effect when
57 kill-line is called interactively, although this is a departure from a
58 previous behavior in the case of setting this variable kill-whole-line
59 to t. It is almost certainly what has always been intended, and most
60 likely the old way of doing things introduced bugs.
61
62 The new function `historical-kill-line' ignores the `kill-whole-line'
63 setting and always gives the historical behavior of only killing to
64 the end of the line. This function is bound to Sh-C-k, so that the
65 kill to end of line behavior is available, even when `kill-whole-line'
66 has been customized.
67
68 ** XEmacs menus now have accelerators by default. If a menu item does
69 not have an accelerator specified, one is created dynamically, using
70 numbers 1-9 and letters.
71
50 ** Interactive searching and matching case improvements. 72 ** Interactive searching and matching case improvements.
51 73
52 Case sensitiveness in searching operations is normally controlled by 74 Case sensitiveness in searching operations is normally controlled by
53 the variable `case-fold-search' (if non-nil, case is ignored while 75 the variable `case-fold-search' (if non-nil, case is ignored while
54 searching). This mechanism has now been slightly improved for 76 searching). This mechanism has now been slightly improved for
66 `isearch-highlight-all-matches' to nil. 88 `isearch-highlight-all-matches' to nil.
67 89
68 ** You can now use the buffer tabs to switch between buffers. The 90 ** You can now use the buffer tabs to switch between buffers. The
69 tabs are located between the toolbar and the uppermost window, in a 91 tabs are located between the toolbar and the uppermost window, in a
70 location called "gutter". If you dislike the buffer tabs, you can 92 location called "gutter". If you dislike the buffer tabs, you can
71 disable them by specifying: 93 disable them by customizing `gutter-buffers-tab-visible-p', or by
72 94 placing this in your .emacs:
73 (set-specifier default-gutter-visible-p nil) 95
74 96 (set-gutter-element-visible-p default-gutter-visible-p 'buffers-tab nil)
75 in your `.emacs'. You can change the location of the gutter with 97
98 You can change the location of the gutter with
76 `set-default-gutter-position', however currently only MS-Windows 99 `set-default-gutter-position', however currently only MS-Windows
77 supports tab widgets with orientations other than vertical.. 100 supports tab widgets with orientations other than vertical.
101
102 ** Kill and yank now interact with the clipboard by default under
103 Windows. This was done by changing the default value of
104 `interprogram-cut-function' and `interprogram-paste-function'. You
105 can get the old behavior by setting these to nil, and there is an
106 option on the options menu to do this.
78 107
79 ** When you press RET at a minibuffer prompt that provides a default 108 ** When you press RET at a minibuffer prompt that provides a default
80 value, the value is stored in history instead of an empty line. Also, 109 value, the value is stored in history instead of an empty line. Also,
81 you can now edit the default value by pressing the down arrow, 110 you can now edit the default value by pressing the down arrow,
82 accessing the logical "future" value. Not all minibuffer prompts have 111 accessing the logical "future" value. Not all minibuffer prompts have
88 `string-rectangle', which filled all lines up to the right side of the 117 `string-rectangle', which filled all lines up to the right side of the
89 rectangle, and `clear-rectangle', which filled even empty lines up to 118 rectangle, and `clear-rectangle', which filled even empty lines up to
90 the left side. All functions have been rewritten to avoid inserting 119 the left side. All functions have been rewritten to avoid inserting
91 unwanted spaces, and an optional prefix now allows them to behave the 120 unwanted spaces, and an optional prefix now allows them to behave the
92 old way. 121 old way.
122
123 Also, the behavior of `string-rectangle' is now compliant with
124 `pending-delete-mode': if this mode is active, then the string
125 replaces the region rectangle. Otherwise, the command does not delete
126 or overwrite any existing text. For those who want that feature but do
127 not use pending-delete-mode, a new function, `replace-rectangle', is
128 available.
93 129
94 As a side effect, the FORCE argument to `move-to-column' now 130 As a side effect, the FORCE argument to `move-to-column' now
95 understands the special value `coerce', which means that the line 131 understands the special value `coerce', which means that the line
96 should not be filled if it is too short to reach the desired column. 132 should not be filled if it is too short to reach the desired column.
97 133
175 211
176 Moreover, -user <user> (which used to only work in unpredictable ways) 212 Moreover, -user <user> (which used to only work in unpredictable ways)
177 is now equivalent to 213 is now equivalent to
178 -user-init-file ~<user>/.emacs -user-init-directory ~<user>/.xemacs. 214 -user-init-file ~<user>/.emacs -user-init-directory ~<user>/.xemacs.
179 215
216 ** Init file may be called .emacs.el.
217
218 Like in GNU Emacs 20.4 and on, you can now name the XEmacs init file
219 `.emacs.el'. Formerly the name had to be `.emacs'. If you use the
220 name `.emacs.el', you can byte-compile the file in the usual way.
221
222 If both `.emacs' and `.emacs.el' exist, the latter file is the one
223 that is used.
224
180 ** New variable `mswindows-meta-activates-menu'. 225 ** New variable `mswindows-meta-activates-menu'.
181 If you set this variable to nil then pressing the Alt key under 226 If you set this variable to nil then pressing and releasing the Alt
182 MS-Windows will no longer activate the menubar. The default is t. 227 key under MS-Windows will no longer activate the menubar. The default
183 228 is t. This is not to be confused with `menu-accelerator-enabled',
184 ** Pixel-based scrolling has been implemented. 229 which enables the use of Alt+<Letter> accelerators to invoke the
230 menus.
231
232 ** Pixel-based scrolling has been implemented.
185 By default this will attempt to scroll in increments equal to the 233 By default this will attempt to scroll in increments equal to the
186 height of the default face. Set `window-pixel-scroll-increment' to 234 height of the default face. Set `window-pixel-scroll-increment' to
187 modify this behaviour. 235 modify this behaviour.
188 236
237 ** Operation progress can be displayed using graphical widgets.
238 See `lprogress-display' for details. This support has been switched
239 on by default for font-lock and some web browsing functions. If you
240 do not like this behaviour set `progress-display-use-echo-area'.
241
189 ** Etags changes. 242 ** Etags changes.
243
244 ** The PostgreSQL Relational Database Management System is now supported.
245 It is now possible to build XEmacs so that the programming interface
246 to the PostgreSQL RDBMS (libpq) is available in XEmacs Lisp.
247 Supported versions of PostgreSQL are 6.5.3 (earlier versions may work,
248 but have not been tested) and 7.0-beta1.
190 249
191 *** In DOS, etags looks for file.cgz if it cannot find file.c. 250 *** In DOS, etags looks for file.cgz if it cannot find file.c.
192 251
193 *** New option --ignore-case-regex is an alternative to --regex. It is now 252 *** New option --ignore-case-regex is an alternative to --regex. It is now
194 possible to bind a regexp to a language, by prepending the regexp with 253 possible to bind a regexp to a language, by prepending the regexp with
239 running XEmacs only needs to mmap() that file and relocate a bit to 298 running XEmacs only needs to mmap() that file and relocate a bit to
240 get to the initialized data. In that scheme, there is no difference 299 get to the initialized data. In that scheme, there is no difference
241 between `temacs' and `xemacs'. 300 between `temacs' and `xemacs'.
242 301
243 This is all very experimental, though. Configure with `--pdump' to 302 This is all very experimental, though. Configure with `--pdump' to
244 try testing it. NOTE: it is expected that `make' will fail after 303 try testing it.
245 dumping `xemacs.dmp'. This is because Makefiles have not yet been
246 modified to not expect `temacs' producing an `xemacs' executable. You
247 can try it out by simply running `src/temacs'. If it starts without
248 failure, the portable dumping worked.
249
250 #### NOTE: the portable dumper is not really usable yet, because the
251 state of built-in variables is not yet saved. Olivier promised to fix
252 it. Nag, nag.
253 304
254 ** Much effort has been invested to make XEmacs Lisp faster: 305 ** Much effort has been invested to make XEmacs Lisp faster:
255 306
256 *** Many basic lisp operations are now faster. 307 *** Many basic lisp operations are now faster.
257 This is especially the case when running a Mule-enabled XEmacs. 308 This is especially the case when running a Mule-enabled XEmacs.
293 are implemented as native window-system widgets. Thus you can embed 344 are implemented as native window-system widgets. Thus you can embed
294 buttons, scrollbars, combo boxes, edit fields and progress gauges in a 345 buttons, scrollbars, combo boxes, edit fields and progress gauges in a
295 buffer. As a side effect subwindow support now works once again. 346 buffer. As a side effect subwindow support now works once again.
296 347
297 All of this is still fairly experimental and there is no 348 All of this is still fairly experimental and there is no
298 documentation. The current APIs might change in a future version of 349 documentation. The current APIs might change in a future version of
299 XEmacs. Some widgets are only available under MS-Windows. See the 350 XEmacs. Some widgets are only available under MS-Windows. See the
300 file glyphs-test.el in the XEmacs src distribution for examples of 351 file glyphs-test.el in the XEmacs src distribution for examples of
301 usage. 352 usage.
302 353
303 The buffers-tab functionality and progress gauge have been implemented 354 The buffers-tab functionality and progress gauge have been implemented
304 using this feature. 355 using this feature.
440 491
441 This behaviour is compatible with other code which treats symbols 492 This behaviour is compatible with other code which treats symbols
442 beginning with colon as keywords only if they are interned in the 493 beginning with colon as keywords only if they are interned in the
443 global obarray. `keywordp' used to wrongly return t in both cases 494 global obarray. `keywordp' used to wrongly return t in both cases
444 above. 495 above.
496
497 ** New variables `this-command-properties' and
498 `last-command-properties' are now available for communication between
499 consecutive commands. Commands should use these to communicate with
500 the pre/post-command hooks, subsequent commands, wrapping commands,
501 etc. in preference to looking at and/or setting `this-command'.
502
503 ** New functions `add-one-shot-hook' and `add-local-one-shot-hook' make
504 it possible to add a "one-shot" hook, which is to say a hook that runs
505 only once, and automatically removes itself after the first time it
506 has run.
507
508 ** The descriptor that specifies the text of a menu item can now be an
509 evaluated expression. This makes this descriptor parallel with
510 others, which can also be expressions.
445 511
446 512
447 * Changes in XEmacs 21.0 513 * Changes in XEmacs 21.0
448 ======================== 514 ========================
449 515