(Message inbox:224) Return-Path: leafusa!groton.HQ.Ileaf.COM!juliem@ileaf.com Return-Path: Received: from ileaf.com by mail.netcom.com (8.6.4/SMI-4.1/Netcom) id GAA16412; Thu, 9 Dec 1993 06:05:57 -0800 Received: from leafusa.UUCP by ileaf.com (4.1/SMI-4.1) id AA03942; Thu, 9 Dec 93 09:05:21 EST Received: from groton.HQ.Ileaf.COM by HQ.Ileaf.COM (4.1/SMI-4.0-leafusa) for tor@netcom.com id AA18217; Thu, 9 Dec 93 08:59:54 EST Received: by groton.HQ.Ileaf.COM (4.1/SMI-4.0-hq) for tor@netcom.com id AA13885; Thu, 9 Dec 93 08:56:25 EST Date: Thu, 9 Dec 93 08:56:25 EST From: juliem@groton.HQ.ileaf.com (Julie Melbin) Message-Id: <9312091356.AA13885@groton.HQ.Ileaf.COM> To: tor@netcom.com Subject: Release notes Ta da - it's notGNU 1.5! The compiled in date for the released version is Dec 8 1993. Any other older versions are Beta and won't be as good. :) You're strongly encouraged to read the included documentation as Tor and Bernie did an awsum job! I can't thank them enough! The documentation goes into more detail, but here are some basics you really should consider. Please excuse the Windows/DOS/NT bias. 1) For new installations, create a directory for all the distributed files - say c:\notgnu. (For Un*x folks, you could choose ~/bin as I did. Or, some global system location as fits your needs.) Install everything is this location; the exe files, the notgnu.fun file, notboot.exe (Windows folks) etc. For existing installations, you need to put the file notgnu.fun in the SAME place as the notgnu (dnot/wnot/ntnot) exe file else the new command "describe-function" will not work. If you formerly put notgnu and other exes in a directory you don't want to put documentation in, now might be a good time to move things about. 2) Make sure the enviroment variable HOME is set. This is the location that notboot and notgnu for Windows/NT want to use to communicate with each other. If you don't know what notboot is, read the documentation. :) For 1.5, notboot and notgnu will also work w/o HOME if the exe files are in the same directory. But HOME is also useful because subtasks from notgnu generate a log file which is placed in the directory defined by HOME. Keeps thing neater. So, define HOME to be the place you put notgnu files into IF you don't already have a HOME defined. 3) Make sure the supplied .pif files go to your windows directory if this is a new installation, for folks using Windows 3.1. Not needed for NT. See documentation on what these are and why there were included. 4) Try it out! Misc. ----- A couple of functions with multiple names have been cleaned up . See the documentation for details. The default format for the dired command has changed. You can get the old version via dired-single-column. See doc for details as well. Perhaps the most useful single new function is describe-function. If you've installed everything in the right place, m-x describe-function (or control-h f) can give you a little info on a particular command. If you don't know the complete command name, try typing in some letters and hitting spacebar. The command provides autocompletion for command names. notboot.exe was useful on Windows 3.1 because wnot.exe could not have multiple instances running (a windows limitation). For NT, there is notboot2.exe; the only difference is that it trys to invoke/talk to ntnot.exe. If you have an DEC ALPHA NT machine, notboot2.exe should work IF you rename ntaxp.exe to ntnot.exe. If you want the source for notboot to build your own AXP version, just give a hollar. Why would an NT user want to use notboot? To open a filemanager associate file into an existing notgnu that was already running :) Some interesting things, suggested by Tor and other users, have been added. See the doc! :) Cheers julie BUGS kinda... ---------- A note to SunOS 4.1 users, perhaps others ?; the value of argv[0] passed in does not include the execution path (as it does on Windows, DOS, NT, HP-UX, others, where the value of the first arg should be something like /u/jam/bin/xnot if I installed xnot in my own bin directory). Not so on my Sparc running SunOS, so typing 'xnot' invokes notgnu such that it can't find the function list file and describe-function doesn't work. How to get around it if your un*x does the same thing? The rough workaround is to type: ~/bin/xnot for the case where I installed xnot in my own bin directory. Or, define an alias as in (for c shell) alias xnot /xnot The same would be try for the curses version. Questions/comments/suggestions? As always, mail to julie@world.std.com AND/OR the notgnu mailing list . Good luck.