Mercurial > hg > xemacs-beta

changeset 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 516934095fef
children 4fa987ead654
files etc/BETA etc/ChangeLog
diffstat 2 files changed, 15 insertions(+), 10 deletions(-) [+]
line wrap: on
line diff
--- a/etc/BETA	Mon Feb 03 22:52:49 2003 +0000
+++ b/etc/BETA	Mon Feb 03 23:35:53 2003 +0000
@@ -118,16 +118,16 @@
     problem is actually occurring.
  
 2.  Attempt to recreate the problem starting with an invocation of
-    XEmacs with `xemacs -vanilla -no-autoloads'.  Quite often,
-    problems are due to package interdependencies, and the like.
-    An actual bug in XEmacs should be reproducible in a default
-    configuration without loading any special packages (or the one
-    or two specific packages that cause the bug to appear).  If you
-    have trouble getting anything to work at all with the above
-    invocation, use `xemacs -vanilla' instead.  If you need to load
-    your user init file or the site file to get the problem to
-    occur, then it has something to do with them, and you should
-    try to isolate the issue in those files.
+    XEmacs with `xemacs -no-autoloads'.  Quite often, problems are
+    due to package interdependencies, and the like.  An actual bug
+    in XEmacs should be reproducible in a default configuration
+    without loading any special packages (or the one or two specific
+    packages that cause the bug to appear).  If you have trouble
+    getting anything to work at all with the above invocation, use
+    `xemacs -vanilla' instead.  If you need to load your user init
+    file or the site file to get the problem to occur, then it has
+    something to do with them, and you should try to isolate the
+    issue in those files.
 
 3.  A picture can be worth a thousand words.  When reporting an
     unusual display, it is generally best to capture the problem in a
--- a/etc/ChangeLog	Mon Feb 03 22:52:49 2003 +0000
+++ b/etc/ChangeLog	Mon Feb 03 23:35:53 2003 +0000
@@ -1,3 +1,8 @@
+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.
+
 2003-02-03  Steve Youngs  <youngs@xemacs.org>
 
 	* BETA: Update.  General tidy up and rewrite sections dealing with