[xemacs-hg @ 2002-04-01 03:58:02 by ben]
bug fixes (e.g. ballooning on X windows)
Makefile.in.in: Try to make the Makefile notice if its source Makefile.in.in is
changed, and regenerate and run itself.
Use a bigger default SHEAP_ADJUSTMENT on Cygwin; otherwise you
can't compile under Mule if a Lisp file has changed. (can't run
temacs)
TODO.ben-mule-21-5: update.
mule/mule-cmds.el: Hash the result of mswindows-get-language-environment-from-locale,
since it's very expensive (and causes huge ballooning of memory
under X Windows, since it's called from x-get-resource).
cl-extra.el, code-files.el, files.el, simple.el, subr.el, x-faces.el: Create new string-equal-ignore-case, based on built-in
compare-strings -- compare strings ignoring case without the need
to generate garbage by calling downcase. Use it in equalp and
elsewhere.
alloc.c, bytecode.c, chartab.c, data.c, elhash.c, emacs.c, eval.c, event-Xt.c, event-unixoid.c, extents.c, file-coding.c, fileio.c, fns.c, glyphs.c, gutter.c, lisp-union.h, lisp.h, mule-charset.c, nt.c, process-unix.c, process.c, specifier.c, symbols.c, sysdep.c, sysdep.h, text.c, toolbar.c: Try to implement GC triggering based on percentage of total memory
usage. Not currently activated (percentage set to 0) because not
quite working. Add `memory-usage' primitive to return XEmacs'
idea of its memory usage.
Add primitive compare-strings, compatible with FSF 21.1 -- can
compare any part of two strings, optionally ignoring case.
Improve qxe() functions in text.c for text comparison.
Use RETURN_NOT_REACHED to try to avoid warnings about unreachable
code.
Add volatile_make_int() to fix warning in unix_send_process().
author |
ben |
date |
Mon, 01 Apr 2002 03:59:04 +0000 |
parents |
9f59509498e1 |
children |
|
rev |
line source |
0
|
1 If you think you may have found a bug in XEmacs, please
|
|
2 read the Bugs section of the XEmacs manual for advice on
|
|
3 (1) how to tell when to report a bug, and
|
|
4 (2) how to write a useful bug report and what information
|
|
5 it needs to have.
|
|
6
|
|
7 There are three ways to read the Bugs section.
|
|
8
|
|
9 (1) In a printed copy of the XEmacs manual.
|
|
10
|
|
11 (2) With Info. Start XEmacs, do C-h i to enter Info,
|
|
12 then m XEmacs RET to get to the Emacs manual, then m Bugs RET
|
|
13 to get to the section on bugs. Or use standalone Info in
|
|
14 a like manner. (Standalone Info is part of the Texinfo distribution,
|
|
15 not part of the XEmacs distribution.)
|
|
16
|
|
17 (3) By hand. Do
|
|
18 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs,"
|
|
19
|
116
|
20
|
|
21 Part II of the XEmacs FAQ, available in a manner similar to the above,
|
|
22 or via the world wide web, contains extensive information on how to
|
|
23 track down and report bugs.
|
|
24
|
|
25 http://www.xemacs.org/faq/
|