view BUGS @ 62467:35f6599373fc

* textmodes/reftex-vars.el (reftex-cite-format-builtin): Support for jurabib. * textmodes/reftex.el (featurep): Define aliases for overlay commands, for XEmacs compatibility, and use these aliases in overlay initializations. (reftex-highlight): Use `reftex-move-overlay'. (reftex-unhighlight): Use `reftex-delete-overlay'. (reftex-uniq): Funktion removed. Use `reftex-uniquify' instead. (reftex-access-search-path): Use `reftex-uniquify' instead of `reftex-uniq' * textmodes/reftex-sel.el (reftex-select-unmark): Overlay `before-string' property modification enables for Emacs as well. (reftex-select-item): Use `reftex-delete-overlay'. (reftex-select-mark): Use `reftex-make-overlay' and `reftex-overlay-put'. (reftex-select-unmark): Use `reftex-delete-overlay' and `reftex-overlay-put'.
author Carsten Dominik <dominik@science.uva.nl>
date Wed, 18 May 2005 11:23:26 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.