Mercurial > emacs
view src/README @ 27406:fb36ccd8457c
(w32_fill_rect): Do not try to deal with NULL hdc
here. Callers changed to always pass real device context.
(w32_draw_bitmap): Likewise.
(w32_get_glyph_overhangs): Likewise.
(w32_draw_box_rect): Make use of s->hdc rather than getting a new one.
(w32_set_vertical_scroll_bar): Pass correct HWND parameters to
pfnSetScrollInfo and SetScrollRange.
(x_get_char_face_and_encoding): Don't turn iso8859-1 characters
back into MULE characters after decoding them.
(x_get_glyph_face_and_encoding): Likewise.
(w32_per_char_metric): Use GetCharExtentPoint32W as fallback when
GetCharABCWidthsW fails, since this is defined on Windows 9x.
(x_produce_glyphs): Calculate per char metrics for a character
that we know exists in default font when font_not_found_p is true.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Sun, 23 Jan 2000 22:15:12 +0000 |
parents | 18e524802887 |
children | 7ca787d18982 |
line wrap: on
line source
This directory contains the source files for the C component of GNU Emacs. Nothing in this directory is needed for using Emacs once it is built and installed, if the dumped Emacs (on Unix systems) or the Emacs executable and map files (on VMS systems) are copied elsewhere. See the files ../README and then ../INSTALL for installation instructions. Under GNU and Unix systems, the file `Makefile.in' is used as a template by the script `../configure' to produce `Makefile.c'. The same script then uses `cpp' to produce the machine-dependent `Makefile' from `Makefile.c'; `Makefile' is the file which actually controls the compilation of Emacs. Most of this should work transparently to the user; you should only need to run `../configure', and then type `make'. See the file VMSBUILD in this directory for instructions on compiling, linking and building Emacs on VMS. The files `*.com' and `temacs.opt' are used on VMS only. The files `vlimit.h', `ioclt.h' and `param.h' are stubs to allow compilation on VMS with the minimum amount of #ifdefs. `uaf.h' contains VMS uaf structure definitions. This is only needed if you define READ_SYSUAF. This should only be done for single-user systems where you are not overly concerned with security, since it either requires that you install Emacs with SYSPRV or make SYSUAF.DAT world readable. Otherwise, Emacs can determine information about the current user, but no one else. `pwd.h' contains definitions for VMS to be able to correctly simulate `getpwdnam' and `getpwduid'.