annotate BUGS @ 32988:c3435dc00ed7

* lisp.h (KEYMAPP): New macro. (get_keymap): Remove. (get_keymap_1): Rename get_keymap. * keyboard.h (get_keymap_1, Fkeymapp): Remove prototype. * xterm.c (note_mode_line_highlight): Use KEYMAPP. * xmenu.c (single_submenu): Use KEYMAPP. (Fx_popup_menu): Fetch keymaps rather than checking Fkeymapp. Use KEYMAPP rather than Fkeymapp. * w32term.c (note_mode_line_highlight): Use KEYMAPP. * w32menu.c (True, False): Remove (use TRUE and FALSE instead). (Fx_popup_menu): Fetch keymaps rather than checking Fkeymapp. Use KEYMAPP rather than Fkeymapp. (single_submenu): Use KEYMAPP. (w32_menu_show, w32_dialog_show): Use TRUE. * minibuf.c (Fread_from_minibuffer): Update call to get_keymap. * keymap.c (KEYMAPP): Remove (moved to lisp.h). (Fkeymapp): Use KEYMAPP. (get_keymap): Rename from get_keymap_1. Remove old def. Return t when autoload=0 and error=0 and the keymap needs autoloading. (Fcopy_keymap): Check (eq (car x) 'keymap) rather than using Fkeymapp. (Fminor_mode_key_binding): Don't raise an error if the binding is not a keymap. (Fuse_global_map, Fuse_local_map): Allow autoloading. (Faccessible_keymaps): Fetch keymaps rather than checking Fkeymapp. * keyboard.c (read_char): get_keymap_1 -> get_keymap. Allow Vspecial_event_map to be autoloaded. (menu_bar_items): Fetch the keymap rather than using keymapp. (menu_bar_one_keymap): No need to follow func-indirect any more. (parse_menu_item): get_keymap_1 -> get_keymap. (tool_bar_items): Fetch the keymap rather than using keymapp. (read_key_sequence): Use KEYMAPP. * intervals.c (get_local_map): Use get_keymap rather than following function-indirections explicitly. * doc.c (Fsubstitute_command_keys): get_keymap_1 -> get_keymap.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Fri, 27 Oct 2000 22:20:19 +0000
parents 354e0c45cedf
children af68d12218d0
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
25856
Dave Love <fx@gnu.org>
parents:
diff changeset
1 If you think you may have found a bug in GNU Emacs, please
Dave Love <fx@gnu.org>
parents:
diff changeset
2 read the Bugs section of the Emacs manual for advice on
Dave Love <fx@gnu.org>
parents:
diff changeset
3 (1) how to tell when to report a bug, and
Dave Love <fx@gnu.org>
parents:
diff changeset
4 (2) how to write a useful bug report and what information
Dave Love <fx@gnu.org>
parents:
diff changeset
5 it needs to have.
Dave Love <fx@gnu.org>
parents:
diff changeset
6
Dave Love <fx@gnu.org>
parents:
diff changeset
7 There are three ways to read the Bugs section.
Dave Love <fx@gnu.org>
parents:
diff changeset
8
Dave Love <fx@gnu.org>
parents:
diff changeset
9 (1) In a printed copy of the Emacs manual.
Dave Love <fx@gnu.org>
parents:
diff changeset
10 You can order one from the Free Software Foundation;
Dave Love <fx@gnu.org>
parents:
diff changeset
11 see the file etc/ORDERS. But if you don't have a copy on
Dave Love <fx@gnu.org>
parents:
diff changeset
12 hand and you think you have found a bug, you shouldn't wait
Dave Love <fx@gnu.org>
parents:
diff changeset
13 to get a printed manual; you should read the section right away
Dave Love <fx@gnu.org>
parents:
diff changeset
14 as described below.
Dave Love <fx@gnu.org>
parents:
diff changeset
15
Dave Love <fx@gnu.org>
parents:
diff changeset
16 (2) With Info. Start Emacs, do C-h i to enter Info,
Dave Love <fx@gnu.org>
parents:
diff changeset
17 then m Emacs RET to get to the Emacs manual, then m Bugs RET
Dave Love <fx@gnu.org>
parents:
diff changeset
18 to get to the section on bugs. Or use standalone Info in
Dave Love <fx@gnu.org>
parents:
diff changeset
19 a like manner. (Standalone Info is part of the Texinfo distribution,
Dave Love <fx@gnu.org>
parents:
diff changeset
20 not part of the Emacs distribution.)
Dave Love <fx@gnu.org>
parents:
diff changeset
21
Dave Love <fx@gnu.org>
parents:
diff changeset
22 (3) By hand. Do
Dave Love <fx@gnu.org>
parents:
diff changeset
23 cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
Dave Love <fx@gnu.org>
parents:
diff changeset
24