X-Git-Url: http://git.chise.org/gitweb/?p=chise%2Fxemacs-chise.git.1;a=blobdiff_plain;f=etc%2FNEWS;h=856fc15169e94b51bbb9ecf2b5a974c01b3c58d0;hp=1c58518e2c0631ebfa3d7e67d84f937532b55940;hb=34360e98c9689b0a7eedab93e14df13281141bbd;hpb=b5eeb6918c29470b36f8461c402eb0c65cb19bd2 diff --git a/etc/NEWS b/etc/NEWS index 1c58518..856fc15 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -33,19 +33,42 @@ file. * Changes in XEmacs 21.2 ======================== -** `delete-key-deletes-forward' now defaults to t. +** The delete key now deletes forward by default. -`delete-key-deletes-forward' is the variable that regulates the -behaviour of the delete key on the systems that offer both a backspace -and a delete key. If set to nil, the key labeled "Delete" will delete -backward. If set to non-nil, the "Delete" key will delete forward, -except on keyboards where a "Backspace" key is not provided. +This is regulated by the variable `delete-key-deletes-forward', which +now defaults to t. `delete-key-deletes-forward' takes effect only on +the systems that offer both a backspace and a delete key. If set to +nil, the key labeled "Delete" will always delete backward. If set to +non-nil, the "Delete" key will delete forward, except on keyboards +where a "Backspace" key is not provided (e.g. old DEC keyboards.) 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. +** Shifted motion keys now select text by default. You can turn this +off by setting `shifted-motion-keys-select-region' to nil. + +** You can now set the variable `kill-whole-line' to `always', which +makes `kill-line' (C-k) delete the entire line always, not just when +the cursor is at the beginning of the line. This behavior, as well as +the existing kill-whole-line behavior, now only take effect when +kill-line is called interactively, although this is a departure from a +previous behavior in the case of setting this variable kill-whole-line +to t. It is almost certainly what has always been intended, and most +likely the old way of doing things introduced bugs. + +The new function `historical-kill-line' ignores the `kill-whole-line' +setting and always gives the historical behavior of only killing to +the end of the line. This function is bound to Sh-C-k, so that the +kill to end of line behavior is available, even when `kill-whole-line' +has been customized. + +** XEmacs menus now have accelerators by default. If a menu item does +not have an accelerator specified, one is created dynamically, using +numbers 1-9 and letters. + ** Interactive searching and matching case improvements. Case sensitiveness in searching operations is normally controlled by @@ -59,6 +82,35 @@ The new behavior affects all functions performing interactive searches, like `zap-to-char', `list-matching-lines', `tags-search' etc. The incremental search facility has always behaved that way. +** Incremental search will now highlight all visible matches, making +it easier to anticipate where consecutive C-s or C-r will place the +point. If you want to disable the feature, set +`isearch-highlight-all-matches' to nil. + +** You can now use the buffer tabs to switch between buffers. The +tabs are located between the toolbar and the uppermost window, in a +location called "gutter". If you dislike the buffer tabs, you can +disable them by customizing `gutter-buffers-tab-visible-p', or by +placing this in your .emacs: + + (set-gutter-element-visible-p default-gutter-visible-p 'buffers-tab nil) + +You can change the location of the gutter with +`set-default-gutter-position', however currently only MS-Windows +supports tab widgets with orientations other than vertical. + +** Kill and yank now interact with the clipboard by default under +Windows. This was done by changing the default value of +`interprogram-cut-function' and `interprogram-paste-function'. You +can get the old behavior by setting these to nil, and there is an +option on the options menu to do this. + +** When you press RET at a minibuffer prompt that provides a default +value, the value is stored in history instead of an empty line. Also, +you can now edit the default value by pressing the down arrow, +accessing the logical "future" value. Not all minibuffer prompts have +yet been converted to support this feature. + ** The rectangle functions have been almost completely rewritten in order to avoid inserting undesirable spaces, notably at the end of lines. Two typical examples of the old behavior were @@ -68,19 +120,21 @@ the left side. All functions have been rewritten to avoid inserting unwanted spaces, and an optional prefix now allows them to behave the old way. +Also, the behavior of `string-rectangle' is now compliant with +`pending-delete-mode': if this mode is active, then the string +replaces the region rectangle. Otherwise, the command does not delete +or overwrite any existing text. For those who want that feature but do +not use pending-delete-mode, a new function, `replace-rectangle', is +available. + As a side effect, the FORCE argument to `move-to-column' now understands the special value `coerce', which means that the line should not be filled if it is too short to reach the desired column. -** Incremental search will now highlight all visible matches, making -it easier to anticipate where consecutive C-s or C-r will place the -point. If you want to disable the feature, set -`isearch-highlight-all-matches' to nil. - -** 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. +** Customize now supports adding comments about your face and variable +settings using a new menu entry. Comments for variables can also be +assigned by calling `customize-set-(value|variable)' with a prefix +argument. ** XEmacs now locates the early package hierarchies at ~/.xemacs/mule-packages/ and ~/.xemacs/xemacs-packages/. Previously, @@ -133,8 +187,8 @@ clipboard can be made; the kill-ring and friends will be updated as per X. The only thing selection doesn't do is set the clipboard automatically -as this would break the MS-Windows model. If you want this behaviour -then set `selection-sets-clipboard' to t +as this would break the MS-Windows model. If you want this behavior +then set `selection-sets-clipboard' to t. ** Mail spool locking now works correctly. XEmacs has always come with a little auxiliary program, movemail, @@ -151,17 +205,65 @@ environment's mail spool locking conventions. When you're using a binary kit, set the `mail-lock-method' variable at startup, or the EMACSLOCKMETHOD environment variable. +** Init file will move to ~/.xemacs/init.el. + +If `~/.xemacs/init.el' exists, XEmacs will prefer it over `~/.emacs' +as an init file. The file may be byte-compiled as +`~/.xemacs/init.elc'. + +Future versions of XEmacs will stop supporting `~/.emacs' as an init +file. XEmacs offers automatic migration upon startup. + +** Custom file will move to ~/.xemacs/custom.el. + +Whereas customize settings were formerly stored in the regular init +file, XEmacs now prefers them to be in a separate file +`~/.xemacs/custom.el', completely under automatic control. This +change goes with the migration of the init file, and XEmacs offers +automatic migration upon startup. + +** Init file may be called .emacs.el. + +For the time being, like in GNU Emacs 20.4 and on, you can now name +the XEmacs init file `.emacs.el'. Formerly the name had to be +`.emacs'. If you use the name `.emacs.el', you can byte-compile the +file in the usual way. + +If both `.emacs' and `.emacs.el' exist, the latter file is the one +that is used. + ** New command-line switches -user-init-file and -user-init-directory. These can be used to specify alternate locations for what is normally ~/.emacs and ~/.xemacs. Moreover, -user (which used to only work in unpredictable ways) -is now equivalent to --user-init-file ~/.emacs -user-init-directory ~/.xemacs. +is now equivalent to -user-init-file ~/.xemacs/init.el +-user-init-directory ~/.xemacs. or -user-init-file +~/.emacs -user-init-directory ~/.xemacs, whichever init +file comes first. ** New variable `mswindows-meta-activates-menu'. -If you set this variable to nil then pressing the Alt key under -MS-Windows will no longer activate the menubar. The default is t. +If you set this variable to nil then pressing and releasing the Alt +key under MS-Windows will no longer activate the menubar. The default +is t. This is not to be confused with `menu-accelerator-enabled', +which enables the use of Alt+ accelerators to invoke the +menus. + +** Pixel-based scrolling has been implemented. +By default this will attempt to scroll in increments equal to the +height of the default face. Set `window-pixel-scroll-increment' to +modify this behavior. + +** Operation progress can be displayed using graphical widgets. +See `lprogress-display' for details. This support has been switched +on by default for font-lock and some web browsing functions. If you +do not like this behavior set `progress-feedback-use-echo-area'. + +** The PostgreSQL Relational Database Management System is now supported. +It is now possible to build XEmacs so that the programming interface +to the PostgreSQL RDBMS (libpq) is available in XEmacs Lisp. +Supported versions of PostgreSQL are 6.5.3 (earlier versions may work, +but have not been tested) and 7.0-beta1. ** Etags changes. @@ -169,9 +271,9 @@ MS-Windows will no longer activate the menubar. The default is t. *** New option --ignore-case-regex is an alternative to --regex. It is now possible to bind a regexp to a language, by prepending the regexp with -{lang}, where lang is one of the languages that `etags --help' prints out. -This feature is useful especially for regex files, where each line contains -a regular expression. The manual contains details. +{lang}, where lang is one of the languages that `etags --help' prints +out. This feature is useful especially for regex files, where each +line contains a regular expression. The manual contains details. *** In C and derived languages, etags creates tags for function declarations when given the --declarations option. @@ -201,7 +303,7 @@ for PSWrap. * Lisp and internal changes in XEmacs 21.2 ========================================== -** A new portable dumper is available. +** A new portable dumper is available for beta testing. Olivier Galibert has written a portable dumper for XEmacs, based on initial work by Kyle Jones. Normally, XEmacs C sources link into an @@ -218,11 +320,7 @@ get to the initialized data. In that scheme, there is no difference between `temacs' and `xemacs'. This is all very experimental, though. Configure with `--pdump' to -try testing it. NOTE: it is expected that `make' will fail after -dumping `xemacs.dmp'. This is because Makefiles have not yet been -modified to not expect `temacs' producing an `xemacs' executable. You -can try it out by simply running `src/temacs'. If it starts without -failure, the portable dumping worked. +try testing it. ** Much effort has been invested to make XEmacs Lisp faster: @@ -267,15 +365,22 @@ are implemented as native window-system widgets. Thus you can embed buttons, scrollbars, combo boxes, edit fields and progress gauges in a buffer. As a side effect subwindow support now works once again. -All of this is still very experimental. This feature is currently -more complete under MS-Windows. +All of this is still fairly experimental and there is no +documentation. The current APIs might change in a future version of +XEmacs. Some widgets are only available under MS-Windows. See the +file glyphs-test.el in the XEmacs src distribution for examples of +usage. + +The buffers-tab functionality and progress gauge have been implemented +using this feature. -** user-init-directory is now an absolute, unexpanded path. -Previously, `user-init-directory' used to be relative to -(concat "~" init-file-user). This turned out to be too complicated -for most packages (and some core Lisp files) to use correctly. +** `user-init-file' and `user-init-directory' are now absolute +file/directory names. Previously, both variables used to be relative +to (concat "~" init-file-user). This turned out to be too complicated +for most packages (and some core Lisp files) to use correctly. Also, +the `init-file-user' variable has been obsoleted in the process. -Also, `init-file-user' has been obsoleted in the process. +The user-visible options like `-u' have not changed their behavior. ** XEmacs finally has an automated test suite! Although this is not yet very sophisticated, it is already responsible @@ -312,6 +417,42 @@ friendlier, but actually faster than checking for C-g. `base64-encode-region', `base64-encode-string', `base64-decode-region' and `base64-decode-string'. +** The functions `read-string', `read-expression', `eval-minibuffer', +`read-variable', `read-command', `read-function', `read-number', +`read-shell-command', `read-from-minibuffer', and `completing-read' +now take an additional argument which specifies the default value. If +this argument is non-nil, it should be a string; that string is used +in two ways: + + It is returned if the user enters empty input. + It is available through the history command M-n. + +** LDAP changes. + +*** The LDAP interface now consists of two layers, a low-level layer +that closely matches the LDAP C API, and a more convenient +higher-level set of functions. + +*** The low-level functions that used to be named *-internal are now +named more simply: `ldap-open', `ldap-close', `ldap-search-basic', +`ldap-add', and `ldap-modify'. They should be used directly for very +specific purposes (such as multiple operations on a connection) only. + +*** The higher-level functions provide a more convenient way to access +LDAP directories hiding the subtleties of handling the connection, +translating arguments and ensuring compliance with LDAP +internationalization rules and formats (currently partly implemented +only.) This layer provides atomic operations for searches, +modification, addition and deletion of multiple entries at once: +`ldap-search-entries', `ldap-add-entries', `ldap-delete-entries', and +`ldap-modify-entries'. + +*** To maintain compatibility with previous code, the now obsolete +function `ldap-search' is now merely a wrapper that calls either +`ldap-search-basic' or `ldap-search-entries'. Please don't use the +`ldap-search' function in your new programs -- a direct call to one of +the two replacements is more efficient and unambiguous. + ** The arguments to `locate-file' are now more Lisp-like. As before, the usage is: @@ -368,11 +509,26 @@ interned in the global obarray. For example: (keywordp (intern ":foo")) ; The same as (keywordp :foo) => t -This behaviour is compatible with other code which treats symbols +This behavior is compatible with other code which treats symbols beginning with colon as keywords only if they are interned in the global obarray. `keywordp' used to wrongly return t in both cases above. +** New variables `this-command-properties' and +`last-command-properties' are now available for communication between +consecutive commands. Commands should use these to communicate with +the pre/post-command hooks, subsequent commands, wrapping commands, +etc. in preference to looking at and/or setting `this-command'. + +** New functions `add-one-shot-hook' and `add-local-one-shot-hook' make +it possible to add a "one-shot" hook, which is to say a hook that runs +only once, and automatically removes itself after the first time it +has run. + +** The descriptor that specifies the text of a menu item can now be an +evaluated expression. This makes this descriptor parallel with +others, which can also be expressions. + * Changes in XEmacs 21.0 ========================