Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rpi!rpi.edu!tale From: tale@pawl.rpi.edu (David C Lawrence) Newsgroups: gnu.emacs.bug Subject: Re: Remember that X bug? Message-ID: Date: 11 Apr 89 06:56:11 GMT References: Sender: usenet@rpi.edu Reply-To: tale@pawl.rpi.edu Distribution: gnu Lines: 26 In-reply-to: tale@pawl.rpi.edu's message of 11 Apr 89 02:06:03 GMT In article I said: tale> (Oh, but in the process I managed to get us up to 18.53.4 when tale> I've only applied two patches ... not that it really matters, tale> but how did it get up there? I tried removing any hints if [sic] tale> earlier versions from the directories and grep'ed the tale> {etc,src}/* files for the 18.53 string but couldn't find where tale> Emacs was keeping track of the patch level. How does temacs tale> inc_version (or whatever) know what level it is to?) Please don't flood me with replies (I think I'll never forgot when I got 87 replies about "Emack's and Bolio's" and ITS). I found out my answer a few minutes later when I went into the lisp directory looking for something else. Staring me right in the face were grow-vers.el, inc-vers.el and version.el. I tweaked the level back down to 1 before a rebuild and everything was peachy. Actually, what I was looking for was a clue as to where to put the autoloads and such that I wanted for my site; I had them in site-init.el (where ${EMACS}/INSTALL said to put any code that was to be loaded into the dumped Emacs) and they didn't take. Perusing the code to loadup.el I finally found my answer (that it should have been in site-load). Perhaps the mention of site-init.el in INSTALL should be a little more clear on what should go into site-init? -- tale@rpitsmts.bitnet, tale%mts@itsgw.rpi.edu, tale@pawl.rpi.edu