(rather than a fixed number of lines) and the scrolling is `progressive'.
---
-*** Unexpected yanking of text due to accidental clicking on the mouse
-wheel button (typically mouse-2) during wheel scrolling is now avoided.
-This behavior can be customized via the mouse-wheel-click-event and
+*** Emacs ignores mouse-2 clicks while the mouse wheel is being moved.
+
+People tend to push the mouse wheel (which counts as a mouse-2 click)
+unintentionally while turning the wheel, so these clicks are now
+ignored. You can customize this with the mouse-wheel-click-event and
mouse-wheel-inhibit-click-time variables.
+++
\f
* New Modes and Packages in Emacs 22.1
-+++
-** New package benchmark.el contains simple support for convenient
-timing measurements of code (including the garbage collection component).
-
+++
** Filesets are collections of files. You can define a fileset in
various ways, such as based on a directory tree or based on
available in `etc/calccard.tex' and `etc/calccard.ps'.
---
-** `cfengine-mode' is a major mode for editing GNU Cfengine
-configuration files.
+** The new package ibuffer provides a powerful, completely
+customizable replacement for buff-menu.el.
+
+---
+** Ido mode is now part of the Emacs distribution.
+
+The ido (interactively do) package is an extension of the iswitchb
+package to do interactive opening of files and directories in addition
+to interactive buffer switching. Ido is a superset of iswitchb (with
+a few exceptions), so don't enable both packages.
+++
-** The new package conf-mode.el handles thousands of configuration files, with
-varying syntaxes for comments (;, #, //, /* */ or !), assignment (var = value,
-var : value, var value or keyword var value) and sections ([section] or
-section { }). Many files under /etc/, or with suffixes like .cf through
-.config, .properties (Java), .desktop (KDE/Gnome), .ini and many others are
-recognized.
+** Image files are normally visited in Image mode, which lets you toggle
+between viewing the image and viewing the text using C-c C-c.
---
** CUA mode is now part of the Emacs distribution.
** The new package flymake.el does on-the-fly syntax checking of program
source files. See the Flymake's Info manual for more details.
----
-** The new Lisp library fringe.el controls the appearance of fringes.
-
----
-** GDB-Script-mode is used for files like .gdbinit.
-
----
-** The new package ibuffer provides a powerful, completely
-customizable replacement for buff-menu.el.
-
----
-** Ido mode is now part of the Emacs distribution.
-
-The ido (interactively do) package is an extension of the iswitchb
-package to do interactive opening of files and directories in addition
-to interactive buffer switching. Ido is a superset of iswitchb (with
-a few exceptions), so don't enable both packages.
-
-+++
-** Image files are normally visited in Image mode, which lets you toggle
-between viewing the image and viewing the text using C-c C-c.
-
+++
** The new keypad setup package provides several common bindings for
the numeric keypad which is available on most keyboards. The numeric
C-x C-k SPC steps through the last keyboard macro one key sequence
at a time, prompting for the actions to take.
+---
+** New minor mode, Visible mode, toggles invisibility in the current buffer.
+When enabled, it makes all invisible text visible. When disabled, it
+restores the previous value of `buffer-invisibility-spec'.
+
++++
+** The wdired.el package allows you to use normal editing commands on Dired
+buffers to change filenames, permissions, etc...
+
+++
** The new package longlines.el provides a minor mode for editing text
files composed of long lines, based on the `use-hard-newlines'
printer) or send directly to printer a PostScript code generated by
`ps-print' package. Use M-x pr-help for more information.
-+++
-** The new python.el package is used to edit Python and Jython programs.
-
---
** The minor mode Reveal mode makes text visible on the fly as you
move your cursor into hidden regions of the buffer.
(setq tramp-default-method "ftp")
----
-** The library tree-widget.el provides a new widget to display a set
-of hierarchical data as an outline. For example, the tree-widget is
-well suited to display a hierarchy of directories and files.
-
---
** The URL package (which had been part of W3) is now part of Emacs.
---
-** New minor mode, Visible mode, toggles invisibility in the current buffer.
-When enabled, it makes all invisible text visible. When disabled, it
-restores the previous value of `buffer-invisibility-spec'.
+** `cfengine-mode' is a major mode for editing GNU Cfengine
+configuration files.
+++
-** The wdired.el package allows you to use normal editing commands on Dired
-buffers to change filenames, permissions, etc...
+** The new package conf-mode.el handles thousands of configuration files, with
+varying syntaxes for comments (;, #, //, /* */ or !), assignment (var = value,
+var : value, var value or keyword var value) and sections ([section] or
+section { }). Many files under /etc/, or with suffixes like .cf through
+.config, .properties (Java), .desktop (KDE/Gnome), .ini and many others are
+recognized.
---
-** The TCL package tcl-mode.el was replaced by tcl.el.
-This was actually done in Emacs-21.1, and was not documented.
-
-** The new package bindat.el provides functions to unpack and pack
-binary data structures, such as network packets, to and from Lisp
-data structures.
+** GDB-Script-mode is used for files like .gdbinit.
+++
-** The new package button.el implements simple and fast `clickable buttons'
-in emacs buffers. `buttons' are much lighter-weight than the `widgets'
-implemented by widget.el, and can be used by lisp code that doesn't
-require the full power of widgets. Emacs uses buttons for such things
-as help and apropos buffers.
+** The new python.el package is used to edit Python and Jython programs.
---
-** master-mode.el implements a minor mode for scrolling a slave
-buffer without leaving your current buffer, the master buffer.
-
-It can be used by sql.el, for example: the SQL buffer is the master
-and its SQLi buffer is the slave. This allows you to scroll the SQLi
-buffer containing the output from the SQL buffer containing the
-commands.
-
-This is how to use sql.el and master.el together: the variable
-sql-buffer contains the slave buffer. It is a local variable in the
-SQL buffer.
-
-(add-hook 'sql-mode-hook
- (function (lambda ()
- (master-mode t)
- (master-set-slave sql-buffer))))
-(add-hook 'sql-set-sqli-hook
- (function (lambda ()
- (master-set-slave sql-buffer))))
-
-+++
-** New Lisp library testcover.el works with edebug to help you determine
-whether you've tested all your Lisp code. Function testcover-start
-instruments all functions in a given file. Then test your code. Function
-testcover-mark-all adds overlay "splotches" to the Lisp file's buffer to
-show where coverage is lacking. Command testcover-next-mark (bind it to
-a key!) will move point forward to the next spot that has a splotch.
-
-Normally, a red splotch indicates the form was never completely
-evaluated; a brown splotch means it always evaluated to the same
-value. The red splotches are skipped for forms that can't possibly
-complete their evaluation, such as `error'. The brown splotches are
-skipped for forms that are expected to always evaluate to the same
-value, such as (setq x 14).
-
-For difficult cases, you can add do-nothing macros to your code to
-help out the test coverage tool. The macro `noreturn' suppresses a
-red splotch. It is an error if the argument to `noreturn' does
-return. The macro 1value suppresses a brown splotch for its argument.
-This macro is a no-op except during test-coverage -- then it signals
-an error if the argument actually returns differing values.
+** The TCL package tcl-mode.el was replaced by tcl.el.
+This was actually done in Emacs-21.1, and was not documented.
\f
* Changes in Specialized Modes and Packages in Emacs 22.1:
*** `makehash' is now obsolete. Use `make-hash-table' instead.
+++
-*** If optional third argument APPEND to `add-to-list' is non-nil, a
-new element gets added at the end of the list instead of at the
-beginning. This change actually occurred in Emacs-21.1, but was not
-documented.
+*** `add-to-list' takes an optional third argument, APPEND.
-+++
-*** New function `copy-tree' makes a copy of a tree, recursively copying
-both cars and cdrs.
+If APPEND is non-nil, the new element gets added at the end of the
+list instead of at the beginning. This change actually occurred in
+Emacs 21.1, but was not documented then.
+++
-*** New function `delete-dups' destructively removes `equal'
-duplicates from a list. Of several `equal' occurrences of an element
-in the list, the first one is kept.
+*** New function `copy-tree' makes a copy of a tree.
+
+It recursively copyies through both CARs and CDRs.
+++
-*** `declare' is now a macro. This change was made mostly for
-documentation purposes and should have no real effect on Lisp code.
+*** New function `delete-dups' deletes `equal' duplicate elements from a list.
+
+It modifies the list destructively, like `delete'. Of several `equal'
+occurrences of an element in the list, the one that's kept is the
+first one.
+++
-*** The new function `rassq-delete-all' deletes all elements from an
-alist whose cdr is `eq' to a specified value.
+*** New function `rassq-delete-all'.
+
+(rassq-delete-all VALUE ALIST) deletes, from ALIST, each element whose
+CDR is `eq' to the specified value.
+++
-*** The function `number-sequence' returns a list of equally-separated
-numbers. For instance, (number-sequence 4 9) returns (4 5 6 7 8 9).
-By default, the separation is 1, but you can specify a different separation
-as the third argument. (number-sequence 1.5 6 2) returns (1.5 3.5 5.5).
+*** The function `number-sequence' makes a list of equally-separated numbers.
+
+For instance, (number-sequence 4 9) returns (4 5 6 7 8 9). By
+default, the separation is 1, but you can specify a different
+separation as the third argument. (number-sequence 1.5 6 2) returns
+(1.5 3.5 5.5).
+++
-*** The variables `most-positive-fixnum' and `most-negative-fixnum'
-hold the largest and smallest possible integer values.
+*** New variables `most-positive-fixnum' and `most-negative-fixnum'.
+
+They hold the largest and smallest possible integer values.
+++
-*** The flags, width, and precision options for %-specifications in function
-`format' are now documented. Some flags that were accepted but not
-implemented (such as "*") are no longer accepted.
+*** Minor change in the function `format'.
+
+Some flags that were accepted but not implemented (such as "*") are no
+longer accepted.
+++
-*** Functions `get' and `plist-get' no longer signals an error for
-a malformed property list. They also detect cyclic lists.
+*** Functions `get' and `plist-get' no longer give errors for bad plists.
+
+They return nil for a malformed property list or if the list is
+cyclic.
+++
-*** The new functions `lax-plist-get' and `lax-plist-put' are like
-`plist-get' and `plist-put', except that they compare the property
-name using `equal' rather than `eq'.
+*** New functions `lax-plist-get' and `lax-plist-put'.
+
+They are like `plist-get' and `plist-put', except that they compare
+the property name using `equal' rather than `eq'.
+++
-*** The new variable `print-continuous-numbering', when non-nil, says
-that successive calls to print functions should use the same
-numberings for circular structure references. This is only relevant
-when `print-circle' is non-nil.
+*** New variable `print-continuous-numbering'.
+
+When this is non-nil, successive calls to print functions use a single
+numbering scheme for circular structure references. This is only
+relevant when `print-circle' is non-nil.
When you bind `print-continuous-numbering' to t, you should
also bind `print-number-table' to nil.
equivalent to the standard C library function `atan2'.)
+++
-*** A function's doc string can now specify the calling pattern.
+*** A function or macro's doc string can now specify the calling pattern.
-You put this in the doc string's last line, which should match the
-regexp "\n\n(fn.*)\\'".
+You put this info in the doc string's last line. It should be
+formatted so as to match the regexp "\n\n(fn .*)\\'". If you don't
+specify this explicitly, Emacs determines it from the actual argument
+names. Usually that default is right, but not always.
+++
-*** New macro `with-local-quit' temporarily sets `inhibit-quit' to nil.
+*** New macro `with-local-quit' temporarily allows quitting.
-This is for use around potentially blocking or long-running code in
-timers and `post-command-hook' functions.
+A quit inside the body of `with-local-quit' is caught by the
+`with-local-quit' form itself, but another quit will happen later once
+the code that has inhibitted quitting exits.
-*** `define-obsolete-function-alias'
-combines `defalias' and `make-obsolete'.
+This is for use around potentially blocking or long-running code
+inside timer functions and `post-command-hook' functions.
+++
-*** New function `unsafep' returns nil if the given Lisp form can't
-possibly do anything dangerous; otherwise it returns a reason why the
-form might be unsafe (calls unknown function, alters global variable,
-etc).
+*** New macro `define-obsolete-function-alias'.
+
+This combines `defalias' and `make-obsolete'.
+
++++
+*** New function `unsafep' determines whether a Lisp form is safe.
+
+It returns nil if the given Lisp form can't possibly do anything
+dangerous; otherwise it returns a reason why the form might be unsafe
+(calls unknown function, alters global variable, etc).
** Lisp code indentation features:
+++
-*** The `defmacro' form can contain declarations specifying how to
-indent the macro in Lisp mode and how to debug it with Edebug. The
-syntax of defmacro has been extended to
+*** The `defmacro' form can contain indentation and edebug declarations.
+
+These declarations specify how to indent the macro calls in Lisp mode
+and how to debug them with Edebug. You write them like this:
(defmacro NAME LAMBDA-LIST [DOC-STRING] [DECLARATION ...] ...)
DECLARATION is a list `(declare DECLARATION-SPECIFIER ...)'. The
-declaration specifiers supported are:
+possible declaration specifiers are:
(indent INDENT)
Set NAME's `lisp-indent-function' property to INDENT.
(edebug DEBUG)
Set NAME's `edebug-form-spec' property to DEBUG. (This is
- equivalent to writing a `def-edebug-spec' for the macro.
+ equivalent to writing a `def-edebug-spec' for the macro,
+ but this is cleaner.)
---
*** cl-indent now allows customization of Indentation of backquoted forms.
+++
** Variable aliases:
-*** defvaralias ALIAS-VAR BASE-VAR [DOCSTRING]
+*** New function: defvaralias ALIAS-VAR BASE-VAR [DOCSTRING]
This function defines the symbol ALIAS-VAR as a variable alias for
symbol BASE-VAR. This means that retrieving the value of ALIAS-VAR
DOCSTRING, if present, is the documentation for ALIAS-VAR; else it has
the same documentation as BASE-VAR.
-*** indirect-variable VARIABLE
+*** New function: indirect-variable VARIABLE
This function returns the variable at the end of the chain of aliases
of VARIABLE. If VARIABLE is not a symbol, or if VARIABLE is not
** defcustom changes:
+++
-*** defcustom and other custom declarations now use a default group
-(the last prior group defined in the same file) when no :group was given.
-
----
-*** The new customization type `float' specifies numbers with floating
-point (no integers are allowed).
+*** The new customization type `float' requires a floating point number.
** String changes:
+++
-*** The escape sequence \s is now interpreted as a SPACE character,
-unless it is followed by a `-' in a character constant (e.g. ?\s-A),
-in which case it is still interpreted as the super modifier.
-In strings, \s is always interpreted as a space.
+*** The escape sequence \s is now interpreted as a SPACE character.
+
+Exception: In a character constant, if it is followed by a `-' in a
+character constant (e.g. ?\s-A), it is still interpreted as the super
+modifier. In strings, \s is always interpreted as a space.
+
++++
+*** A hex escape in a string constant forces the string to be multibyte.
+++
-*** A hex escape in a string forces the string to be multibyte.
-An octal escape makes it unibyte.
+*** An octal escape in a string constant forces the string to be unibyte.
+++
*** `split-string' now includes null substrings in the returned list if
multibyte string with the same individual character codes.
+++
-*** New function `substring-no-properties returns a substring without
+*** New function `substring-no-properties' returns a substring without
text properties.
+++
`assoc-ignore-representation', which are still available, but have
been declared obsolete.
-** Buffer/variable changes:
-
+++
-*** The new function `buffer-local-value' returns the buffer-local
-binding of VARIABLE (a symbol) in buffer BUFFER. If VARIABLE does not
-have a buffer-local binding in buffer BUFFER, it returns the default
-value of VARIABLE instead.
-
-+++
-** There is a new facility for displaying warnings to the user.
+** Displaying warnings to the user.
-See the functions `warn' and `display-warning' .
+See the functions `warn' and `display-warning', or the Lisp Manual.
+If you want to be sure the warning will not be overlooked, this
+facility is much better than using `message', since it displays
+warnings in a separate window.
+++
** Progress reporters.
+++
*** The `line-move', `scroll-up', and `scroll-down' functions will now
modify the window vscroll to scroll through display rows that are
-taller that the height of the window, for example in the presense of
-large images. To disable this feature, Lisp code can bind the new
-variable `auto-window-vscroll' to nil.
+taller that the height of the window, for example in the presence of
+large images. To disable this feature, bind the new variable
+`auto-window-vscroll' to nil.
+++
-*** The argument to `forward-word', `backward-word',
-`forward-to-indentation' and `backward-to-indentation' is now
-optional, and defaults to 1.
+*** The argument to `forward-word', `backward-word' is optional.
+
+It defaults to 1.
+++
-*** Lisp code can now test if a given buffer position is inside a
-clickable link with the new function `mouse-on-link-p'. This is the
-function used by the new `mouse-1-click-follows-link' functionality.
+*** Argument to `forward-to-indentation' and `backward-to-indentation' is optional.
+
+It defaults to 1.
+++
-*** New function `line-number-at-pos' returns the line number of the
-current line in the current buffer, or if optional buffer position is
-given, line number of corresponding line in current buffer.
+*** New function `mouse-on-link-p' test if a position is in a clickable link.
+
+This is the function used by the new `mouse-1-click-follows-link'
+functionality.
+++
-*** `field-beginning' and `field-end' now accept an additional optional
-argument, LIMIT.
+*** New function `line-number-at-pos' returns the line number of a position.
+
+It an optional buffer position argument that defaults to point.
+
++++
+*** `field-beginning' and `field-end' take new optional argument, LIMIT.
+
+This argument tells them not to search beyond LIMIT. Instead they
+give up and return LIMIT.
+++
*** Function `pos-visible-in-window-p' now returns the pixel coordinates
** Text modification:
+++
-*** The new function `insert-buffer-substring-as-yank' works like
-`insert-buffer-substring', but removes the text properties in the
-`yank-excluded-properties' list.
+*** The new function `insert-for-yank' normally works like `insert', but
+removes the text properties in the `yank-excluded-properties' list
+and handles the `yank-handler' text property.
+
++++
+*** The new function `insert-buffer-substring-as-yank' is like
+`insert-for-yank' except that it gets the text from another buffer as
+in `insert-buffer-substring'.
+++
*** The new function `insert-buffer-substring-no-properties' is like
-insert-buffer-substring, but removes all text properties from the
+`insert-buffer-substring', but removes all text properties from the
inserted substring.
+++
*** The new function `filter-buffer-substring' extracts a buffer
substring, passes it through a set of filter functions, and returns
-the filtered substring. It is used instead of `buffer-substring' or
+the filtered substring. Use it instead of `buffer-substring' or
`delete-and-extract-region' when copying text into a user-accessible
-data structure, like the kill-ring, X clipboard, or a register. The
-list of filter function is specified by the new variable
-`buffer-substring-filters'. For example, Longlines mode uses
+data structure, such as the kill-ring, X clipboard, or a register.
+
+The list of filter function is specified by the new variable
+`buffer-substring-filters'. For example, Longlines mode adds to
`buffer-substring-filters' to remove soft newlines from the copied
text.
---
*** The function `insert-string' is now obsolete.
-** Syntax table changes:
-
+++
-*** The macro `with-syntax-table' does not copy the table any more.
+** Atomic change groups.
-+++
-*** The new function `syntax-after' returns the syntax code
-of the character after a specified buffer position, taking account
-of text properties as well as the character code.
+To perform some changes in the current buffer "atomically" so that
+they either all succeed or are all undone, use `atomic-change-group'
+around the code that makes changes. For instance:
-+++
-*** `syntax-class' extracts the class of a syntax code (as returned
-by syntax-after).
+ (atomic-change-group
+ (insert foo)
+ (delete-region x y))
-*** The new package `syntax.el' provides an efficient way to find the
-current syntactic context (as returned by `parse-partial-sexp').
+If an error (or other nonlocal exit) occurs inside the body of
+`atomic-change-group', it unmakes all the changes in that buffer that
+were during the execution of the body. The change group has no effect
+on any other buffers--any such changes remain.
-** GC changes:
+If you need something more sophisticated, you can directly call the
+lower-level functions that `atomic-change-group' uses. Here is how.
-+++
-*** New variables `gc-elapsed' and `gcs-done' provide extra information
-on garbage collection.
+To set up a change group for one buffer, call `prepare-change-group'.
+Specify the buffer as argument; it defaults to the current buffer.
+This function returns a "handle" for the change group. You must save
+the handle to activate the change group and then finish it.
-+++
-*** Functions from `post-gc-hook' are run at the end of garbage
-collection. The hook is run with GC inhibited, so use it with care.
+Before you change the buffer again, you must activate the change
+group. Pass the handle to `activate-change-group' afterward to
+do this.
+
+After you make the changes, you must finish the change group. You can
+either accept the changes or cancel them all. Call
+`accept-change-group' to accept the changes in the group as final;
+call `cancel-change-group' to undo them all.
+
+You should use `unwind-protect' to make sure the group is always
+finished. The call to `activate-change-group' should be inside the
+`unwind-protect', in case the user types C-g just after it runs.
+(This is one reason why `prepare-change-group' and
+`activate-change-group' are separate functions.) Once you finish the
+group, don't use the handle again--don't try to finish the same group
+twice.
+
+To make a multibuffer change group, call `prepare-change-group' once
+for each buffer you want to cover, then use `nconc' to combine the
+returned values, like this:
+
+ (nconc (prepare-change-group buffer-1)
+ (prepare-change-group buffer-2))
+
+You can then activate the multibuffer change group with a single call
+to `activate-change-group', and finish it with a single call to
+`accept-change-group' or `cancel-change-group'.
+
+Nested use of several change groups for the same buffer works as you
+would expect. Non-nested use of change groups for the same buffer
+will lead to undesirable results, so don't let it happen; the first
+change group you start for any given buffer should be the last one
+finished.
** Buffer-related changes:
---
*** `list-buffers-noselect' now takes an additional argument, BUFFER-LIST.
+
If it is non-nil, it specifies which buffers to list.
+++
*** `kill-buffer-hook' is now a permanent local.
++++
+*** The new function `buffer-local-value' returns the buffer-local
+binding of VARIABLE (a symbol) in buffer BUFFER. If VARIABLE does not
+have a buffer-local binding in buffer BUFFER, it returns the default
+value of VARIABLE instead.
+
** Local variables lists:
+++
If the form is not "ok to call", that means Emacs asks for
confirmation as before.
-** Abbrev changes:
+** Searching and matching changes:
+
++++
+*** New function `looking-back' checks whether a regular expression matches
+the text before point. Specifying the LIMIT argument bounds how far
+back the match can start; this is a way to keep it from taking too long.
+
++++
+*** The new variable `search-spaces-regexp' controls how to search
+for spaces in a regular expression. If it is non-nil, it should be a
+regular expression, and any series of spaces stands for that regular
+expression. If it is nil, spaces stand for themselves.
-*** The new function copy-abbrev-table returns a new abbrev table that
-is a copy of a given abbrev table.
+Spaces inside of constructs such as `[..]' and inside loops such as
+`*', `+', and `?' are never replaced with `search-spaces-regexp'.
+++
-*** define-abbrev now accepts an optional argument SYSTEM-FLAG. If
-non-nil, this marks the abbrev as a "system" abbrev, which means that
-it won't be stored in the user's abbrevs file if he saves the abbrevs.
-Major modes that predefine some abbrevs should always specify this
-flag.
+*** New regular expression operators, `\_<' and `\_>'.
+
+These match the beginning and end of a symbol. A symbol is a
+non-empty sequence of either word or symbol constituent characters, as
+specified by the syntax table.
+
+---
+*** rx.el has new corresponding `symbol-end' and `symbol-start' elements.
+
++++
+*** `skip-chars-forward' and `skip-chars-backward' now handle
+character classes such as `[:alpha:]', along with individual
+characters and ranges.
+
+---
+*** In `replace-match', the replacement text no longer inherits
+properties from surrounding text.
+
++++
+*** The list returned by `(match-data t)' now has the buffer as a final
+element, if the last match was on a buffer. `set-match-data'
+accepts such a list for restoring the match state.
+
++++
+*** The default value of `sentence-end' is now defined using the new
+variable `sentence-end-without-space', which contains such characters
+that end a sentence without following spaces.
+
+The function `sentence-end' should be used to obtain the value of the
+variable `sentence-end'. If the variable `sentence-end' is nil, then
+this function returns the regexp constructed from the variables
+`sentence-end-without-period', `sentence-end-double-space' and
+`sentence-end-without-space'.
** Undo changes:
+++
-*** An element of buffer-undo-list can now have the form (apply FUNNAME
-. ARGS), where FUNNAME is a symbol other than t or nil. That stands
-for a high-level change that should be undone by evaluating (apply
-FUNNAME ARGS).
+*** `buffer-undo-list' can allows programmable elements.
+
+These elements have the form (apply FUNNAME . ARGS), where FUNNAME is
+a symbol other than t or nil. That stands for a high-level change
+that should be undone by evaluating (apply FUNNAME ARGS).
These entries can also have the form (apply DELTA BEG END FUNNAME . ARGS)
which indicates that the change which took place was limited to the
+++
*** If the buffer's undo list for the current command gets longer than
-undo-outer-limit, garbage collection empties it. This is to prevent
+`undo-outer-limit', garbage collection empties it. This is to prevent
it from using up the available memory and choking Emacs.
+++
** New `yank-handler' text property can be used to control how
-previously killed text on the kill-ring is reinserted.
+previously killed text on the kill ring is reinserted.
-The value of the yank-handler property must be a list with one to four
+The value of the `yank-handler' property must be a list with one to four
elements with the following format:
(FUNCTION PARAM NOEXCLUDE UNDO).
The `insert-for-yank' function looks for a yank-handler property on
the first character on its string argument (typically the first
-element on the kill-ring). If a yank-handler property is found,
+element on the kill-ring). If a `yank-handler' property is found,
the normal behavior of `insert-for-yank' is modified in various ways:
When FUNCTION is present and non-nil, it is called instead of `insert'
`yank-rectangle', PARAM should be a list of strings to insert as a
rectangle.
If NOEXCLUDE is present and non-nil, the normal removal of the
-yank-excluded-properties is not performed; instead FUNCTION is
+`yank-excluded-properties' is not performed; instead FUNCTION is
responsible for removing those properties. This may be necessary
if FUNCTION adjusts point before or after inserting the object.
If UNDO is present and non-nil, it is a function that will be called
called with two arguments, the start and end of the current region.
FUNCTION can set `yank-undo-function' to override the UNDO value.
-*** The functions kill-new, kill-append, and kill-region now have an
-optional argument to specify the yank-handler text property to put on
+*** The functions `kill-new', `kill-append', and `kill-region' now have an
+optional argument to specify the `yank-handler' text property to put on
the killed text.
-*** The function yank-pop will now use a non-nil value of the variable
-`yank-undo-function' (instead of delete-region) to undo the previous
-yank or yank-pop command (or a call to insert-for-yank). The function
-insert-for-yank automatically sets that variable according to the UNDO
-element of the string argument's yank-handler text property if present.
+*** The function `yank-pop' will now use a non-nil value of the variable
+`yank-undo-function' (instead of `delete-region') to undo the previous
+`yank' or `yank-pop' command (or a call to `insert-for-yank'). The function
+`insert-for-yank' automatically sets that variable according to the UNDO
+element of the string argument's `yank-handler' text property if present.
*** The function `insert-for-yank' now supports strings where the
`yank-handler' property does not span the first character of the
string. The old behavior is available if you call
`insert-for-yank-1' instead.
-*** The new function insert-for-yank normally works like `insert', but
-removes the text properties in the `yank-excluded-properties' list.
-However, the insertion of the text can be modified by a `yank-handler'
-text property.
+** Syntax table changes:
+
++++
+*** The macro `with-syntax-table' no longer copies the syntax table.
+
++++
+*** The new function `syntax-after' returns the syntax code
+of the character after a specified buffer position, taking account
+of text properties as well as the character code.
+
++++
+*** `syntax-class' extracts the class of a syntax code (as returned
+by `syntax-after').
+
+*** The new function `syntax-ppss' rovides an efficient way to find the
+current syntactic context at point.
** File operation changes:
+++
*** New vars `exec-suffixes' and `load-suffixes' used when
-searching for an executable resp. an elisp file.
+searching for an executable or an Emacs Lisp file.
+++
*** The new primitive `set-file-times' sets a file's access and
The value in that case is an identifier for the remote file system.
+++
-*** `auto-save-file-format' has been renamed to
-`buffer-auto-save-file-format' and made into a permanent local.
+*** `buffer-auto-save-file-format' is the new name for what was
+formerly called `auto-save-file-format'. It is now a permanent local.
+++
*** Functions `file-name-sans-extension' and `file-name-extension' now
`.emacs' are treated as extensionless.
+++
-*** copy-file now takes an additional option arg MUSTBENEW.
+*** `copy-file' now takes an additional option arg MUSTBENEW.
This argument works like the MUSTBENEW argument of write-file.
-+++
-*** If the second argument to `copy-file' is the name of a directory,
-the file is copied to that directory instead of signaling an error.
-
+++
*** `visited-file-modtime' and `calendar-time-from-absolute' now return
a list of two integers, instead of a cons.
sure saved files have the current year in any copyright headers.
+++
-*** If a buffer sets buffer-save-without-query to non-nil,
-save-some-buffers will always save that buffer without asking
-(if it's modified).
+*** If `buffer-save-without-query' is non-nil in some buffer,
+`save-some-buffers' will always save that buffer without asking (if
+it's modified).
*** New function `locate-file' searches for a file in a list of directories.
`locate-file' accepts a name of a file to search (a string), and two
executables without polluting Lisp code with OS dependancies.
---
-*** The precedence of file-name-handlers has been changed.
-Instead of blindly choosing the first handler that matches,
-find-file-name-handler now gives precedence to a file-name handler
-that matches near the end of the file name. More specifically, the
-handler whose (match-beginning 0) is the largest is chosen.
-In case of ties, the old "first matched" rule applies.
+*** The precedence of file name handlers has been changed.
+
+Instead of choosing the first handler that matches,
+`find-file-name-handler' now gives precedence to a file name handler
+that matches nearest the end of the file name. More precisely, the
+handler whose (match-beginning 0) is the largest is chosen. In case
+of ties, the old "first matched" rule applies.
+++
*** A file name handler can declare which operations it handles.
+++
*** An interactive specification can now use the code letter 'U' to get
the up-event that was discarded in case the last key sequence read for a
-previous 'k' or 'K' argument was a down-event; otherwise nil is used.
+previous `k' or `K' argument was a down-event; otherwise nil is used.
+++
*** The new interactive-specification `G' reads a file name
it returns just the directory name.
---
-*** Functions y-or-n-p, read-char, read-key-sequence and the like, that
+*** Functions `y-or-n-p', `read-char', `read-key-sequence' and the like, that
display a prompt but don't use the minibuffer, now display the prompt
using the text properties (esp. the face) of the prompt string.
+++
*** (while-no-input BODY...) runs BODY, but only so long as no input
arrives. If the user types or clicks anything, BODY stops as if a
-quit had occurred. while-no-input returns the value of BODY, if BODY
+quit had occurred. `while-no-input' returns the value of BODY, if BODY
finishes. It returns nil if BODY was aborted.
** Minibuffer changes:
++++
*** The new function `minibufferp' returns non-nil if its optional
buffer argument is a minibuffer. If the argument is omitted, it
defaults to the current buffer.
+++
-*** New function minibuffer-selected-window returns the window which
+*** New function `minibuffer-selected-window' returns the window which
was selected when entering the minibuffer.
+++
-*** read-from-minibuffer now accepts an additional argument KEEP-ALL
+*** `read-from-minibuffer' now accepts an additional argument KEEP-ALL
saying to put all inputs in the history list, even empty ones.
+++
variable is used by read-file-name-internal to filter the completion list.
---
-*** The new variable `read-file-name-function' can be used by lisp code
-to override the internal read-file-name function.
+*** The new variable `read-file-name-function' can be used by Lisp code
+to override the built-in `read-file-name' function.
+++
*** The new variable `read-file-name-completion-ignore-case' specifies
`read-file-name' function.
+++
-*** The new function `read-directory-name' can be used instead of
-`read-file-name' to read a directory name; when used, completion
-will only show directories.
+*** The new function `read-directory-name' for reading a directory name.
-** Searching and matching changes:
+It is like `read-file-name' except that the defaulting works better
+for directories, and completion inside it shows only directories.
-+++
-*** New function `looking-back' checks whether a regular expression matches
-the text before point. Specifying the LIMIT argument bounds how far
-back the match can start; this is a way to keep it from taking too long.
+** Completion changes:
+++
-*** The new variable search-spaces-regexp controls how to search
-for spaces in a regular expression. If it is non-nil, it should be a
-regular expression, and any series of spaces stands for that regular
-expression. If it is nil, spaces stand for themselves.
-
-Spaces inside of constructs such as [..] and *, +, ? are never
-replaced with search-spaces-regexp.
+*** The functions `all-completions' and `try-completion' now accept lists
+of strings as well as hash-tables additionally to alists, obarrays
+and functions. Furthermore, the function `test-completion' is now
+exported to Lisp. The keys in alists and hash tables can be either
+strings or symbols, which are automatically converted with to strings.
+++
-*** There are now two new regular expression operators, \_< and \_>,
-for matching the beginning and end of a symbol. A symbol is a
-non-empty sequence of either word or symbol constituent characters, as
-specified by the syntax table.
+*** The new macro `dynamic-completion-table' supports using functions
+as a dynamic completion table.
-+++
-*** skip-chars-forward and skip-chars-backward now handle
-character classes such as [:alpha:], along with individual characters
-and ranges.
+ (dynamic-completion-table FUN)
----
-*** In `replace-match', the replacement text no longer inherits
-properties from surrounding text.
+FUN is called with one argument, the string for which completion is required,
+and it should return an alist containing all the intended possible
+completions. This alist can be a full list of possible completions so that FUN
+can ignore the value of its argument. If completion is performed in the
+minibuffer, FUN will be called in the buffer from which the minibuffer was
+entered. `dynamic-completion-table' then computes the completion.
+++
-*** The list returned by `(match-data t)' now has the buffer as a final
-element, if the last match was on a buffer. `set-match-data'
-accepts such a list for restoring the match state.
-
----
-*** rx.el has new corresponding `symbol-end' and `symbol-start' elements.
+*** The new macro `lazy-completion-table' initializes a variable
+as a lazy completion table.
-+++
-*** The default value of `sentence-end' is now defined using the new
-variable `sentence-end-without-space', which contains such characters
-that end a sentence without following spaces.
+ (lazy-completion-table VAR FUN &rest ARGS)
-The function `sentence-end' should be used to obtain the value of the
-variable `sentence-end'. If the variable `sentence-end' is nil, then
-this function returns the regexp constructed from the variables
-`sentence-end-without-period', `sentence-end-double-space' and
-`sentence-end-without-space'.
+If the completion table VAR is used for the first time (e.g., by passing VAR
+as an argument to `try-completion'), the function FUN is called with arguments
+ARGS. FUN must return the completion table that will be stored in VAR. If
+completion is requested in the minibuffer, FUN will be called in the buffer
+from which the minibuffer was entered. The return value of
+`lazy-completion-table' must be used to initialize the value of VAR.
+++
** Enhancements to keymaps.
*** Interactive commands can be remapped through keymaps.
-This is an alternative to using defadvice or substitute-key-definition
+This is an alternative to using `defadvice' or `substitute-key-definition'
to modify the behavior of a key binding using the normal keymap
binding and lookup functionality.
original command.
Example:
-Suppose that minor mode my-mode has defined the commands
-my-kill-line and my-kill-word, and it wants C-k (and any other key
-bound to kill-line) to run the command my-kill-line instead of
-kill-line, and likewise it wants to run my-kill-word instead of
-kill-word.
+Suppose that minor mode `my-mode' has defined the commands
+`my-kill-line' and `my-kill-word', and it wants C-k (and any other key
+bound to `kill-line') to run the command `my-kill-line' instead of
+`kill-line', and likewise it wants to run `my-kill-word' instead of
+`kill-word'.
Instead of rebinding C-k and the other keys in the minor mode map,
-command remapping allows you to directly map kill-line into
-my-kill-line and kill-word into my-kill-word through the minor mode
-map using define-key:
+command remapping allows you to directly map `kill-line' into
+`my-kill-line' and `kill-word' into `my-kill-word' using `define-key':
(define-key my-mode-map [remap kill-line] 'my-kill-line)
(define-key my-mode-map [remap kill-word] 'my-kill-word)
-Now, when my-mode is enabled, and the user enters C-k or M-d,
-the commands my-kill-line and my-kill-word are run.
+When `my-mode' is enabled, its minor mode keymap is enabled too. So
+when the user types C-k, that runs the command `my-kill-line'.
-Notice that only one level of remapping is supported. In the above
-example, this means that if my-kill-line is remapped to other-kill,
-then C-k still runs my-kill-line.
+Only one level of remapping is supported. In the above example, this
+means that if `my-kill-line' is remapped to `other-kill', then C-k still
+runs `my-kill-line'.
The following changes have been made to provide command remapping:
- The new function `command-remapping' returns the binding for a
remapped command in the current keymaps, or nil if not remapped.
-- key-binding now remaps interactive commands unless the optional
+- `key-binding' now remaps interactive commands unless the optional
third argument NO-REMAP is non-nil.
-- where-is-internal now returns nil for a remapped command (e.g.
- kill-line if my-mode is enabled), and the actual key binding for
+- `where-is-internal' now returns nil for a remapped command (e.g.
+ `kill-line', when `my-mode' is enabled), and the actual key binding for
the command it is remapped to (e.g. C-k for my-kill-line).
It also has a new optional fifth argument, NO-REMAP, which inhibits
- remapping if non-nil (e.g. it returns C-k for kill-line and
- <kill-line> for my-kill-line).
+ remapping if non-nil (e.g. it returns "C-k" for `kill-line', and
+ "<kill-line>" for `my-kill-line').
- The new variable `this-original-command' contains the original
command before remapping. It is equal to `this-command' when the
over minor mode keymaps.
*** The `keymap' property now also works at the ends of overlays and
-text-properties, according to their stickiness. This also means that it
+text properties, according to their stickiness. This also means that it
works with empty overlays. The same hold for the `local-map' property.
*** Dense keymaps now handle inheritance correctly.
+
Previously a dense keymap would hide all of the simple-char key
bindings of the parent keymap.
*** New function `describe-buffer-bindings' inserts the list of all
defined keys and their definitions.
-*** New function `keymap-prompt' returns the prompt-string of a keymap
+*** New function `keymap-prompt' returns the prompt string of a keymap.
*** (map-keymap FUNCTION KEYMAP) applies the function to each binding
in the keymap.
-*** New variable emulation-mode-map-alists.
+*** New variable `emulation-mode-map-alists'.
Lisp packages using many minor mode keymaps can now maintain their own
-keymap alist separate from minor-mode-map-alist by adding their keymap
-alist to this list.
-
-+++
-** Atomic change groups.
-
-To perform some changes in the current buffer "atomically" so that
-they either all succeed or are all undone, use `atomic-change-group'
-around the code that makes changes. For instance:
-
- (atomic-change-group
- (insert foo)
- (delete-region x y))
-
-If an error (or other nonlocal exit) occurs inside the body of
-`atomic-change-group', it unmakes all the changes in that buffer that
-were during the execution of the body. The change group has no effect
-on any other buffers--any such changes remain.
-
-If you need something more sophisticated, you can directly call the
-lower-level functions that `atomic-change-group' uses. Here is how.
-
-To set up a change group for one buffer, call `prepare-change-group'.
-Specify the buffer as argument; it defaults to the current buffer.
-This function returns a "handle" for the change group. You must save
-the handle to activate the change group and then finish it.
-
-Before you change the buffer again, you must activate the change
-group. Pass the handle to `activate-change-group' afterward to
-do this.
-
-After you make the changes, you must finish the change group. You can
-either accept the changes or cancel them all. Call
-`accept-change-group' to accept the changes in the group as final;
-call `cancel-change-group' to undo them all.
+keymap alist separate from `minor-mode-map-alist' by adding their
+keymap alist to this list.
-You should use `unwind-protect' to make sure the group is always
-finished. The call to `activate-change-group' should be inside the
-`unwind-protect', in case the user types C-g just after it runs.
-(This is one reason why `prepare-change-group' and
-`activate-change-group' are separate functions.) Once you finish the
-group, don't use the handle again--don't try to finish the same group
-twice.
+** Abbrev changes:
-To make a multibuffer change group, call `prepare-change-group' once
-for each buffer you want to cover, then use `nconc' to combine the
-returned values, like this:
++++
+*** The new function `copy-abbrev-table' copies an abbrev table.
- (nconc (prepare-change-group buffer-1)
- (prepare-change-group buffer-2))
+It returns a new abbrev table that is a copy of a given abbrev table.
-You can then activate the multibuffer change group with a single call
-to `activate-change-group', and finish it with a single call to
-`accept-change-group' or `cancel-change-group'.
++++
+*** `define-abbrev' now accepts an optional argument SYSTEM-FLAG.
-Nested use of several change groups for the same buffer works as you
-would expect. Non-nested use of change groups for the same buffer
-will lead to undesirable results, so don't let it happen; the first
-change group you start for any given buffer should be the last one
-finished.
+If non-nil, this marks the abbrev as a "system" abbrev, which means
+that it won't be stored in the user's abbrevs file if he saves the
+abbrevs. Major modes that predefine some abbrevs should always
+specify this flag.
+++
** Enhancements to process support
-*** Function list-processes now has an optional argument; if non-nil,
-only the processes whose query-on-exit flag is set are listed.
+*** Function `list-processes' now has an optional argument; if non-nil,
+it lists only the processes whose query-on-exit flag is set.
-*** New set-process-query-on-exit-flag and process-query-on-exit-flag
-functions. The existing process-kill-without-query function is still
-supported, but new code should use the new functions.
+*** New fns `set-process-query-on-exit-flag' and `process-query-on-exit-flag'.
-*** Function signal-process now accepts a process object or process
+These replace the old function `process-kill-without-query'. That
+function is still supported, but new code should use the new
+functions.
+
+*** Function `signal-process' now accepts a process object or process
name in addition to a process id to identify the signalled process.
*** Processes now have an associated property list where programs can
maintain process state and other per-process related information.
-The new functions process-get and process-put are used to access, add,
-and modify elements on this property list.
+Use the new functions `process-get' and `process-put' to access, add,
+and modify elements on this property list. Use the new functions
+`process-plist' and `set-process-plist' to access and replace the
+entire property list of a process.
-The new low-level functions process-plist and set-process-plist are
-used to access and replace the entire property list of a process.
-
-*** Function accept-process-output now has an optional fourth arg
-`just-this-one'. If non-nil, only output from the specified process
+*** Function `accept-process-output' has a new optional fourth arg
+JUST-THIS-ONE. If non-nil, only output from the specified process
is handled, suspending output from other processes. If value is an
integer, also inhibit running timers. This feature is generally not
recommended, but may be necessary for specific applications, such as
On some systems, when emacs reads the output from a subprocess, the
output data is read in very small blocks, potentially resulting in
very poor performance. This behavior can be remedied to some extent
-by setting the new variable process-adaptive-read-buffering to a
+by setting the new variable `process-adaptive-read-buffering' to a
non-nil value (the default), as it will automatically delay reading
from such processes, to allowing them to produce more output before
emacs tries to read it.
obeys file handlers. The file handler is chosen based on
`default-directory'.
-*** A filter function of a process is called with a multibyte string
-if the filter's multibyteness is t. That multibyteness is decided by
-the value of `default-enable-multibyte-characters' when the process is
-created and can be changed later by `set-process-filter-multibyte'.
+*** A process filter function gets the output as multibyte string
+if the process specifies t for its filter's multibyteness.
+
+That multibyteness is decided by the value of
+`default-enable-multibyte-characters' when the process is created, and
+you can change it later with `set-process-filter-multibyte'.
*** The new function `set-process-filter-multibyte' sets the
multibyteness of the strings passed to the process's filter.
+++
** Enhanced networking support.
-*** There is a new `make-network-process' function which supports
-opening of stream and datagram connections to a server, as well as
+*** The new `make-network-process' function makes network connections.
+It allows opening of stream and datagram connections to a server, as well as
create a stream or datagram server inside emacs.
- A server is started using :server t arg.
*** `emacsserver' now runs `pre-command-hook' and `post-command-hook'
when it receives a request from emacsclient.
-** Minibuffer changes:
-
-+++
-*** The functions all-completions and try-completion now accept lists
-of strings as well as hash-tables additionally to alists, obarrays
-and functions. Furthermore, the function `test-completion' is now
-exported to Lisp. The keys in alists and hash tables can be either
-strings or symbols, which are automatically converted with to strings.
-
-+++
-*** The new macro `dynamic-completion-table' supports using functions
-as a dynamic completion table.
-
- (dynamic-completion-table FUN)
-
-FUN is called with one argument, the string for which completion is required,
-and it should return an alist containing all the intended possible
-completions. This alist can be a full list of possible completions so that FUN
-can ignore the value of its argument. If completion is performed in the
-minibuffer, FUN will be called in the buffer from which the minibuffer was
-entered. `dynamic-completion-table' then computes the completion.
-
-+++
-*** The new macro `lazy-completion-table' initializes a variable
-as a lazy completion table.
-
- (lazy-completion-table VAR FUN &rest ARGS)
-
-If the completion table VAR is used for the first time (e.g., by passing VAR
-as an argument to `try-completion'), the function FUN is called with arguments
-ARGS. FUN must return the completion table that will be stored in VAR. If
-completion is requested in the minibuffer, FUN will be called in the buffer
-from which the minibuffer was entered. The return value of
-`lazy-completion-table' must be used to initialize the value of VAR.
-
** Lisp file loading changes:
+++
---
*** New function `x-send-client-message' sends a client message when
running under X.
+
+** GC changes:
+
++++
+*** New variables `gc-elapsed' and `gcs-done' provide extra information
+on garbage collection.
+
++++
+*** The normal hook `post-gc-hook' is run at the end of garbage collection.
+
+The hook is run with GC inhibited, so use it with care.
+\f
+* New Packages for Lisp Programming in Emacs 22.1
+
++++
+** The new library benchmark.el contains simple support for convenient
+timing measurements of code (including the garbage collection component).
+
+---
+** The new library tree-widget.el provides a widget to display a set
+of hierarchical data as an outline. For example, the tree-widget is
+well suited to display a hierarchy of directories and files.
+
+** The new library bindat.el provides functions to unpack and pack
+binary data structures, such as network packets, to and from Lisp
+data structures.
+
++++
+** The new library button.el implements simple and fast `clickable
+buttons' in emacs buffers. Buttons are much lighter-weight than the
+`widgets' implemented by widget.el, and can be used by lisp code that
+doesn't require the full power of widgets. Emacs uses buttons for
+such things as help and apropos buffers.
+
+---
+** master-mode.el implements a minor mode for scrolling a slave
+buffer without leaving your current buffer, the master buffer.
+
+It can be used by sql.el, for example: the SQL buffer is the master
+and its SQLi buffer is the slave. This allows you to scroll the SQLi
+buffer containing the output from the SQL buffer containing the
+commands.
+
+This is how to use sql.el and master.el together: the variable
+sql-buffer contains the slave buffer. It is a local variable in the
+SQL buffer.
+
+(add-hook 'sql-mode-hook
+ (function (lambda ()
+ (master-mode t)
+ (master-set-slave sql-buffer))))
+(add-hook 'sql-set-sqli-hook
+ (function (lambda ()
+ (master-set-slave sql-buffer))))
+
++++
+** The new library testcover.el does test coverage checking.
+
+This is so you can tell whether you've tested all paths in your Lisp
+code. It works with edebug.
+
+The function `testcover-start' instruments all functions in a given
+file. Then test your code. The function `testcover-mark-all' adds
+overlay "splotches" to the Lisp file's buffer to show where coverage
+is lacking. The command `testcover-next-mark' (bind it to a key!)
+will move point forward to the next spot that has a splotch.
+
+Normally, a red splotch indicates the form was never completely
+evaluated; a brown splotch means it always evaluated to the same
+value. The red splotches are skipped for forms that can't possibly
+complete their evaluation, such as `error'. The brown splotches are
+skipped for forms that are expected to always evaluate to the same
+value, such as (setq x 14).
+
+For difficult cases, you can add do-nothing macros to your code to
+help out the test coverage tool. The macro `noreturn' suppresses a
+red splotch. It is an error if the argument to `noreturn' does
+return. The macro `1value' suppresses a brown splotch for its argument.
+This macro is a no-op except during test-coverage -- then it signals
+an error if the argument actually returns differing values.
\f
* Installation changes in Emacs 21.3
projects / emacs.git / commitdiff