Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!paperboy!hsdndev!cmcl2!lanl!silbar@mpx2.lampf.lanl.gov From: silbar@mpx2.lampf.lanl.gov (SILBAR, RICHARD R.) Newsgroups: comp.sys.next Subject: funny stuff with Emacs-2.0 Message-ID: <20587@lanl.gov> Date: 8 Apr 91 14:32:57 GMT Sender: news@lanl.gov Reply-To: silbar@mpx2.lampf.lanl.gov Organization: LAMPF Data Analysis Center, Los Alamos, New Mexico Lines: 36 Some oddities in my setting up of the new John Myers (thanks again, John!) front-end to Emacs that works in 2.0. Unfortunately, for me, only sort of. There are the following peculiarities. First, I didn't see, in the Makefile, any reference to the "streams/error.h" include-file that was brought up here a few weeks ago by someone. I made the (soft) link to "objc/error.h" anyway, figuring it couldn't hurt anything. The "make" of the executable seems to have gone without error. However, when I launch Emacs, I get the following error in the "message line window" at the bottom of the screen: "stack overflow in byte code (byte compiler bug), pc = 7" I don't know what that means, but I suspect that something might be wrong in my .emacs file. One reason for the suspicion is that the Emacs I get is not totally dys- functional. After a while a "$" came up in the *scratch* window, and I could proceed to load a file into an edit buffer. I can move around the file with arrows and control keys, the functions as a (as God so intended), but I have no mouse functions at all. I believe I moved all the eterm files into their proper places, but having written that reminds me I should check this point. Earlier, back in 1.0 days but after I took the NeXT off the net, I was getting an error message that emacs couldn't find the host named "whistler", which is what the NeXT used to be called. I haven't seen that message for a while, but in that version ALSO (after the error started to appear) I had no mouse functions. I didn't bother to try to fix that back then because I was "soon" about to upgrade to 2.0. Besides, I may have fixed this hostname error somewhere along the line, following some suggestion made here, but I don't recall the details right now. Anyone know what's going on? Dick Silbar