view BUGS @ 97819:23390849e8b8

Include window.h, frame.h, dispextern.h font.h. (Vcomposition_function_table) (get_composition_id): Don't handle COMPOSITION_WITH_GLYPH_STRING. (gstring_hash_table, gstring_work, gstring_work_headers): New variables. (gstring_lookup_cache, composition_gstring_put_cache) (composition_gstring_from_id, composition_gstring_p) (composition_gstring_width, fill_gstring_header) (fill_gstring_body, autocmp_chars, composition_compute_stop_pos) (composition_reseat_it, composition_update_it) (composition_adjust_point, Fcomposition_get_gstring): New functions. (syms_of_composite): Initialize gstring_hash_table, gstrint_work, and gstring_work_headers. DEFVAR_LISP composition-function-table. Defsubr compostion_get_gstring.
author Kenichi Handa <handa@m17n.org>
date Fri, 29 Aug 2008 07:53:27 +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.