home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
MSQ2-204.ZIP
/
MSGEDSQ.UPD
< prev
next >
Wrap
Text File
|
1992-02-04
|
13KB
|
325 lines
___________________________________________________________________
Msgedsq 'read.me' file v2.0.4; Copyright (c) 1991-92, John Dennis.
___________________________________________________________________
ALERT1! There has been a slight name change: it is now called "Msgedsq",
and will identify itself on the tearline as "msgedsq 2.x.x[b]".
Where "x.x" is the version numbers, and "b" indicates a beta not
in general release. (Ie. you can't 'freq it). Check the history.doc
file for availability of versions etc.
ALERT2! The CC:'s do not work the way they used to!
ALERT3! To make sure you get all the new key assignments (etc.) you should use
the included cfg file. You can copy over your area definitions from
your old cfg file.
__________________________________
Summary of New features for 2.0.4
_________________________________
-- OS/2 version!
-- Imporvements to the editor code. (again). Fixes to areas where lines
were lost etc. are now in place.
-- New Crosspost feature; you can crosspost to different echomail areas.
-- CC:'s now look different, and are entered differently - check it out.
-- New "followup" reply function; you can followup on a msg, leaving it
addressed to the same person.
-- New multiple attribline feature - choose from different attrib lines.
-- Spawn to ems/xms/int 15/disk.
-- Help screens for reader and editor.
-- Multi-network support has been fixed in *.msg areas.
-- Undelete line function in editor.
-- You can now ESC properly out of most things.
-- Support for the SquishMail config file.
-- CC:'s now support aliases & aliases are case insensitive.
-- Many smaller bug fixes.
(See history.doc if you don't mind the gory details)
___________
All people:
___________
There is a little utility included: keycode.exe , this will print out
the keycodes used by Msgedsq, press "q" to quit. All printable characters
will be displayed, others will have the scancode only. You can use this
to determine the scancode of keys that tyou wish to assign to some function.
Please note the changes to the CC: (carbon copy) usage; this will save you a
suprise later. Also note that when operating in a multi-network environment
and using the *.msg netmail type, you must pick the right address to view
msgs originating from out of your primary zone (that is, if they don't have any
^a Kludges).
Also, *never* turn off ^aMSIGDs unless necessary: they are used by a number
of editors (including this one) to obtain information on the origin of the
msg. Such information that is saved in binary, is lost when leaving your
system, the ^aKlugdes retain it.
__________
New Users:
__________
For a quick start up: edit the area names and change the name & address.
If you have other aka's, put them in and be sure to try <ctrl>-w (or -
'who'). Also have a look at <alt>-s, which lets you change things on
the fly. The cfg file that comes with the archive is setup the way most
would like it.
If you aren't planning on running multi-network stuff, leave out addresses
everywhere, except for your primary address (& pointnet if you want one).
____________________
For Upgrading Users:
____________________
! Please read the bit in the front of msgedsq.doc for information regarding the
copyright of this program. It's there to protect the time I have spent working
on this program; do not worry, it's free and will always be so. (the rest of
the document hasn't changed, except the bit at the end describing how to send
bug reports).
! There *may* be a source release in the *future*, tho it may be protected by a
copyleft or something of that nature. Please don't ask; I will release it
when i'm ready.
A detailed description of the new features:
__________________________________________________________________________
Version 2.0.4 (or G4; 2.0.4 is prefered)
__________________________________________________________________________
! Re-worked editor code (again);
The line-dissappearing problems should be gone now. Most wrapping bugs
with quotes and normal text should also be near-dead -- it should be
predictable, at least. You can now space past the right margin to ~4
characters, after wich the spaces will be wrapped to the next line. If
you type a non-whitespace char after the right margin it will be wrapped
immediately, starting on that char (the previous whitespaces will be left
on the last line). You can turn quotelines off by deleting the '>' char
in the first 11 chars of the line. You can turn a line into a quote the
same way.
! Crossposts:
It is now possible to enter a message in one echomail area and have the
same message copied to other areas of your choice. Simply precede the
message text with the first line being:
xc: tub,maxdev,muffin[,...] |the "[,...]" means you can continue|
|area names are case insensitive |
With "xc:" on the first line, starting in the first column. If you have to
go to another line, use a hard CR (ie: enter/return) to terminate the line
and begin the next line with "xc:". It will stop looking as soon as it
encounters a line not begining with "xc:"; the "xc:" lines will be removed
and replaced with:
* Crossposted in area "MUFFIN"
* Crossposted in area "MAXDEV"
* Crossposted in area "TUB"
! New CC:'s operation.
CC:'s are now typed out differently to previous versions; you must type them
out like this:
cc: mike,david nugent!3:632/345,rich
cc: joe,paul marwick!3:711/234
(NOTE: there must be no spaces, except those inbedded in a name)
The '!' character delimits an address for the preceding name, if this is
specified the name will NOT be looked up. If an address is not present,
first the aliases will be checked, then the usual fidouser.lst. Note that
with aliases, the alias is replaced with the name, as in the following:
(using the above, assuming message was addressed to Linclon Dale)
* Carbon Copies sent to:
Lincoln Dale, Michael Studte, david nugent, Richard Dale, Joe Bloggs
paul marwick
As you will have noticed, the "cc:" lines are deleted and a copy of the
new message is sent to all those listed in the "cc:" lines PLUS the
original destination of the msg. NOTE: The original message is left as
it was; you can now edit it and re-send all the cc:'s by re-saving the
message. It will have the "hold" bit set, so it won't get sent.
The text should begin straight after the last "cc:" line as ONE '\n' is
inserted after the " * Carbon..." bit. If the names will not fit on the
first line (going by the right margin) then it will continue on the next
line.
! Followup; "followup" in cfg file (key assignment).
This function defaults to <Alt><U>, and quotes the current message, and
leaves it addressed to the original desintation.
! Help!
You can get help in the Reader and Editor by pressing <Alt><H>. The keypress
will clear the screen and read in a file specified by the user in the cfg
file. The keywords to specifiy the files is:
rhelp rhelp.hlp ; reader helpfile.
ehelp ehelp.hlp ; editor help file.
! Undelete; "undelete" in cfgfile (key assignment.
You can now undelete the last 30 lines you deleted.
! Multiple attribline; "attrib" in cfgfile (key assignment).
You can have up to 10 attrib lines, plus the ability to change them as
you like. The select function is <Ctrl><A>, which will bring up a list
of your attrib lines.
Note: the "%e" and "%i" characters have been added to the attrib line parser,
"%i" is the fIrst name, and "%e" is the Echomail/nEtmail area name.
! SquishMail cfg file support.
You can direct the editor to read an areas.bbs file OR the squish.cfg file.
the keyword usage is:
areafile s|a [name] |the '|' means "or"|
The s|a is not optional -- 's' = "squish.cfg" and 'a' = "areas.bbs".
If you specify a name, it will try that before trying for the default names.
For squish.cfg, passthru areas will be ignored (ones with "-0"), it will
get the primary address "-p" as well as the correct msgbase type (*.msg or
squish. Note: The default is *.msg -- NOT squish).
If you put this line BEFORE the areas in msged.cfg, WITH a filename, then
the areas in that file will appear first on the picklist. If you do not
give a filename, the default files will be checked (Squish.cfg and areas.bbs)
and the areas will appear after the ones defined in msged.cfg. If you do
not want msgedsq to check either, simply comment out that line in the config
file (then it will only use areas defined in msged.cfg).
! A warning has been added when you try to change and already sent/scanned
message.
! The <end> and <enter> keys operate differently by default; due to the fact
that squish lastread pointers cannot hold the highest-read information
(which the old sysop lastread file did), the "unread" bit in the area
pick list will show the amount left from the current message in that area.
Within a squish area, the <end> key will take you to the last message, the
<enter> key will take you to the first message read when entering the area.
If you don't like this, you can put the keyword "compat" in the config file,
it will then operate like the older vesions of msged and msgedsq.
! Note, the "remap" verb has been removed: it is now obsolete. Msgs in
*.msg areas addressed to a zone not equal to your primary zone will
automatically get a ^aINTL:, to help squish determine the destination.
! A note on timestamps: when moving & forwarding a msg, the timestamp will
be altered to relfect the current time. When changing a msg, the time
will NOT be altered, same for copying a msg. This is to avoid dups of
the same msg appearing on the net.
! Note, aliases and "xc:"'s are all case in-sensitive.
_____________________________________________________________________________
Version G3
_____________________________________________________________________________
■ Aliases. "alias" in cfg file.
This is mainly for points and bosses with points (and people who don't wish
to keep a fidouser.lst file). In the cfg file you specify an alias, viz:
alias jb,joe bloggs,3:23/234.2
And when entering the destination name, you simply type "jb". The rest will
be filled in for you; simply press return. You can specify as many as you
like in the cfg file. At the moment, this does not work with cc's.
■ First keyword. "first" in cfg file (key assignment).
This is automatically assigned to the <home> key, it is assigned in the cfg
file using "first". It moves the user to the first message in the message
base. If you want to use this you will have to comment out the "home" key
assignment standard in all cfg files. The "home" function now takes you back
to the message you started on in the current area, it is not assigned to any
key.
■ QQuotes keyword. "qqotes" in cfg file.
This entered in your config file will make the quote code quote everything
in the message you are quoting, specifically including quotes. eg:
RD> JK> What's goin down dude?
RD> nothin' down this part of the world...
well, i don't know what you guys are talking about! this place is full of
life...!!
Without the qquotes keyword, it will look like this:
JK> What's goin down dude?
RD> nothin' down this part of the world...
well, i don't know what you guys are talking about! this place is full of
life...!!
It all depends on what you like :-)
■ No Remap. "no remap" in cfg file.
This is needed when operating a mulit-network node using a *.msg netmail
area. Due to a lack in the *.msg format, zone information is not stored,
and when your packer is packing out the mail, it will have trouble sending
to the right zone; unless you give it a chance (read: more information).
If you are at two addresses (and running *.msg :), say 3:690/626 and
61:345/32, to enter a message to a zone 61 address, you must be using your
zone 3 address. With "no remap" in your cfg file, this will produce a
^aINTL; without it it will automatically readdress the origin address to
your zone 61 address. There is a solution to this; start using the squish
format for netmail areas - the squish format is capable of storing both
zone and point information and you can then enter zone 61 (for example)
mail and it will be scanned out to the correct zone. (if anyone has
suggestions on how to handle the *.msg problem, please send them).
■ Sqllast. "sqllast" in cfg file.
This existed in G2, but it's changed to being NOT the default. Put this
in your config file and it will store the highest message that you read in
the lastread file. Comment it out and it will store the last read message.
_______________________________________________________________________________
John Dennis, Jan 25th.
3:690/626.4@fidonet.org
john@miyu.dialix.oz.au