[xemacs-hg @ 2003-02-15 10:15:54 by ben]
autoload fixes, make-doc speed improvements
Makefile.in.in: Run update-elc-2 with -no-autoloads
to avoid multiple autoload-loading problem.
configure.usage: Document quick-build better.
make-docfile.el: Use `message' (defined in this file) in place of `princ'/`print',
and put in a terpri, so that we get correct newline behavior.
Rewrite if-progn -> when and a few similar stylistic niceties.
And the big change: Allow MS Windows to specify the object files
directly and frob them into C files here (formerly this was done
in xemacs.mak, and very slooooooooooooooooooowly). Due to
line-length limitations in CMD, we need to use a "response file"
to hold the arguments, so when we see a response file argument
(preceded by an @), read in the args (a bit of trickiness to do
this), and process recursively. Also frob .obj -> .c as mentioned
earlier and handle other junk dependencies that need to be removed
(NEEDTODUMP, make-docfile.exe).
update-elc-2.el: Use :test `equal' in call to set-difference.
update-elc.el: Put back commented out kill-emacs, update header comment.
xemacs.mak: Delete old unused code that checks SATISFIED.
Move update-elc-2 up to be near update-elc.
Run update-elc-2 with -no-autoloads to avoid multiple
autoload-loading problem.
Don't compute make-docfile args ourselves. Pass the raw objects
to make-docfile.el, which does the computation (much faster than
we could). Don't delete the DOC file, split the invocation into
two calls to make-docfile.exe (one direct, one through
make-docfile.el), etc. In general, all we do is call make-docfile.
Add proper dependencies for DOC-file rebuilding so it doesn't get
done when not necessary. Implement quick-building here: not
building the DOC file unless it doesn't exist, as the quick-build
docs say.
Makefile.in.in: Don't delete the DOC file. Implement quick-building here: not
building the DOC file unless it doesn't exist, as the quick-build
docs say.
config.h.in, emacs.c: Nothing but niggly spacing changes -- one space before a paren
starting a function-call arglist, please.
author |
ben |
date |
Sat, 15 Feb 2003 10:16:14 +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/
|