Mercurial > hg > xemacs-beta

comparison etc/BETA @ 1255:11941b052501

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2003-02-03 23:35:53 by youngs] 2003-02-04 Steve Youngs <youngs@xemacs.org> * BETA: '-no-autoloads' implies '-vanilla' so suggest people invoke 'xemacs -no-autoloads' when trying to reproduce a bug.
author youngs
date Mon, 03 Feb 2003 23:35:53 +0000
parents fa27ca2c798c
children 4322bab48cfb
comparison
equal deleted inserted replaced
1254:516934095fef 1255:11941b052501
116 possible to recreate problems which afflict a specific platform. 116 possible to recreate problems which afflict a specific platform.
117 The line numbers in the C stack backtrace help isolate where the 117 The line numbers in the C stack backtrace help isolate where the
118 problem is actually occurring. 118 problem is actually occurring.
119 119
120 2. Attempt to recreate the problem starting with an invocation of 120 2. Attempt to recreate the problem starting with an invocation of
121 XEmacs with `xemacs -vanilla -no-autoloads'. Quite often, 121 XEmacs with `xemacs -no-autoloads'. Quite often, problems are
122 problems are due to package interdependencies, and the like. 122 due to package interdependencies, and the like. An actual bug
123 An actual bug in XEmacs should be reproducible in a default 123 in XEmacs should be reproducible in a default configuration
124 configuration without loading any special packages (or the one 124 without loading any special packages (or the one or two specific
125 or two specific packages that cause the bug to appear). If you 125 packages that cause the bug to appear). If you have trouble
126 have trouble getting anything to work at all with the above 126 getting anything to work at all with the above invocation, use
127 invocation, use `xemacs -vanilla' instead. If you need to load 127 `xemacs -vanilla' instead. If you need to load your user init
128 your user init file or the site file to get the problem to 128 file or the site file to get the problem to occur, then it has
129 occur, then it has something to do with them, and you should 129 something to do with them, and you should try to isolate the
130 try to isolate the issue in those files. 130 issue in those files.
131 131
132 3. A picture can be worth a thousand words. When reporting an 132 3. A picture can be worth a thousand words. When reporting an
133 unusual display, it is generally best to capture the problem in a 133 unusual display, it is generally best to capture the problem in a
134 screen dump and include that with the problem report. The easiest 134 screen dump and include that with the problem report. The easiest
135 way to get a screen dump is to use the xv program and its grab 135 way to get a screen dump is to use the xv program and its grab