view BUGS @ 28479:5e8fd5aab7a7

(lispy_mouse_names): Variable removed. (Vlispy_mouse_stem): New variable. (syms_of_keyboard): Initialize Vlispy_mouse_stem. (make_lispy_event) <mouse_click, scroll_bar_click>: Don't abort for any mouse button number. Increase size of mouse_syms and button_down_location as needed. Call modify_event_symbol with different arguments. (make_lispy_event) <scroll_bar_click> [USE_TOOLKIT_SCROLL_BARS]: Call modify_event_symbol with different arguments. (make_lispy_event) <w32_scroll_bar_click> [WINDOWSNT]: Don't abort for any button number. Call modify_event_symbol with different arguments. (modify_event_symbol): Rename NAME_ALIST to NAME_ALIST_OR_STEM. Accept a string for NAME_ALIST_OR_STEM.
author Gerd Moellmann <gerd@gnu.org>
date Mon, 03 Apr 2000 12:11:39 +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,"