Mercurial > emacs
view BUGS @ 67457:819dc1a5c256
Include keymap.h.
(mac_ready_for_apple_events): New variable.
(Vmac_apple_event_map, Qmac_apple_event_class)
(Qmac_apple_event_id): New variables.
(syms_of_macselect): Initialize them.
(Qundefined, mac_store_apple_event): Add externs.
(struct apple_event_binding): New struct.
(find_event_binding_fun, find_event_binding)
(mac_find_apple_event_spec, defer_apple_events)
(mac_handle_apple_event, init_apple_event_handler)
(copy_scrap_flavor_data): New functions.
(Fmac_process_deferred_apple_events): New defun.
(syms_of_macselect): Defsubr it.
(mac_store_services_event): Fix extern.
(mac_handle_service_event): Don't allocate Lisp objects during
asynchronous input processing. Use mac_store_services_event
instead of mac_store_application_menu_event.
author | YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> |
---|---|
date | Sat, 10 Dec 2005 01:49:44 +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.