============== Revision Notes ============== You don't have to worry about this file AT ALL - the docs are up to date as of version 2.10. This is included in the archive so you can see the effort that's gone into the program, and the changes that have been made on the way to the 2.10 release. This file is in reverse chronological order - ie most recent changes to the oldest. So to read it from an historical perspective, start at the bottom and work back up to here! Version 2.09 (07 Jan 95) ------------------------- * Bugfix: Input quotefile for internal editor now doesn't number lines 1,2,2,3,4,5... rather the normal consecutive cardinal numbers 1,2,3,4,5... :-) * Added the EXWRITTEN keyword, extract from the docs: --------- EXWRITTEN --------- This keyword will execute a command (as specified) when a message is written. I use this to set an environment variable when a message is written so that after the user logs off the BBS, a full message scan (rather than just a toss) can be performed resulting in messages users have written being immediately processed for distribution after they log off. Thus my after-BBS mail processing script can go something like: GETENV MsgWritten IF $MsgWritten EQ TRUE TrapToss Toss Scan ELSE TrapToss Toss ENDIF And then if no messages have been written, a lot of time is saved by not getting TrapToss to scan all the message areas. This might be useful for other purposes I can't think of now. Default: None. Nothing is executed when a message is written. Example: EXWRITTEN Setenv MsgWritten TRUE Version 2.08 (28 Dec 94) ------------------------- * There are now completely user-definable Reply, Cross-Reply and Forward headers instead of the hard coded ones. The defaults are EXACTLY the same as what Plutonic uses now, however using three new keywords you can change any or all of these. The keywords are: REPLYHEADER CROSSHEADER FORWARDHEADER Behind these keywords you can specify a wide range of embedded percent commands (and any other characters) which will have the relevant details substituted in when making up a reply, cross-reply or forwarded message. For example, the defaults of these keywords are: REPLYHEADER In a message to %A posted on %d%labout '%s', %W writes: CROSSHEADER Replying to a msg to %A posted on %d in %l'%p' about '%s', where %W writes: (all on one line) FORWARDHEADER Message forwarded from: %p%l Originally written by: %W%l Originally written to: %A%l Originally dated: %d %t (all on one line) Here is a list of the embedded percent commands currently available (applicable for all these keywords). Please note that these are CASE SENSITIVE, and unlike most other keywords, leading and trailing spaces are NOT stripped. %% -> a single % sign %r -> a (hard) carriage return (Ctrl-M) if using your own editor, otherwise a linefeed (Ctrl-J) if using the internal editor. Use of a hard carriage return will ensure that the header is not reflowed. However, it's usually much better to actually re-flow the header anyway, so I don't recommend the use of this one at all! (PS: you can also prevent it being reflowed by indenting the header text at least one space from the left, as exemplified above in the FORWARDHEADER default) %l -> a linefeed character (Ctrl-J). This is the one to use 99% of the time. For these next two commands, bear in mind the two date formats: Fido format: 01 Jan 86 02:34:56 Seadog Format: Mon 1 Jan 86 02:34 Since DLG uses the SeaDog format, we see a lot of it in Amiga message areas. %d -> Date of original message. I even include the year if we get a Seadog format date. So with standard Fido format this will be 9 characters long, if the message has Seadog format it's 13 characters long. If this doesn't work properly, the message you are replying to isn't obeying FTS-1. (IE broken) %t -> Time of original message. This is always 8 characters long, if we have a Seadog date format, then :00 is appended to the end of the time string %S -> Full subject of the original message %s -> (Up to) the leftmost 36 characters of the subject of the original message %p -> Name of the message area as given in plutonic.areas %W -> Full name of the writer of the original message %w -> First name of the writer of the original message %A -> Full name of the receiver (addressee) of the original message %a -> First name of the receiver (addressee) of the original message %M -> if the fromname of the original message is you, yourself (not case-sensitive) this is translated to the word "me". Otherwise equivalent to %W %m -> if the toname of the original message is you, yourself (not case-sensitive) this is translated to the word "me". Otherwise equivalent to %A %I -> if the fromname of the original message is you, yourself (not case-sensitive) this is translated to the word "I". Otherwise equivalent to %W %i -> if the toname of the original message is you, yourself (not case-sensitive) this is translated to the word "I". Otherwise equivalent to %A Unfortunately, since we DON'T KNOW the name of the person you're going to post the message to until AFTER it's been written, I can't figure out how to implement a "you" via these embedded percent commands. And getting the ToName BEFORE the message is written would involve substantial internal re-structuring, and not something I'm too keen on doing anyway - I prefer to be asked who to send the message to AFTER I've written it! Some examples might be: ReplyHeader On %d at %t, %W wrote to %m%labout '%s'%l%l Hello %w,%l CrossHeader In '%p' on %d, %I%lwrote to %m about "%S" ReplyHeader Hi there, %w, you were talking about%l "%s" on %d: (etc, etc, etc) Version 2.07 (28 Dec 94) ------------------------- * Well, 2.06 was a full release but I decided not to put it on to AmiNet until more features were installed. * BugFix: Selecting a file to attach would only work if you clicked on the filename in the FileSelector twice. If you clicked on the filename and then the ATTACH gadget, or typed in the name and hit return, it didn't work. * Loops back to "Attach a File?" question if you make an error in the file attach selector by chosing a non-existant filename, or attaching a directory instead of a file. * Best guess match for netmail origins. This is done using the new FROMADDRESS keyword. The usage of the FROMADDRESS keyword is: FROMADDRESS Where is the destination zone, and is the node number you'd like to use if writing to that zone. A maximum of 100 FROMADDRESS keywords can be used (can be increased, I doubt anyone would be in networks totalling 100 zones, though!) All my FROMADDRESS keywords look like this: ; Matrix addresses FROMADDRESS 1 3:622/401 FROMADDRESS 2 3:622/401 FROMADDRESS 3 3:622/401 FROMADDRESS 4 3:622/401 FROMADDRESS 5 3:622/401 FROMADDRESS 6 3:622/401 FROMADDRESS 7 7:500/401 FROMADDRESS 9 9:200/104 FROMADDRESS 39 41:200/401 FROMADDRESS 40 41:200/401 FROMADDRESS 41 41:200/401 FROMADDRESS 42 42:5800/19 FROMADDRESS 51 54:6101/401 FROMADDRESS 52 54:6101/401 FROMADDRESS 53 54:6101/401 FROMADDRESS 54 54:6101/401 FROMADDRESS 55 54:6101/401 If a match for the destination zone cannot be found from this list, the address specified in Plutonic.areas will be the default address used on the netmail. This only sets the DEFAULT address - anyone with a security level of equal to or greater than the MATRIXADDRESS parameter can actually change the origin address of a netmail, by simply typing another one in when the program asks for the origin address. However, you almost certainly now won't want to give anyone access to this feature (or at least ensure you're giving a pretty high security level for MATRIXADDRESS). Version 2.06 (14 Dec 94) ------------------------- * Breaking the rule of full-tenth numbers, this is a FULL release version destined for upload to the UUCP AmiNet. Thanks to Philip Brown (3:640/213) for getting these on to AmiNet for me. * The docs in the release archive are NOT up to date. These changes apply to Pluto 2.06, and mainly add features. Please check this file carefully for the extra bits and pieces. * When you attach a file, the file size will be reported when you're asked to confirm your desire to actually attach the file selected by the file requester. * Plutonic will now not let you attach a directory instead of a file :-) * Separate keyword implemented for Rescan security. The Delete Whats.here function was previously sysop-only. Now it will be available at the security level you specify via the RESCAN keyword Default: 5 Example: RESCAN 9 * Separate keyword for security of ability to change default origin address of a netmail via the MATRIXADDRESS keyword. Default: 5 Example: MATRIXADDRESS 2 Version 2.05 (10 Dec 94) ------------------------- * Not released, not enough changes. * Fixed print message Cancel function so the "File Channel Exists" requester no longer comes up - it simply quits there and then (S Banham) * No longer reflows forwarded messages. Okay so it seemed like good idea at the time. * Changed text so it says "Reflow your message text?" when you WRITE a message (was printing "Reflow your REPLY text?"). A little too much cut and paste I think. * Default for Forward Message Security is now level 5 (to be consistent with the default for ShowKludge) (P Nicolas - I dunno about 9 though, Pete - you still have the WRITE security working on forwarding, so if someone can't write in an area they can't forward. See changes 2.04) Version 2.04 (08 Dec 94) ------------------------- * Implemented message forwarding function. A message can be forwarded from one mail base into ANY other (including the original base). Forwarding is implemented as per Fido requirements (ie the from name is that of the forwarder, all kludge lines are stripped, and your OWN origin line and address is used for the message). A tagline is NOT added to forwarded messages even if you have taglines turned on (a lot of them already have taglines, so no point adding a second one). Forwarding is similar in function to actually writing a reply - except you don't have to type the message. This will be handy for sending multiple netmails to more than one person, incidentally. Write the original, and forward it to whomsoever you want. * New keyword: FORWARD This controls the security of people allowed to forward messages. Usage is FORWARD . Users have a tendency to forward messages left, right and centre, so consider carefully the security level you wish to make forwarding available to. Users can only forward into areas they have write access to, of course, and it's only available if they have write access IN THE AREA THE (original) MESSAGE IS IN. Default: Level 1 (Everyone can forward) Example: FORWARD 9 * Found an error in a label name in the netmail reply code - it seems nobody has dropped carrier here immediately after a netmail message has been posted - if they had, an invalid label name would have been GOTO'd (and Pluto would have quit, so it wouldn't have been a hassle anyway). * When getting a ToName for a message reply, and NOT using the default, the given ToName is now parsed through the capitaliser routines. * Printed messages now have all kludge lines and header text indented one space, so they can be used as raw message text and not get reflowed unintentionally. * Print Message function now calls up a File Selector, rather than a small window (Steve Banham). This will take a bit of getting used to, I must say. If you select to send the message to the printer, you must click on the PRINT gadget to get out of the file Selector box - it won't let you get out by just pressing return when typing in PRT: If sending to a file, this should make is a lot easier to choose a (unique) filename. * New keyword: PRINTMSGDIR This is the initial default directory to save printed messages to when the print message File Selector is called up. (S Banham/P Nicolas). A trailing slash is optional (one is added if not already specified). A trailing colon for a device name is mandatory if you use that. If you use the printer a lot, I suggest you make this PRT: Default: RAM: Example: PRINTMSGDIR Mail:Saved_Msgs/ * Increased the size of (quite) a few strings taken in from Plutonic.cfg. These are only arbitrary levels and can be longer if need be (P Nicolas). * Went back to the old mouse method in the Headit routine, because what I changed it to in 2.01 just wasn't working (Steve Banham/Me). * TO-DO: embedded percent commands and user-definable message reply, cross-post and forward headers. * TO-DO: best guess match for netmail origin number. Version 2.03 (04 Dec 94) ------------------------- * On re-loading the message areas from an "L" the file Plutonic.areas would be loaded. Now if you've run the program with a command line telling Plutonic the areas file, that filename will be used instead. For this to work properly ensure you have no AREAFILE keyword in your config because the "L"oad config reads your config file and will use the AREAFILE command from there if it finds one. (Thanks Steve Banham) * If aborting or pressing any key after reading an echo rules file the key you used was a valid Menu command, that command would be executed! I ALWAYS press Return when I get an [Any_key] prompt, so I've never noticed this. Fixed by adding one line of code (Steve Banham again). * Fixed problem in unregistered mode I won't go into at all (Steve once more!) * decided to archive this version into the PltNic20.lha file, so if you've frequed that after today, you'll have v2.03 now! Version 2.02 (29 Nov 94) ------------------------- * Hmm, version 2.02, will have to call it Non Commercial :-) * Added a few keyboard and serial purges. * Removed idle timer in local mode entirely! (Still there for remote callers, mind you) * creation of Plutonic.lmr files for new echo areas substantially sped up (probably by a factor of around 15-20 times); now no longer worth printing "Creating User Index" text, so formatting of newly created areas isn't made askew when Pluto creates the Last Message Read file. Version 2.01 (27 Nov 94) ------------------------- * Changed the Headit routine so selection is no longer made when you press the mouse-button, rather when you RELEASE the mousebutton. This should speed things up a little, BTW because there was a pause of 2/5 second after each button press. You can now no longer hold down the mouse button over a gadget and get it to cycle through the options ON, OFF, ON, OFF (etc). It will take a click and release for each change. * Tearline/PID creation changed. Will now add tearlines like: --- Plutonic 2.01 #1 --- Plutonic 2.01 Unregistered Or PID lines like: ^aPID: Plutonic 2.01 1 ^aPID: Plutonic 2.01 (for unregistered) 1.99 Gamma E (21 Nov 1994) -------------------------- o Small display error in the editor now prints blank line between the instructions and the editor lines to the REMOTE as well as locally. o Adds a blank line before "Continue One Line Summary" when using this function. o Big deal, eh? This is the one we're running with - it will be recompiled as V2.0 in about 5 minutes.... 1.99 Gamma D (19 Nov 1994) -------------------------- o Ahhhhh what the hell - 12 message areas isn't enough - give em 20 in unregistered mode. No more! 1.99 Gamma C (19 Nov 1994) -------------------------- o I bit the bullet! I spent about six hours this morning developing a keyfile system for the program, and it's BLODY SECURE. To reverse engineer the thing would be a work of brilliance, almost certainly involving dissasembling the exe. All but 4 bytes of the keyfile are checksummed (the 4 others ARE the checksum!), so don't alter 1 single byte of it, or the progam will run in unregistered mode. (It doesn't do anything nasty if it finds a hacked key, BTW) This will mean the SAME version can go out to all and sundry. The two limitations I imposed on the non-registered version are: * There is a maximum of twelve message areas * If the time remaining figures at greater than 25 minutes, the door will use the time routines to exit after 25 minutes. (This was easily achieved because the door keeps track of the time limit anyway) Pluto won't kick you off in the middle of a message at all - it hangs around until you do post it (or elect not to), even if you've gone over the time limit. o The hidden keyword to change the tearlines is GONE. The program name and registration number from your keyfile is now used instead. Of course you can choose config options to either not add it or use TEARLINE Replace in TrapToss - but in most cases the registration numbers will be visible in messages produced by Pluto. 1.99 Gamma B (19 Nov 1994) -------------------------- o Hardly any point mentioning the changes - so few 1.99 Gamma A (18 Nov 1994) -------------------------- o Well, Gamma mode now, meaning one more step beyond Beta. IE nearly release mode. The public release will be simply restricted to 12 message areas only, BTW. o Very few changes - mainly changed a few keyword defaults after writing the keyword documentation when I realised it might be better to have MAXBAUD defaulting to 19200, for instance rather than 2400 :-) If you're specifying most keywords in the config (like me) you won't be able to pick ANY changes over 198 beta Z. 1.98 Beta Z (17 Nov 1994) ------------------------- o Bugger it - didn't set a flag when using the INTERNAL editor for message WRITES (replies were fine), and program was asking you if you wanted to reflow messages written in the internal editor, and using the wrong input routine to make them into a message. Fixed, of course. 1.98 Beta Y (16 Nov 1994) ------------------------- o Reflow routines added for messages written in your own editor. This completely changes the method external Plutonic.tmp files are read in, so even if you don't use the reflow, you'll be pleased to know the 255 character per line limit has gone (in fact, I tested it on a 32,000 character single line and it worked really well). The Reflow routine is really nifty. To stop Plutonic reflowing some sections you DON'T want reflowed (eg log extracts) you have two options: 1) Indent the line(s) by one or more spaces. 2) Use a Carriage Return (Ascii 13) rather than a LineFeed (Ascii 10) at the End of Line. All carriage returns are entered into the message verbatim. Naturally, for the reflow to be effective you need to separate paragraphs with either two blank lines, or indent the next paragraph by one or more spaces. (You'd be doing this anyway). Plutonic asks you after EVERY message written in the external editor whether you want to reflow the message or not. The Default Yes/No answer for this can be set by use of a new keyword: (NO)DEFREFLOW This is short for Default Reflow Answer. If it's turned on, the default answer is YES (which is the default setting if you don't use the keyword in Plutonic.cfg). Turned off (NODEFREFLOW) the default answer is NO. To test these routines out, I'll be using the external editor as much as possible this week (internal one is unchanged), and use the NODEFINTERNAL keyword to this aim. Please do likewise! Oh, one more thing, I had to change my Signoff lines to prevent Plutonic reflowing THEM. Initially they were: SIGNOFF1 Regards, SIGNOFF2 -Peter! But they became SIGNOFF1 Regards, SIGNOFF2 -Peter! One added space in front stops the reflow. o Changed the psuedo control character in $) Printed messages from "@" to "^a". This finally brings Plutonic into line with PlutScan and PluText. o Changed keyword syntax. Previously keywords of the form ADD___ would be made negative by using NO___. They are now in the standard form NOADD___ to bring the program into line with other mail software. For this version, NOADD___ and NO___ are NO LONGER SYNONYMS. You will now HAVE TO change any of these old keywords to the new form: Old Keyword New Syntax ----------- ---------- NOTEAR NOADDTEAR NOMSGID NOADDMSGID NOPID NOADDPID NOSEEN NOADDSEEN NOPATH NOADDPATH o Definitely made one other change to this yesterday, can't remember at all now what it was... 1.98 Beta X (27 Oct 1994) ------------------------- o Now clears the screen before a Jump to Message #, several other cosmetic (ie display) changes not worth mentioning... o Re-worked the One Line Summary function to allow you to get a summary and then Read AND Reply from that summary. Works really well - try it! I tend to ignore the One Line Summary part of Plutonic, reading ALL messages in their entirety - but now this section has been re-worked, I think I'll be using it a LOT more now, especially in high traffic areas. o Much larger Tagline file included in the archive 1.98 Beta W (24 Oct 1994) ------------------------- o Changed default colours - Use the SCREEN? command in the config if you want the old colours, use these lines: Screen0 000 Screen1 F11 Screen2 1F1 Screen3 FF1 Screen4 55F Screen5 F1F Screen6 1FF Screen7 FFF o Now clears the screen before a Set Last Message Read. 1.98 Beta V (20 Oct 1994) ------------------------- Probably more features added than I've ever added in a week, and DEFINITELY more features than I've ever added in a day. Plutonic is going to be publicly released THIS MONTH, hence the massive efforts! o Woops! fixed a tiny bug in Netmail messages by adding a carriage return at the end. The Via line was being added by TrapToss on the same line as the tagline. o Regarding NETMAIL replies to ECHOMAIL messages. The address of the sending system is difficult to obtain. Strictly, it's in brackets at the end of the origin line, but scanning through text and trying to parse an origin line boggles the mind. What if the origin line is malformed in some way? (EG missing brackets, too long, not having the node number there at all, having it there twice, being truncated, etc, etc). What if there WAS no origin line at all, or maybe MORE than one origin line (it happens). Finally, what if the system the message came from had an error in the setup, and this node number was wrong? (Maybe from the wrong net, or simply the wrong address). Previously, Plutonic was just using as a predicted return address the address in the header - which is the system that you picked the echomail up from - almost never the system that wrote it. As a result you had to remember to write down the return address before embarking on a Matrix reply to echomail and type it in manually, or display the origin line when you're finishing the reply by looking at the end of the quote file. Pluto 198/bV will go a long way to fixing this up now, because it can grab the return address from the MSGID line - if the original message has one, that is. This is working beautifully and fortunately, MOST messages DO have MSGIDs these days. If it can't find the return address in the MSGID because it's not in a valid Fido format, or the MSGID is missing, it still uses the header address as the return address. Be careful, and if the predicted address is ever one of a system you link directly with, you'll have to figure out the address yourself. Don't forget you can always run another copy of Plutonic and look back at the original message if the worst comes to the worst. (But naturally, if there's a valid MSGID line there, you're home and hosed!!!!) 1.98 Beta U (20 Oct 1994) ------------------------- Not released. o Added support for a random tagline to be appended to the foot of your messages from a textfile of taglines. This was pretty easy to add, and gives Plutonic one of the nicer "show-off" features of other editors. This is achieved by having a taglines file, and the use of two extra keywords: (NO)ADDTAGLINE The magical keyword to turn this on or off. Defaults to OFF, so if you want to use this feature, you need to add it to the config TAGLINEFILE Keyword telling Plutonic where to find its taglines. Defaults to a file called "Mail:Plutonic.tags" Examples: TAGLINEFILE BBS:Tags/Plutonic.Tags TAGLINEFILE Work:TagLines (BTW if you do call your file "Mail:Plutonic.tags" you don't need to use this keyword). If Plutonic cannot locate the file, it will act as if you had selected NOADDTAGLINE. Pluto doesn't do much checking on the file, so read on to ensure you get it in the right format. The TagFile Pluto uses is pretty basic, and allows for either one- line tags, or two-line tags. The file is simply an ascii file of plain text. No line should be longer than 74 characters, otherwise it will be truncated to 74 characters. You can use Hi ascii characters in it if you like, however be aware that a lot of echoes have banned the use of them. Each line should start hard against the left hand margin, unless it's the SECOND line of a pair. In that case the second line needs to be indented one (or more) spaces from the left margin. Plutonic will never use the last 80 characters of the file, so the last line should be a dummy. Here's a very short example from the tagline file I'm using at the moment: You have a tendency to feel you are superior to most computers. You have the right to remain silent. You have an ambitious nature and may make a name for yourself. You will attract cultured and artistic people to your home. You'll never be the man your mother was. You're never alone with schizophrenia. This last line will never get used and must start hard against the left edge It's a good idea to add three or four blank lines at the end of the file, too. Mind you, the odds of selecting this last line are pretty slim (depending on the size of the file), but take my word for it - Make sure the last dummy line is pretty long and there's a few blank lines after it. Your luck may not hold! As you can see, the second line of a pair is indented by a space. If Plutonic selects the first line of a pair, it will read in the next line and insert a two-line tagline. Only single and double line tags can be used. Multiple line tags just unnecessarily add to message bulk and are a burden on the network. It's pretty easy, really. You can easily convert tagline files from other point packages for use in Plutonic, probably with a Macro in your text editor. Thanks to Nico Francois for the inspiration for the implementation. It's the same as Spot, which I find to be very neat and unobtrusive. I will include a reasonably large tagline file with this archive. The length of this file will not matter, in theory you could use the Fido Nodelist or an even bigger file, and it shouldn't make ANY difference in memory usage or speed of tagline selection. o Fixed display up in the Nodelist Scanner section. The nodelist is described now as being "nearly 3 megabytes long" rather than "over one megabyte", and the zone you specify in the ZONE parameter is used as the default zone in both the text (previously said 0 - woops!) and as the search default (was previously fixed at 3). o The ZONE parameter would only parse the first character from the config, making multiple digit zones impossible to enter. (Mostly you'd be using a Fido zone which IS only 1 digit). We pull in 6-7 digits now - more than enough. In fact the limit before this variable will overflow is 32767. o Pressing "L" on the main menu brings up a question "Rematch selection Parameters?" This used to default to YES and you could re-choose the MATCH parameters from the areas file this way. Now it defaults to NO and just then reloads the config and areas file on pressing Return. The screen is closed and opened to accomodate any changes you might make to the COLO(U)RS and SCREEN parameters. This way you can change the config, and have the changes take effect without quitting and restarting the program. o If you choose to reply to a message in a different message base, the area name of the base you choose is displayed now. Previously it would simply go ahead and use the area number you typed in. If it was typo'd you'd have NO idea what base your message was going to be entered in until AFTER you saved it and tracked it down! 1.98 Beta T (20 Oct 1994) ------------------------- Not released. o Changing keyword syntax. Previously keywords of the form ADD___ would be made negative by using NO___. They are now in the standard form NOADD___ to bring the program into line with other mail software. For this version, NOADD___ and NO___ are synonyms. The program looks for BOTH words and acts the same regardless of whichever you use. However in a version or two these synonyms are going to be removed to speed up config file parsing slightly, so please change your config file NOW so it becomes less painful later. The keywords this applies to are: Old Keyword New Syntax ----------- ---------- NOTEAR NOADDTEAR NOMSGID NOADDMSGID NOPID NOADDPID NOSEEN NOADDSEEN NOPATH NOADDPATH o Added support for automatic adding of up to three sign-off lines. The keywords are SIGNOFF1 SIGNOFF2 and SIGNOFF3. To save adding to useless echo bulk, I have decided to limit you to three lines ONLY, even though adding more would be simplicity in itself. To use this function, you MUST specify a SIGNOFF1 parameter. This really turns the function on and off. If there is no SIGNOFF1 parameter then SIGNOFF2 and SIGNOFF3 will not be used regardless of whether you have set them or not. SIGNOFF1 defaults to a NULL, so unless you add them to the config, they won't be used. To turn them off, simply leave the SIGNOFF1 keyword out of the config (or simply comment it out). The text used in the SIGNOFF keywords is limited to 78 characters per keyword. If you use a longer argument, it will be truncated. Leading and trailing spaces are NOT stripped from this string, allowing you to indent your signature if you like. Some examples might be: SIGNOFF1 | Peter Deane Fido: 3:622/401 | SIGNOFF2 | Plutonic Development AmigaNet: 41:200/401 | SIGNOFF3 | BBS Phone +61-49-721647 GlobalNet: 54:6101/401 | or SIGNOFF1 Regards, SIGNOFF3 -Peter! (Note that in the above example, SIGNOFF2 since it doesn't exist will be ignored when the program enters them into the message). or simply SIGNOFF1 Cheers, TREV If you are using your own editor, the text will be placed inside the temp file your editor opens. You are then free to change it as you desire while writing the message. If you are using the internal line editor, it will be tacked on to the end of your message AFTER you finish writing it. PLEASE REMEMBER TO NOT SIGN OFF MANUALLY ANY MORE IF YOU USE THIS. I know it's going to be a hard habbit to break, and expect to see a lot of my messages getting two signoffs until I get used to this myself! A blank line is inserted before your signature, there's no need to add one at the end when you write your message. Just get to the last line and go /S. If you should happen to be writing in an area which allows ALIAS names, and you use one, then the SIGNOFF lines WON'T be added to the message, to preserve your anonymity. Naturally, so remote users don't get YOUR signoff, this only works in LOCAL mode. If you've logged into your own system from remote, don't forget to sign off yourself :-) o Added 9 new keywords: NOMATCH1 - NOMATCH9. These do the opposite of the MATCH1 - MATCH9 keywords. Changed the default of the MATCH? keywords to be ON rather than off. o no longer parses the BBSNAME parameter through the text capitaliser routine, so you get it exactly as specified in the config o default for QUOTELENGTH now 32,768 bytes o default for QUOTELINES is now 999 lines. Plutonic won't allow you to quote a line past line 999 of the input message anyway (only 3 digits of the line number will fit on the display anyway) o When asking for an alias, the limit is now 31 bytes, rather than 32. Forgot about the last character of a FromName having to be a NULL. o Added the ^aREALNAME: kludge line. With this kludge, if you use an alias in a message, then a ^aREALNAME: will be added to the message in line with other message editors. This allows extra security and shouldn't be able to be read by normal users on most BBSs. NOTE WELL that Plutonic WILL display kludges to users with a security greater than what you specify in the SHOWKLUDGE keyword, so you may not want to use this at all, or you might like to increase the value of SHOWKLUDGE. The keyword is the longest in Pluto so far: (NO)ADDREALNAMEKLUDGE It defaults to ON. 1.98 Beta S (18 Oct 1994) ------------------------- Not released. o Strips leading and trailing spaces from entered node numbers before giving them to traplist.library to parse. EG earlier if you entered " 3:622/401", an error would be reported and you'd have to try again. 1.98 Beta R (13 Oct 1994) ------------------------- o Revised MSGID number creation to use the Unix timestamp instead of a GFA-BASIC timer value. This brings the MSGID number into line with other programs creating one, such as TrapToss, SkyAreaFix, etc. Also the Unix timestamp won't repeat for 136 years (the old timer value would repeat after about 6 months) making it perfectly FTS-9 compliant. Note well that in the year 2038 AD and beyond, this value will overflow the signed 32 bit variable that holds it, and cause a crash. If Plutonic is still a going concern in 2038AD, can someone please write me a message and remind me to adjust the code :-) (BTW this routine has also been added to PlutScan (for the weekly stats messages) and also in the PlutOne single message door) 1.98 Beta Q (23 May 1994) ------------------------- o _Really_ fixed small problem where Plutonic would always turn the kludges on for remote callers if you have KLUDGEON set in the config. 1.98 Beta P (22 May 1994) ------------------------- o can't remember now, but there WERE a few small operational changes! :-) 1.98 Beta O (21 May 1994) ------------------------- o Added new feature: Echo Rules Text Display. If you have a textfile in each *.Msg directory called "EchoRules" the user will be presented with another option at the top level menu for that area - [E]cho Rules. It's up to you to collect these texts, so as you're reading an area and notice a message with the Echo Rules posted, you can save it off, edit it up a bit, and put it in that message directory. The text needs to be a normal ASCII file (remove the CRs if it's from an IBM), and !MUST! end with a blank line on its own (as usual for most files sent by GFABasic). You can, of course, use this for other than Echo Rules - any old ASCII text is fine. o Another new feature: It's now possible to abort messages that aren't being displayed, in the Selective Read, My Messages Only, and when a user with low security is getting Private messages by-passed on him. Simply press the Spacebar, S, N or Ctrl-C to abort the read. o BugFix: Due to me reformatting my hard drive, and copying messages back from a partition in orderly fashion, I found a VERY VERY serious bug in the message scanning code that causes the Hiwater and Lowater mark to both be set to 2. This only manifests itself when as each message number is discovered they are in perfect sequential order. Normally they are given in a random order and you don't see this! This bug has been extant in Plutonic and PlutScan for several YEARS now, without it being a problem due to your message bases always being on a fragmented partition. There's a new PlutScan to accompany this release of Plutonic, because the same code is used there. Please replace your PlutScan, TOO! 1.98 Beta N (28 January 1994) ----------------------------- o Fixed small bug where I wasn't checking the user's level before showing him the kludge lines as per KLUDGEON and KLUDGEOFF (see beta M) 1.98 Beta M (28 January 1994) ----------------------------- o Cross-referenced Plutonic's Hiwater mark with the one in the 1.MSG file (if one exists) when it is about to create a message, preventing message numbers below the tosser's from ever occuring. This will prevent a few occasions where written messages are not exported due to being below the tosser's hiwater mark. (Mind you, the tosser is probably responsible for getting the hiwater mark in 1.msg wrong in the first place, (up till today Plutonic never touched the 1.msg files!) but the least we can do is fix its mistake). Thanks to Rene Hexel for mentioning this. o New keywords in config: KLUDGEON and KLUDGEOFF. Currently when Pluto loads, it comes up with kludge lines turned off, and you have to turn them on yourself from the change parameters function. Now Pluto will load up with your choice. Defaults to KLUDGEOFF (original behaviour), but you can now change it to (guess?) o added a space into the output when - well - again - see if you can guess where! 1.98 Beta L (5 January 1994) ---------------------------- o If Plutonic figures out that a message you are replying to would be addressed to your OWN name, then it will put the Toname of the message you are replying to as the toname of your reply, rather than sending it from Joe Bloggs to Joe Bloggs. EG: -------------------------------------------- From: Joe Bloggs To : All -------------------------------------------- I have put some new things on my BBS. TTYL: J.B. Joe Bloggs comes back later and REPLIES to the message: -------------------------------------------- From: Joe Bloggs To : All -------------------------------------------- JB> I have put some new things on my BBS. Yes, this includes a great new door!! TTYL: J.B. Instead of posting this to "Joe Bloggs" (the original poster) Plutonic sees the user is replying to a message he has written himself. So it uses the original message's _To_name as the new message's Toname. o Re-defined how Plutonic actually _FINDS_ its config file: Plutonic will first look for "Plutonic.cfg" in the current directory, and then it checks for "MAIL:Plutonic.cfg" If either of these are found (in that precedence - current dir over MAIL:) that will be the config name we use. If Plutonic has been run from Metro BBS, then _IF_ the program can find a "Plutonic.cfg" in the DOORFILE directory, then that will override all other filenames. o Now parses the UserNames out of messages one is replying to, through the Capitalising routine earlier, to allow use in quote header and enquiring of the user. o Attempted to get rid of messages sent to "y" about "N" (etc) due to users not figuring out Return=Fred - not Y=Fred when replying to messages. If the user does not enter AT LEAST TWO characters for these inputs, then the defaults from the original message will be used instead. This method should be quite succesful. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!! IMPORTANT CHANGES FOR THE AREAS FILE NAME !!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! o Now Plutonic understands ONE command line argument. You can give Plutonic the name of the AREAS file to use from the command line! And! Read On: o New keyword: AREAFILE If specified in the config, then instead of using "Mail:Plutonic.areas" as the areas file, you may specify your own. If the areas file info is given on both the command line and in the config, the command line will take precedence. Default "Mail:Plutonic.areas" Examples AREAFILE "Mail:Configs/Areas.1" AREAFILE "Mail:Plutonic.one" If running from Metro BBS, two methods are available to you to get Plutonic to select its AREAS file: Firstly, since Plutonic looks firstly in the DOORFILE directory for a config file, then you can have a Plutonic.cfg for each door directory specifying a different AREAFILE ine each one. Secondly, you can set the program up as a script, to specify the areas file from the command line. EG Filename of script: "Door25" Contents - 1 line: MAIL:Bin/Plutonic Mail:Configs/MsgAreas-1.cfg (Don't forget to set the Executable and Script bits of the script). Reminder: the command line will take precedence over config if you use both methods. In any case, these two methods will do away with ALL renaming scripts for Plutonic.areas. A "Plutonic.cfg" file is still needed, but it can be in either the door's directory, the current directory or Mail: 1.98 Beta K (14 December 1993) ------------------------------ o Added new feature in the Set Last_Message_Read routine to allow you to change your LMR back to what it was when you entered that message area. It will remember what your LMR was for as long as you stay in that message area. 1.98 Beta J (21 November 1993) ------------------------------ o Fixed a small bug which left a RAM:MsgBody.tmp file around if you selected "NO" after doing a $Footer Edit o Made available the FLAGS and COST information from the nodelist. You'll see this in the Nodelist lookup function, and in netmail replies and posts. o Made the Netmail replies use the 4d information for Netmail replies. You WILL notice this! And this is one of the major changes I wished to make. 1.98 Beta I (17 October 1993) ----------------------------- Still not out. Okay, all I really need to do now is re-write the message-text inputting routine, and make use of the 4d mode in netmail replies if you have it switched on. Users of Multinet TrapToss systems will then find ALL their zones correctly guessed. o Added a quick Message Cloning facility in the $)ysopOptions menu. This simply copies the message number you are viewing to the msg number above the hi message mark. You could then later use Headit on the message as a primitive form of cc'ing; or keep an important message from being buried among other replies. A hundred and one other uses. To undo an accidental selection of this, simply delete the message thus produced. Second thoughts maybe a confirmation? question could be added later... WARNING: Ensure you are aware of the status of the SENT bit. If you don't want the message to be re-exported ensure the SENT bit is set on the copy produced. (Alternatively, ensure the netmail message is addressed to YOU or one of your AKAs - the latter only works in netmail, though). 1.98 Beta H (15 July 1993) -------------------------- o New keyword (NO)ACTIVATEWINDOW for loading in remote mode. Up to you now whether the program goes quietly to the back, or will pop to the front. *In local mode it will always pop front and activate the window* o Now YOU can give values for all the 8 screen colours Pluto opens, using the SCREENx keyword in Plutonic.cfg! The keywords, along with the DEFAULT settings, are: SCREEN0 0 SCREEN1 F11 SCREEN2 1F1 SCREEN3 FF1 SCREEN4 55F SCREEN5 F1F SCREEN6 1FF SCREEN7 FFF Please note that the values are for RGB settings and HAVE to be in HEX. The left digit representing red values (0-F); the middle green, and the rightmost giving the blue setting. Decimal entry is NOT suppported yet, and probably won't be given that the HEX is most useful for this anyway! o Echoes "F" now when Footer Edit code starts. 1.98 Beta G (02 June 1993) -------------------------- o Added a THIRD option for the $ Print Msg function. This adds an OverWrite option to the Append (default) and Abort. o Your config can now be in either UPPER or lower or MixEd case!! Keywords previously HAD to be in capitals. I decided to stop being lazy and improve the parser to make things a little more user-friendly! 1.98 Beta F (30 May 1993) ------------------------- o Bug-swatting time for all the bugs introduced by the new features last version. Nothing very major, though. o Fixed up fourth line gadget co-ordinates (was 2 pixels too low) o File attach from Headit now uses the same default directory as the rest of the code o The "Are you sure?" requester taken out of the QUIT function from Headit (you can always easily get back there - just don't forget to save your changes!!) o Made .0 the default for point numbers in the destination and origin node number fields in Headit (was previously whatever was there, meaning if the original address said 3:622/401.2, and you typed in 3:711/439, it would pop back up as 3:711/439.2) o Fixed a few smallish picky bugs around the place, including a strange long integer->real transition that appeared to happen to three or four variables, including one memory allocation pointer (Danger is my game). I don't know how this happened. A few versions ago they were long integers, on looking through version E, they'd become reals. Weird. o Sanity check on NextReply and ReplyTo values, disabling access to these message numbers from the Chaining if they are out of the range of lowater <= number <= hiwater 1.98 Beta E (27 May 1993) ------------------------- o About a thousand lines of code has been added to Plutonic for two new sysop functions in local mode (ONLY!!) Press $ after a message has been displayed to access these functions. o Implemented the Headit program into Plutonic to edit message headers. o Added the ability to edit the body of a *.MSG from your defined editor. 1.98 Beta D (21 May 1993) ------------------------- o Added new keyword so you can turn on file attaching in TrapToss (made necessary by us routing BRE files for a local system). The keyword is: (NO)FLOATTACH Turning it on (FLOATTACH) will make Pluto act in the current way of creating a FLO file for any file you attach. This is the default. Turning it off (NOFLOATTACH) will mean the FULL path/filename is copied to the subject field; leaving TrapToss itself to make the relevant .DLO file (which can then be later CHANGED in TrapToss if need be). o Fixed up the $ Print Msg function to add APPEND mode, and a few other enhancements in this section, you'll see, such as giving up on the default PRT: filename (I only used this while testing it when I wrote it - they all get printed to files, here!) o Changed the quoted material to remove the SEEN-BYs. This means you may have to $ Print the message if you want to include any SEEN-BYS. The $Printed copy is better for these purposes because it has ALL the kludge lines and header info, anyway. The origin line can still be quoted back, it's just that the SEEN-BYs were a little harder to remove because they don't get pre-ceeded by a Ctrl-A 1.98 Beta C (19 May 1993) ------------------------- o Shortened these notes. o Added the (NO)DEFINTERNAL keyword. If this is set, the question asked when you load the editor (in local mode) will default to the internal editor. If this is false (NODEFINTERNAL) this will act the same way as Plutonic always used to. The default is DEFINTERNAL (IE "Use your own editor (y/N)?") o Added the (NO)DEFATTACH keyword. This defaults to off (the way Plutonic currently works). If you turn it on (DEFATTACH), then you will change the question to do a file attach to "Attach a file (Y/n)?" This is useful if you keep forgetting to attach files like me, and you can just hit the cancel gadget in the requester to get out... 1.98 Beta B (8 May 1993) ------------------------ o You can now reply in ANY base to a message. Please check this (ie so that it won't let you post into an area you don't have security to WRITE into; or returning you to the correct area, etc) o Added Kill-Sent bit option to netmail o Fixed a problem where a '/' was appended to a directory name, even when it ended in a ':' in about 3 places (out of 20-odd) 1.98 Beta A (25 April 1993) --------------------------- INTO BETA MODE WHILE HEAVY WORK GOES ON o Added a search facility based on any or all of the fields: FromName, ToName, Subject, Date. o Added (NO)MATRIXPID keyword, so you can set whether you add a PID to Matrix Mail. Default is on. Note that we don't go adding tearlines to Matrixmail, so you now have full control of this, PID or None. o fixed up default for 4DMSGHEADER to be ON. (Was off in 1.97 despite what the docs said. The docs are now correct without having to change them! o Added two reserved keywords for future use. 1.97 (21 February 1993) ----------------------- o Not public o changed the year in this file to 1993... o New Keyword (NO)GATEROUTE. This will work on matrix mail to either send any INTL messages to the ZoneGate or just to the address of the system. Previously, Plutonic would correctly Gate Route mail; but TrapToss never used this part of the header anyway. The default function is NOT to gate-route, which IS a change in the way Pluto works. But if you use TrapToss, you won't notice any difference. NOGATEROUTE is the recommendation now. o Tweaked the message-scanning code a little when you do a elete Whats.here. Now all should be sane, and a little more accurate. o Upgraded the message printing facility to bring it into line with the displayed format. Now includes TimesRead, and if Matrix, the From and To addresses (in 2d or 4d mode). 1.96 (10 February 1993) ---------------------- o Not public o Added sanity check for message area numbers when changing configs and loading up. o Added in From and To addresses to netmail directories. This is done using a new keyword (NO)4DMSGDISPLAY. Turning on the 4d display will be very useful when using Traptoss 1.5; but for now it will really only work properly on messages created by Plutonic itself. Turn it off if the weird Zone and Point numbers bother you. 1.95 (28 January 1993) ---------------------- , I accepted the task of Beta Tester of TrapToss, and thanks to Rene I have version 1.47 of the program to use and critically look at. I'll be trying to take advantage of the new features offered in TrapToss, and make Plutonic a little more subservient to TrapToss itself. Mind you, I will keep it generic, but I'll be looking to take advantage of the new features of TrapToss, which isn't far from public release. o It is immediately apparent that the move is toward a single netmail directory, coming with TT 1.50. As a result, for each netmail directory, the last question the program asks when posting a message is which address to use as the origin. Currently it's not very intelligent as to the default, and use will need to be made of the destination of the message to determine where it will really go. Use it for now, it works, but more typing... o Full four-dimensional FTS-1 *.MSGS will now be produced (by default). To not do this, use NO4DMSGHEADER in Plutonic.cfg. You should note that the default is by far the optimal way to store messages, and can be used with any version of TrapToss. In a MultiNetwork environment, the newer 4-d storage will be of great importance, so please use it now by simply not changing your config (or including the word 4DMSGHEADER in it somewhere). The old mode has been used for possible compatibility reasons only, and is a bit suspect anyway! o When being run off the BBS (more strictly if a RAM:Userdata file exists) Plutonic now looks in the door directory specified in that file FIRST for its config (if it doesn't find one it will still look in MAIL:). This means that if you wish to run the program multiple times, you can use the Plutonic.cfg to influence how Plutonic is run, for EACH DOOR DIRECTORY you use, without any need for renaming scripts. EG if you run Plutonic as Door25, then it will look in BBS:DOORFILES1/DOOR25/ firstly for a Plutonic.cfg. If you run it as door 59 then it will look firstly in BBS:DOORFILES2/DOOR59/, etc, etc. This will be handy when used in conjunction with the next added feature... o The MATCH feature has been introduced to select groups of message areas. In Plutonic.areas, each second line has a 'name' of the message area. It's used for display and easy reference. Now, you can precede this line with a single digit (0-9) to filter your message areas into groups (eg all Fido mail might be group 1, GlobalNet might be group 3, etc). To specify this, simply edit Plutonic.cfg so that each number 2 line has a digit in front of it. To retain current behaviour, simply ensure that every second line has NO digit as the first character, or add a 0 in front. EG Say the area initially said: MAIL:Matrix Fido NET Mail 1 2 This origin line is not used, but MUST be here!! 3:622/401.0 MATRIX KEEP 70 If we wish to put this in group 1, simply add in a 1 before the area description (every 2nd line): MAIL:Matrix 1Fido NET Mail <========= 1 2 ... A line commencing with a 0 or with a non-digit character will be classified as group zero. Group 0 echoes ALWAYS display in Plutonic. There is no way to turn them off. It is always a very advisable idea to always have AT LEAST ONE group 0 echo area, simply to avoid the problem of loading up Plutonic and not being able to find ANY areas to choose from! The other groups, 1 to 9, are up to you. Any area can be classified as anything, as messages from ANY group are selectable from within Plutonic.cfg. Areas not loaded, incidentally, do NOT use any memory space at all while the program is running. To choose which areas you will be reading, simply include an appropriate MATCH statement in your PLUTONIC.cfg. There are 9 such statements, MATCH1 - MATCH9 (note they are one word, with no space). To select messages from groups 1, 4, 6, 9 then you would need to specify these keywords in Plutonic.cfg: MATCH1 MATCH4 MATCH6 MATCH9 (Pretty simple). To match all areas in your config, simply put in 9 lines, you then make sure of it. Default for each group is OFF, so the word needs to be specified before you can get to the areas! If you have Sysop security, choose the oad Message Areas from the main menu, and you will see that you can toggle each of the areas WHILE THE PROGRAM IS RUNNING. This obviates the need to have to edit your Plutonic.cfg all the time. If you have a lot of areas, then just use a few MATCH statements in Plutonic.cfg to start you off, then switch them on and off as you need to as you use the program. 1.94 (2 Nov 1992) ----------------- o MAJOR bug where nodelist support was turned off. All netmails were being sent to 0:0/0.0. Blast, this was in the first public release! I simply didn't notice it because I've always had a nodelist... o On a Matrix Write, the system address is asked for firstly. It will then check the nodelist and the to-name defaults to the sysop of the system you are writing to. (Naturally, you can still type in the To-name - you HAVE to if there's no nodelist entry for the node you enter, of course) Beware! Sometimes you want to write to 'AreaFix' instead of the Sysop! o New configuration keyword: (NO)TRANSAMIGA Doc extract: -------------- (NO)TRANSAMIGA -------------- Plutonic used to create a Message.BBS file in the message directory for the benefit of TransAmiga. The reason this is done, is because TransAmiga, unlike Plutonic, accepts the index pointer's word for the number of messages in a base absolutely. So if the REAL hiwater was 10, and the index said that it was 8, the next message number Transamiga saves is 9.MSG :-( Plutonic checks its index and then also checks if a message EXISTS before it uses that message number (bumping it until it finds a number that DOESN'T exist). So if you are running a dual system (or running Pluto off Transamiga) users can safely write messages in Plutonic that WON'T get overwritten by TransAmiga itself. This action was hard-coded previously. Now it's in the config. If you DO NOT wish to create Transamiga's Message.BBS files, do nothing. If you do, then use the config keyword to instruct Plutonic to go back to its old behaviour of creating Message.BBS files in addition to its own. Default: FALSE (IE NOTRANSAMIGA) (only create whats.here files, not message.bbs as well) Example: TRANSAMIGA 1.93p (22 Oct 1992) ------------------- This is the same as 1.93, without any possibility of the serial routines being used except by reverse engineering. If you can reverse engineer this sort of thing, then you are good enough to write serial routines anyway, so feel free :-) 1.93 (21 Oct 1992) ------------------ o Well, okay, THIS will be the public release o Fixed up some elements of text output. o Re-aranged the Subject headers. The 'Orig:' (previously of dubious value) is removed, and the Subj: line no longer needs to be truncated. The full 71 characters will be displayed if they're there. 1.92 (21 Oct 1992) ------------------ o This will be the public release. o Fixed up printing back the cursor after an EDIT or INSERT in the line editor (in local mode). o More power to the EDIT funtions in the line editor, dragging the old line into the GFA Form Input routine allowing much more power to change that line with the cursor-keys/delete/backspace, etc. o I doubt this door would run in Iconised mode now. The option will be removed in a version or two. DO NOT PRESS F3 while the program is running. It won't crash - but it may open an unwanted window at times which will be hard to get rid of while the program is running. 1.91 (20 Oct 1992) ------------------ o added the INBOUND and OUTBOUND keywords to Plutonic.cfg (BTW only the OUTBOUND keyword is currently used :-) The INBOUND might well come later. It's not beyond the bounds of possibility, shall we say?) o Added the ability to finally use the thing without a nodelist, by using the (NO)NODELIST keyword. Defaults to no nodelist support, which is the opposite to what it does now. To maintain previous performance ensure you specify NODELIST in Plutonic.cfg. o Quick-start loadups in local mode. Defaults to ANSI, 28 lines and no kludges shown. Use the [A]lter function once the areas load if you don't want these settings. o That's it. This thing goes public today in a limited release. 1.90 (18 Oct 1992) ------------------ o Serial open bug fixed o Plutonic.cfg keywords now must all be specified in uppercase. EG NoMSgid WILL NOT WORK! NOMSGID would, however. 1.89 (16 Oct 1992) ------------------ o Command line parsing now in place. This only applies if being run of another BBS than OzMetro, and not to the freely distributable release. Please just be aware that if you run Pluto WITH a command line or partial command line, it MUST be correct. If Pluto stops running now, printing up usage details, then you do not have a non-blank argument field after the command. (EG "plutonic ." - which would have worked before). o Fixed up blank name alias bug in the REPLYs now, as well as POSTs. o Set the minimum you can have LOASCII to a value of 15. This is because of important Ctrl-Characters in this range that I need control of. If you set a LOASCII value of less than 15, it will now be adjusted to 15. Just thought you should know. o Prevented the entering of arrow keys in the internal editor. o Implemented another Sysop option after each message is displayed, IE Print Message. Pressing $ (to access sysop functions) will reveal a new option if you are in LOCAL mode - P)rintMsg. Press P and you'll be prompted for a filename, which defaults to PRT: You can enter any valid amiga filename. If the file exists, you will be warned, and prevented from using that name. Note that the PRT: (printer) is quite a valid option. Make sure your printer is ready to run with power and paper, and in an online state! For making quick files, I suggest the use of the RAM: disk. The messages can then be incorporated into subsequent messages you write, for instance. This feature is not available to anyone with Sysop security if they are remote. Only local console. 1.88 (15 Oct 1992) ------------------ o Added a few more keywords to the config. They are o ATTACHDIR This is the default directory where the File Attach file requestor will look in for files. Was previously just SYS:. Now defaults to SYS: only if you haven't specified it in the config o DEVICE Will default to 'serial.device' but if you want to use your own device, then fine... o UNIT <#> Serial unit NUMBER, defaults to 0 o NOMSGID/ADDMSGID Defines whether or not a ^A-MSGID line is added to the messages. Currently, I am letting TRAPTOSS add the MSGID lines around here. Plutonic will generate its own MSGID number for you if you like, but TrapToss does it better. Up to you which method you use. Make sure that if you don't get Pluto to add a MSGID you specify ADDMSGID in your TrapToss/Fido .cfg o NOPID/ADDPID Defines whether or not a ^A-PID line is added. Works in conjunction with NOTEAR/ADDTEAR (qv). o NOTEAR/ADDTEAR Defines whether or not a 'blank' [---] tearline is added or an annotated one [--- Plutonic 1.xx]. This works in conjunction with NOPID/ADDPID. You cannot specify BOTH Tearlines and a PID. IF you do, the Tearline will take precedence. Make sure you read the tearline options in TrapToss again before using these. Default is to add a TEARLINE, not PID. I find it more interesting where ALL message readers can see it. o NOSEEN/ADDSEEN o NOPATH/ADDPATH The Syntax for these was brought into line with the others. (They are existing features). For the next few versions, the old configuration keywords NOADDSEEN and NOADDPATH will be synonyms for NOSEEN and NOPATH. Please however make the change to the new format now. I will stop looking for the old forms in a version or two... 1.87a (05 Oct 1992) ------------------ o When using a HIASCII value of greater than 140, the soft carriage return which brain-dead software adds to messages, was entering the quotes. Displaying a soft CR on the Amiga CON: window results in the cursor moving back to the start of the line with no linefeed. As a result one could not SEE what one was quoting (although it was all still there - see the line numbers). Now, soft carriage returns will not enter quotes. 1.87 (04 Oct 1992) ------------------ o Just a few more minor things before the point version goes out: o If the input type is 1, that is, a multi-character input, the FORM INPUT routine is used in local mode. This means for things like names, subjects and node numbers you can use the ARROW KEYS for getting around the input fields. You'll notice this change in a BIG way. Shift Left arrow moves it hard left. Shift Right arrow does something you can work out. You can't delete the whole line with a keystroke, however - don't try. I'd know if it could happen.... (GFA v4.0??) o Got Hi-Ascii into the quotes, if you have HIASCII and LOASCII set to numbers close to the limits... (ie wreckless mode :-) (I use Hiascii of 255, and Loascii of 3 now....) o Thought I'd take a big stand against the Re: syndrome. If at any time a subject field should begin with re:, RE:, Re:, or rE: then Plutonic ignores it, won't display it and won't perpetuate it into replies. (It felt like a good idea at the time.. Basically, it's a stand against increasing message bulk) 1.86 (25 Sep 1992) ------------------ o Finally re-wrote the [C]hange Message Area code for SPEED! 1.85 (21 Sep 1992) ------------------ o .FLO files for file attaches when CREATED have the TrapToss filenote set in them. You must have the Filenote command in the c: directory for this to work... o Better quote routine by far. Doesn't re-add initials to already quoted material. Right hand margin extended to 79 columns for already-quoted material. o Fishes out FMPT from messages and uses it for netmail replies. o Changed the "Attach a file?" prompt to Dark Blue, and moved it down a line or two... 1.84 (19 Sep 1992) ------------------ o Memory de-fragging works, in that v1.83 had not crashed EVER for over a fortnight! o I give up on quotes! It seems many people DO NOT comply with the FSC specs, and place a space AFTER the > sign. Anyway, in this version, anything with a > sign in the first 5 characters will be printed in the quote colour. o Fixed dual-line display bug when the More? prompt was printed up in a long paragraph. o Freed up the text-filtering a little. Now you can safely use a HIASCII value of 255 without the soft-carriage returns some inefficient editors left in messages wrecking message display as it previously did. Note that to display Hi-Ascii, the topaz.font will generally NOT do. You need to set your system font to that of an ibm font with the fastfonts program supplied on the WB 1.3 distribution, or, if you have WB 2.0, set the system font from prefs. o Added the feature to delete the whats.here file in any particular message directory (for Sysop level only), thus effectively re-scanning that area for new messages entered without having to Plutscan all the areas. 1.83 (5 Sep 1992) ----------------- Roll on Spring, and a new version comes along. This one adds these features: o 'Secret weapons' against memory fragmentation added. Fingers crossed! o [F]ind New Messages now starts from the message area number you are in, and through back to this number via zero if necessary. (Press [F], you'll see!) Previously it started at message area 1, and went through to the end. o Fixed number entry bug where it would only let you start reading from message numbers of only FOUR digits (ie up to 9999). Now it lets you enter up to five. NB, when you reach 32,767 messages in a base, it's BAD NEWS! RENUMBER IT once it hits 30,000, and delete the Plutonic.lmr file in that message base. (My highest area (AUST_AMIGA) is in the 18,000 vicinity now, but I've been getting that area since I used Chameleon....) o When searching the nodelist for POINTS, the boss number is not automatically assumed. We first search for the point number, and only if there is no entry for it do we then search for the bossnode. As a result, keep your Pointlist files up to date, because we'll be using them now. o Finally prevented a 'hanging' REPLY: kludge left over from if a message reply was aborted. V 1.80 only fixed this in the R>eply to message option, not the [W]rite function (woops). 1.82 (17 August 1992) --------------------- o Few misc bug fixes, but no real functional changes. There wasn't much in this, and I'm NOT writing this on 17 August 1992, so it's a bit hard to recall! 1.81 (19 July 1992) ------------------- o Fixed up a small problem introduced by not scanning all the areas - your New messages on the [F]ind new messages printed not the number of new messages, but the HiWater mark instead! o Also fixed the main screen where the number of new messages reported will now never exceed the number of messages you actually have in the base. o Small display problem in the [J]ump to message while reading messages. Now prints two blank lines instead of printing up at the J keypress without dropping down! 1.80 (19 July 1992) ------------------- o In the [W]rite a message function for netmail, you _HAD_ to type in the Zone details. Now it defaults to the same zone as that you've got set for that area. So basically, you won't need to enter Zone details on Netmails any more unless you're going interzonal. o Fixed a small bug where the REPLY: kludge was added to the NEXT message you wrote if you aborted a message. o Got rid of the load all areas on entry. This is good for you with many message areas (like me) as your remote users will be in the program STRAIGHT AWAY rather than waiting it to go through all the areas. The expense of this is slowing down the [F]ind New Messages function somewhat. I hope it doesn't affect anything else. o Number of new messages reported on the main menu screen is now reduced to the total number of messages in the base instead of simply Hiwater minus LastRead, if this result is greater than the messages in the base.