Mercurial > emacs
view BUGS @ 32024:a0ba404b97a5
(search_file_line): Fix skipping of whitespace.
(get_quoted_string): Fix limit on memchr search.
(set_bdf_font_info): Use unsigned chars. Negate yoffset.
(w32_init_bdf_font): Initialize codepoint and bitmap heaps.
(w32_free_bdf_font): Free bitmaps and codepoints on heaps.
(get_cached_font_char, cache_char_offset): Use macro
BDF_CODEPOINT_RANGE_COVER_P.
(cache_char_offset): Use HeapAlloc to allocate codepoints on own heap.
(clear_cached_bitmap_slots): New function.
(GET_HEX_VALUE): G-Z, g-z are not hex.
(w32_get_bdf_glyph): Convert to DIB format. Return bytes read.
(get_bitmap_with_cache): Use new cache implementation.
(create_offscreen_bitmap): New function.
(w32_BDF_TextOut): Use it. Draw glyphs as DIBs.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Fri, 29 Sep 2000 21:23:10 +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,"