kolling@decwrl.UUCP (Karen Kolling) (06/04/85)
>To clarify and expand on mirror!rs's comment, the .mo situation is >this: Gosling's v264 will look at .mo files produced by Unipress >2.01, realize they are out of date, and (silently) recompile the >mlisp sources to produce old format .mo files. When Unipress 2.01 >tries to read the old format files, it does dump core. > >This is actually a more subtle problem than it seems, if you have >users trying to use different versions of Emacs with overlapping >EPATHs. Periodically, someone here will try to invoke the old (264) >Emacs for some reason, trashing many of the .mo files in the maclib >directory. Then everyone else's new Emacs (Unipress) suddenly core >dumps the first time it tries to read a .mo that's been ambushed. This is the pits. Thank goodness I'd already decided that the bug level in v2 was so high that I'm not going to release it to our users. We have to have two versions of emacs coexisting, Unipress emacs because it (up to v2, anyway) is "better", and an old emacs (84? 85?) because Unipress emacs wedges when our Modula2 users run multi-threaded programs under emacs shells. And, natch, both versions share our local hacked ml files. Just what I wanted, two copies of all the subsidiary libraries and half the users having to edit their EPaths. Why has the format of the mo files changed, I'd like to know? Karen
chris@umcp-cs.UUCP (Chris Torek) (06/05/85)
> Thank goodness I'd already decided that the bug level in v2 was so > high that I'm not going to release it to our users. That's why I'm still running the local edition of #264... (not that it looks all that much like the original #264 inside anymore.) Even some of the new features are (I think) more bugs than anything else. Consider the key-binding feature of autoload: is it global or is it local? (I think it's global, but someone took my copy of the manual.) And why oh why did they have to use *that* formatting? (*shudder*) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland