[xemacs-hg @ 2003-03-02 09:38:37 by ben]
To: xemacs-patches@xemacs.org
PROBLEMS: Include nt/PROBLEMS and update. Add note about incremental
linking badness.
cmdloop.el, custom.el, dumped-lisp.el, files.el, keydefs.el, keymap.el, lisp-mode.el, make-docfile.el, replace.el, simple.el, subr.el, view-less.el, wid-edit.el: Lots of syncing with FSF 21.2.
Use if-fboundp in wid-edit.el.
New file newcomment.el from FSF.
internals/internals.texi: Fix typo.
(Build-Time Dependencies): New node.
PROBLEMS: Delete.
config.inc.samp, xemacs.mak: Eliminate HAVE_VC6, use SUPPORT_EDIT_AND_CONTINUE in its place.
No incremental linking unless SUPPORT_EDIT_AND_CONTINUE, since it
can cause nasty crashes in pdump. Put warnings about this in
config.inc.samp. Report the full compile flags used for src
and lib-src in the Installation output.
alloc.c, lisp.h, ralloc.c, regex.c: Use ALLOCA() in regex.c to avoid excessive stack allocation.
Also fix subtle problem with REL_ALLOC() -- any call to malloc()
(direct or indirect) may relocate rel-alloced data, causing
buffer text to shift. After any such call, regex must update
all its pointers to such data. Add a system, when
ERROR_CHECK_MALLOC, whereby regex.c indicates all the places
it is prepared to handle malloc()/realloc()/free(), and any
calls anywhere in XEmacs outside of this will trigger an abort.
alloc.c, dialog-msw.c, eval.c, event-stream.c, general-slots.h, insdel.c, lisp.h, menubar-msw.c, menubar-x.c: Change *run_hook*_trapping_problems to take a warning class, not
a string. Factor out code to issue warnings, add flag to
call_trapping_problems() to postpone warning issue, and make
*run_hook*_trapping_problems issue their own warnings tailored
to the hook, postponed in the case of safe_run_hook_trapping_problems()
so that the appropriate message can be issued about resetting to
nil only when not `quit'. Make record_unwind_protect_restoring_int()
non-static.
dumper.c: Issue notes about incremental linking problems under Windows.
fileio.c: Mule-ize encrypt/decrypt-string code.
text.h: Spacing changes.
| author |
ben |
| date |
Sun, 02 Mar 2003 09:38:54 +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/
|