view BUGS @ 96857:571d51f3521f

Change NS to Nextstep in docstrings and error messages. (Fns_create_frame, Fns_read_file_name, Fns_get_resource) (Fns_set_resource, Fns_set_alpha, Fns_server_max_request_size) (Fns_server_vendor, Fns_server_version, Fns_display_screens) (Fns_display_mm_height, Fns_display_mm_width) (Fns_display_backing_store, Fns_display_visual_class) (Fns_display_save_under, Fns_open_connection) (Fns_close_connection, Fns_hide_emacs, Fns_font_name) (Fns_list_colors, Fns_perform_service, Fns_color_defined_p) (Fns_color_values, Fxw_display_color_p, Fx_display_grayscale_p) (Fns_display_pixel_width, Fns_display_pixel_height) (Fns_display_usable_bounds, Fx_display_planes) (Fns_display_color_cells, Vns_icon_type_alist): Doc fixes.
author Chong Yidong <cyd@stupidchicken.com>
date Mon, 21 Jul 2008 15:40:18 +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.