Mercurial > emacs
view BUGS @ 27634:6c9ee29e8955
* dispextern.h: Change HAVE_X_WINDOWS to HAVE_WINDOW_SYSTEM,
around image definitions and prototypes.
(gamma_correct) [WINDOWSNT]: New prototype.
* w32term.c (x_make_frame_visible): Replace call to
input_poll_signal with poll_for_input.
* window.c [WINDOWSNT]: Include w32term.h.
* xdisp.c [WINDOWSNT]: Include w32term.h.
* makefile.nt: Add dependencies on w32gui.h.
(OBJ1): Include atimer.obj.
($(BLD)\atimer.obj): New dependency rule.
* w32.c (sigmask): New function (does nothing).
(sigunblock): Ditto.
* frame.c [WINDOWSNT]: Include w32term.h.
* w32gui.h (struct W32FontStruct): Add ascent and descent slots.
* lread.c (syms_of_lread): Fix literal newlines.
* emacs.c (USAGE): Split into USAGE1 and USAGE2, to work-around
the string constant limit (2048 bytes) in MSVC.
(main): Ditto.
author | Andrew Innes <andrewi@gnu.org> |
---|---|
date | Sun, 06 Feb 2000 23:37:51 +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,"