view BUGS @ 43231:06e0fbd07e17

Various doc and message fixes. (non-iso-charset-alist): Add mac-roman. Don't add entries for codepages already present. (list-block-of-chars): Display space for null entries in translation table. Display tab specially. (list-non-iso-charset-chars): Check for null charsets. Use pop for clarity. Don't break 8-bit sets into sections between ranges. (list-charset-chars): Avoid indent-tabs-mode. (describe-char-after): Maybe use the text property for syntax table information. Maybe report char-code-property-table info. Maybe report character's unicode. Tweak printing of list info. (list-input-methods): Add xref buttons. (dump-charsets, dump-codings): Deleted (obsolete). From Dave Love <[e-mail]>.

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.