view BUGS @ 41887:8c0b69283972

Fix some 8-bit-graphic characters. Use iso2022 encoding. (latin1-char-displayable-p): Doc fix. (latin1-display-ucs-per-lynx): New option. (latin1-display-ucs-per-lynx): New command. (latin1-display-reset): Special-case arabic. (ucs-tables): Require. (latin1-display-sets, latin1-display-setup): Add arabic. (latin1-display) <variable>: Use function latin1-display. (latin1-display) <function>: Add mule-unicode stuff. (latin1-display-check-font): Don't lose if `info' is nil.
author Dave Love <fx@gnu.org>
date Fri, 07 Dec 2001 18:08:15 +0000
parents af68d12218d0
children 8ce686bd7f4f
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 P in Emacs) to
make sure it isn't a known issue.