Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!lsuc!jimomura From: jimomura@lsuc.UUCP Newsgroups: comp.sys.m68k Subject: Re: M. GNU EMACS OSK Message-ID: <1769@lsuc.UUCP> Date: Mon, 4-May-87 21:14:43 EDT Article-I.D.: lsuc.1769 Posted: Mon May 4 21:14:43 1987 Date-Received: Tue, 5-May-87 01:08:14 EDT References: <1764@lsuc.UUCP> <1925@castor.usc.edu> Reply-To: jimomura@lsuc.UUCP (Jim Omura) Distribution: na Organization: Consultant, Toronto Lines: 55 Summary: Varargs.h Hi Bob, it's good to find you online! In article <1925@castor.usc.edu> blarson@castor.usc.edu (Bob Larson) writes: >In article <1764@lsuc.UUCP> jimomura@lsuc.UUCP (Jim Omura) writes: >> I've been trying to get MicroGNU EMACS up on my FHL QT-20X >>(OS-9 68K version 2.0 on 68020 system). The original posting needed ... >>to compile. 'c68' panics and tells me that there is a line that's >>too long (not surprising since he has used a "line" which runs, I think, >>8 or more lines using backslashes). >Strange. I didn't have any problem with my varargs. Did someone >convert the tabs in varargs.h to spaces? (That would probably put it Somewhere along the line, yes, the tabs got converted to spaces. I tried killing off a bunch of spaces early on in the section that got the error, but I got the same error at the same point so I didn't think that it was helping. I'll go back and try killing all the spaces and see if it makes any difference. >Hmmm.... If someone is converting tabs to spaces, better look at the >lines in mg calling varargs... it might be that converting the leading >indention there could even cause problems. That's definitely a posibility in this circumstance. I'll check that out too. >Did I realy forget to include my varargs.h in with the mg1a posting? Yup. It shouldn't affect many people though. I think we were the only ones missing a 'varargs.h'. >If you need to convert spaces to tabs, you might want to try the tabs >program I posted on mod.sources and the compuserve os9 utilities >section. Huh? What tabs converter? I think I missed it. By the way. I have found that your 'unshar' and Wecker's 'shar' overlap but are not mutually redundant for unsharing files. Wecker's 'shar -u' failed to unshar one of the Micro GNU EMACS postings (with subdirectories), while it was able to unshar Oz's 'proff.c' distribution which your 'unshar' failed. So it seems that although there is some overlap, they are both useful to keep for the time being. Cheers! -- Jim O. -- Jim Omura, 2A King George's Drive, Toronto, (416) 652-3880 ihnp4!utzoo!lsuc!jimomura Byte Information eXchange: jimomura