Default is 0.25.
+** Changes to hideshow.el
+
+Hideshow is now at version 5.x. It uses a new algorithms for block
+selection and traversal and includes more isearch support.
+
+*** Generalized block selection and traversal
+
+A block is now recognized by three things: its start and end regexps
+(both strings), and a match-data selector (an integer) specifying
+which sub-expression in the start regexp serves as the place where a
+`forward-sexp'-like function can operate. Hideshow always adjusts
+point to this sub-expression before calling `hs-forward-sexp-func'
+(which for most modes evaluates to `forward-sexp').
+
+If the match-data selector is not specified, it defaults to zero,
+i.e., the entire start regexp is valid, w/ no prefix. This is
+backwards compatible with previous versions of hideshow. Please see
+the docstring for variable `hs-special-modes-alist' for details.
+
+*** Isearch support for updating mode line
+
+During incremental search, if Hideshow minor mode is active, hidden
+blocks are temporarily shown. The variable `hs-headline' records the
+line at the beginning of the opened block (preceding the hidden
+portion of the buffer), and the mode line is refreshed. When a block
+is re-hidden, the variable is set to nil.
+
+To show `hs-headline' in the mode line, you may wish to include
+something like this in your .emacs.
+
+ (add-hook 'hs-minor-mode-hook
+ (lambda ()
+ (add-to-list 'mode-line-format 'hs-headline)))
+
** Changes to Change Log mode
Change Log mode now adds a file's version number to change log entries
** New modes and packages
+*** bs.el is a new package for buffer selection similar to
+list-buffers or electric-buffer-list. Use M-x bs-show to display a
+buffer menu with this package. You can use M-x bs-customize to
+customize the package.
+
*** The minor modes cwarn-mode and global-cwarn-mode highlights
suspicious C and C++ constructions. Currently, assignments inside
expressions, semicolon following `if', `for' and `while' (except, of
When you add a new item, please add it without either +++ or ---
so I will know I still need to look at it -- rms.
+** If an abbrevs has only a hook, and that hooks has a non-nil
+`no-self-insert' property, the return value of the hook specifies
+whether an expansion has been done or not. If it returns nil, no
+expansion has been performed. The character leading to the call of
+the hook will then be self-inserted.
+
** The function `intern-soft' now accepts a symbol as first argument.
In this case, that exact symbol is looked up in the specified obarray,
and the function's value is nil if it is not found.
+++
** Support functions for colors on text-only terminals.
-The function `face-register-tty-color' can be used to define colors
-for use on TTY frames. It maps a color name to a color number on the
-terminal. Emacs defines a couple of default color mappings by
+The function `tty-color-define' can be used to define colors for use
+on TTY and MSDOS frames. It maps a color name to a color number on
+the terminal. Emacs defines a couple of common color mappings by
default. You can get defined colors with a call to
-`tty-defined-colors'. The function `face-clear-tty-colors' can be
+`defined-colors'. The function `tty-color-clear' can be
used to clear the mapping table.
+** Unified support for colors independent of frame type.
+
+The new functions `defined-colors', `color-defined-p', `color-values',
+and `display-color-p' work for any type of frame. On frames whose
+type is neither x nor w32, these functions transparently map X-style
+color specifications to the closest colors supported by the frame
+display. Lisp programs should use these new functions instead of the
+old `x-defined-colors', `x-color-defined-p', `x-color-values', and
+`x-display-color-p'. (The old function names are still available for
+compatibility; they are now aliases of the new names.) Lisp programs
+should no more look at the value of the variable window-system to
+modify their color-related behavior.
+
+The primitives `color-gray-p' and `color-supported-p' also work for
+any frame type.
+
+++
** The minibuffer prompt is now actually inserted in the minibuffer.
building images from data. When this is done, no `:file' property
may be present in the image specification.
+`:data DATA'
+
+Get image data from DATA. (As of this writing, this is not yet
+supported for image type `postscript'). Either :file or :data may be
+present in an image specification, but not both. All image types
+support strings as DATA, some types allow additional types of DATA.
+
*** Supported image types
**** XBM, image type `xbm'.
XPM images can be built from memory instead of files. In that case,
add a `:data' property instead of a `:file' property.
-`:data DATA'
-
-DATA must be a string containing an XPM image. The contents of the
-string are of the same format as that of XPM files.
-
The XPM library uses libz in its implementation so that it is able
to display compressed images.
**** JPEG, image type `jpeg'
Support for JPEG images requires the external library `libjpeg',
-package `jpegsrc.v6a.tar.gz', or later. There are no additional image
-properties defined.
+package `jpegsrc.v6a.tar.gz', or later. Additional image properties
+are:
**** TIFF, image type `tiff'
(defun display-anim (buffer file idx max first-time)
(when (= idx max)
(setq idx 0))
- (let ((img (create-image file nil :index idx)))
+ (let ((img (create-image file nil nil :index idx)))
(save-excursion
(set-buffer buffer)
(goto-char (point-min))