I managed to get NEdit compile and run under Apollo Domain/OS 10.4, and figured you'd perhaps want the changes necessary to incorporate them in the next release? The biggest problem here is that the cc is limited to 4K of literal strings, so I had to truncate some of the help pages -- it would be nice if you could think of some work-around? Anyways, here is our changes file... Enjoy, mjl -------------------------------------------------------------------------- # # Changes for Apollo Domain/OS 10.4 with UEDK 2.0 installed # # # If I remember right, this is because otherwise the compiler # complains about "cannot overwrite help.c" or something to that # effect # diff -r no/source/Makefile.common ne/source/Makefile.common 16c16 < $(CC) $(CFLAGS) $(BIGGER_STRINGS) -c help.c -o $@ --- > $(CC) $(CFLAGS) $(BIGGER_STRINGS) -c help.c # # The Apollo cc is limited to static strings with a maximum # length of 4096 bytes. I tried to segment the strings first, # to see whether it's actually a per-segment or per-string # limitation. It's per-string, so I had to cut some of the # help text. Thus help is incomplete on Apollos. This is # life... diff -r no/source/help.c ne/source/help.c 269,270c269,270 < "Indentation\n\ < \n\ --- > "Indentation\n" > "\n\ 276,277c276,277 < \n\ < The Shift Left and Shift Right commands adjust the \ --- > \n" > "The Shift Left and Shift Right commands adjust the \ 284a285,286 > \n" > "Line Numbers\n\ 286,287d287 < Line Numbers\n\ < \n\ 336,337c336,338 < \n\ < NEdit can also be set to load a tags file automatically when it starts up. \ --- > \n" > #ifndef apollo > "NEdit can also be set to load a tags file automatically when it starts up. \ 341,342c342,343 < the same tags file, or a file name without a path or with a relative path, \ < in which case NEdit will load it starting from the current directory. The \ --- > the same tags file, or a file name without a path or with a relative path, " > "in which case NEdit will load it starting from the current directory. The \ 346,348c347,350 < since this is the name that ctags uses.\n\ < \n\ < To find the definition of a function or data structure once a tags file is \ --- > since this is the name that ctags uses.\n" > "\n\" > #endif > "To find the definition of a function or data structure once a tags file is \ 357a360,361 > \n" > "Menu Accelerators\n\ 359,360d362 < Menu Accelerators\n\ < \n\ 367a370,371 > \n" > "Menu Mnemonics\n\ 369,370d372 < Menu Mnemonics\n\ < \n\ 375a378,379 > \n" > "Labeled Function Keys\n\ 377,378d380 < Labeled Function Keys\n\ < \n\ 387,388c389,390 < \n\ < Holding down the shift key while pressing a named key begins or extends a \ --- > \n" > "Holding down the shift key while pressing a named key begins or extends a \ 401a404,405 > \n" > "Keyboard Shortcuts within Dialogs\n\ 403,404d406 < Keyboard Shortcuts within Dialogs\n\ < \n\ 586a589,591 > \n" > #ifndef apollo > "Substitution\n\ 588,589d592 < Substitution\n\ < \n\ 610,611c613,614 < \n\ < In general, the possibilities in a list of branches are considered in \ --- > \n" > "In general, the possibilities in a list of branches are considered in \ 625,626c628,630 < \n\ < In the particular case where no `|'s are present and there is only one \ --- > \n" > #endif > "In the particular case where no `|'s are present and there is only one \ 768a773 > #ifndef apollo 903,904c908,909 < \n\ < You will need to refer to a book on the X window system for the exact \ --- > \n" > "You will need to refer to a book on the X window system for the exact \ 1075,1076c1080,1082 < \n\ < Send questions and comments to: nedit_support@fnal.gov.", --- > \n" > #endif > "Send questions and comments to: nedit_support@fnal.gov.", # # Domain/OS does not define O_NONBLOCK. I hope O_NDELAY means the # same. # diff -r no/source/shell.c ne/source/shell.c 1327a1328,1330 > #ifdef apollo > #define O_NONBLOCK O_NDELAY > #endif # # Inserted forgotten #ifdef USE_DIRENT # diff -r no/util/getfiles.c ne/util/getfiles.c 54a55 > #ifdef USE_DIRENT 55a57,60 > #else > #include > #include > #endif