view BUGS @ 27462:a4cddf1245d7

(IT_clear_end_of_line): Print the extent of the cleared part of the line to the termscript file. (IT_clear_to_end): Clear the entire line, not just its beginning. (menu_help_message, prev_menu_help_message): New variables. (IT_menu_make_room): Make room for the help_text member. (IT_menu_display): New argument disp_help; all callers changed. If disp_help is non-zero, store the help text of the active menu item in menu_help_message. (XMenuAddPane): Initialize the help_text member to NULL. (XMenuAddSelection): New argument help_text. Store it in the XMenu structure. (XMenuActivate): New argument help_callback. If the value of menu_help_message has changed since the last time, display the menu help message text while waiting for the mouse to move. Clear the echo area before exiting. (XMenuDestroy): Free the help_text member.
author Eli Zaretskii <eliz@gnu.org>
date Thu, 27 Jan 2000 17:07:27 +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,"