view BUGS @ 46471:028a5b2de9e4

(chars_in_text, multibyte_chars_in_text, copy_text): (count_size_as_multibyte, count_combining_before): (count_combining_after, insert_1, insert_1_both, message_dolog): (insert, insert_and_inherit, insert_before_markers) (insert_before_markers_and_inherit, set_message, message2): (message2_dolog, build_string, make_string, make_unibyte_string): (make_multibyte_string, intern, oblookup, report_file_error): (fast_c_string_match_ignore_case, temp_echo_area_glyphs): (emacs_open, xstrdup): Declarations updated.

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.