view BUGS @ 29317:2d3d5bf49d4e

Format and doc changes to bring closer to xfns.c. (VIETNAMESE_CHARSET): Define if not defined in system headers. (Qline_spacing, Qcenter): New variables. (Qw32_charset_*, w32_codepage_for_font): Moved from w32term.c. (x_set_line_spacing): New function. (x_set_frame_parameters): Use FRAME_NEW_WIDTH, FRAME_NEW_HEIGHT macros. (x_specified_cursor_type): New function. (x_set_cursor_type): Use it. (x_set_name, x_set_title): Use ENCODE_SYSTEM to encode titlebar and icon strings. (validate_x_resource_name, x_get_resource_string): Measure lengths of external strings in bytes. (w32_wnd_proc) [WM_MEASURE_ITEM]: Avoid calling GetTextExtentPoint32 with NULL title. (Fx_create_frame): Initialize Qline_spacing. (w32_load_system_font): Initialize font->double_byte_p. (x_to_w32_charset): Use Vw32_charset_info_alist. (Image, busy cursor, tooltip functions): Merged changes from xfns.c. Not yet functional on Windows.
author Jason Rumney <jasonr@gnu.org>
date Tue, 30 May 2000 21:45:33 +0000
parents 354e0c45cedf
children af68d12218d0
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,"