[1629] in testers
7.3C Emacs
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Tue Jul 30 17:33:09 1991
From: ckclark@ATHENA.MIT.EDU
Date: Tue, 30 Jul 91 17:33:14 -0400
To: jtkohl@ATHENA.MIT.EDU
Cc: vanharen@ATHENA.MIT.EDU, testers@ATHENA.MIT.EDU
In-Reply-To: John T Kohl's message of Mon, 29 Jul 91 13:36:34 -0400 <9107291736.AA09197@pit-manager.MIT.EDU>
Reply-To: ckclark@mit.edu
>>>>> On Mon, 29 Jul 91 13:36:34 -0400, John T Kohl <jtkohl@ATHENA.MIT.EDU> said:
John> I suspect the problem with the mouse map is the reordering of elisp
John> loading in more recent emacses (i.e. changed after 18.54).
In the previous Athena version of emacs, (18.54), we had an
Athena-specific hack, namely, a "site-load.el" containing the single
line:
(load "x-mouse")
In other words, since it was already loaded, users were able to ignore
the putting a "require" statement in their .emacs files. This "feature"
was not a stardard part of emacs 18.54 and is not a stardard part of
18.57. Any elisp source posted on newsgroups, etc., which uses
"x-mouse" will contain the appropriate "require" statement in the
source, because it would not work otherwise, so the only users affected
would be those who, like Chris, have either deliberately or unwittingly
taken advantage of the pre-loading of x-mouse in Athena's emacs in the
past.
If the powers that be decide that they want to re-instate the
pre-loading of x-mouse in order to provide backwards compatability with
users' .emacs files, then this is what has to be done:
1. Create the file site-load.el containing the line:
(load "x-mouse")
2. Remove xemacs and dump a new one.
3. Make sure the dump works on *all* the platforms *before* installing
the new version on *any* of the architectures---there's a small chance
that the inclusion of an extra pre-loaded file will exceed the pure lisp
storage. If this happens, PURESIZE would have to be increased in
config.h, and emacs would have to be rebuilt. If this problem occurs,
it would save time to know ahead of time.
Alteratively, you could just leave it as it is and document the
difference in the release notes. This is my suggestion, but I'm not
going to make the decision.
-Calvin
