Mercurial > emacs
view BUGS @ 101639:789d88174e93
* nsterm.h (EmacsPrefsController.cursorBlinkSlider): Only define
under GNUstep.
(ns_query_color): New declaration.
* nsterm.m (ns_confirm_quit): New variable.
(ns_set_default_prefs, syms_of_nsterm, ns_term_init): Initialize it.
(EmacsApp-applicationShouldTerminate:): Use it.
(EmacsPrefsController): Let user set it.
(ns_query_color): New function.
(ns_defined_color): Use it.
(ns_initialize): Drop.
(ns_term_init): Add two lines from ns_initialize(), and set
input_interrupt_mode to nil.
* image.c (svg_load_image): Don't right-shift background RGB when
obtained from FRAME_BACKGROUND_PIXEL. Under HAVE_NS use ns_query_color.
author | Adrian Robert <Adrian.B.Robert@gmail.com> |
---|---|
date | Thu, 29 Jan 2009 10:38:16 +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.