home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR36
/
TIMA10C.ZIP
/
WHATSNEW.A10
< prev
next >
Wrap
Text File
|
1993-09-26
|
10KB
|
244 lines
New in alpha 10c:
-----------------
* TimEd would regard (JAM-) messages with an empty TO: field as
deleted..
* Specifying the 'd' (direct) attribute in an Area configuration line
in timEd.cfg would lead to a complaint ('junk attribute'), although
it would actually work correctly. Fixed.
* When using 'RAMSG purge' and 'RAMSG pack' WITHOUT renumber (now
possible with the RAMSG provided with RA 2.01), creating a new
message in a JAM area would lead to very strange en undesirable
things (but certainly not a correctly generated message :-).
* The area information screen (pressing ALT-I in an area) would not
always show the correct message base type. Also note, that 'purging
info' (Maximum number of messages, number of days to keep msgs etc)
is only available in Squish area. In *.MSG and Squish areas, it
simply does not exist!
* In addition to ALT-<right>, you can now also press ALT-+ (so hold ALT
down and press '+') to go to the 'next reply'. ALT-<right> is not
available if you use the cursor keys on a numeric keypad..
* Tried to improve detection of the right zone for *.MSG areas
(netmail). In *.MSG areas, zone info is often not directly available,
and timEd would sometimes have to 'guess' for the right zone. It
would then take the zone of your main address. This often went wrong,
so I tried to improve it.
* Changed AKA matching logic a bit. TimEd won't change the address as
easy as it would before. If you don't know what I'm talking about,
you didn't have the problem anyway.. :-)
* Added a new type of macro's: USENETMACRO. This works very similar to
a 'normal' macro, but you can also supply a 'usenet style' name, that
will be placed in the body of the message (TO: art@beard.next.nl for
example).
The format is as follows:
USENETMACRO Usenet_address, toname, [toaddress], [subject]
The last two items are optional.
Usenet_address should be an address like art@beard.nest.nl.
Toname should be the name to be filled in in the TO: field. Usually,
this will be 'postmaster' or 'uucp'.
Toaddress is the address to send the message to, usually the address
of you Usenet <-> Fidonet gate.
An example:
My Usenet <-> Fidonet gate is 60:60/0, and I want to send a message
to art@beard.nest.nl (why would I send a message to myself? :-). A
macro could be:
Usenetmacro au, art@beard.next.nl, postmaster, 60:60/0
When entering a message, I can now just type 'au' in the TO: field,
and timEd will automatically fill in 'postmaster' in the TO: field,
60:60/0 in the to-address field, and leave me at the subject field.
When I start to edit the body, 'TO: art@beard.nest.nl' will be placed
at the top of the message.
New in alpha 10b:
-----------------
* The % counter at the bottom of the screen (when reading a long
message) would sometimes go crazy. Fixed.
* Added several extra variables to be used in the 'hello' and
'rephello' strings:
%subj : subject of the message
%orig : address of the sender of the message (2:281/527)
%dest : address of the recipient of the message (2:281/527)
%time : time the message was written (01:25)
%year : the year the message was written (1993)
%mon : the month the message was written (jan, feb etc)
%day : the day of the month msg was written (a number)
%dow : the 'day of week' msg was written (mon, tue, wed etc)
In the above, 'the message' is:
When doing a reply: the message you are replying to.
When creating a new message: this new message.
When using alt-O (follow up): the message you are 'following up'.
* Reading fastecho.cfg would fail (out of memory!) if you had only one
address in your fastecho setup.
* When replying to a message, that (original) message would lose its
kludges, when timEd tried to update the reply-links (in JAM areas
only). This may lead to RAMSG complaining about 'invalid JAM
signatures' when doing a 'RAMSG pack'. Right now, timEd doesn't
update reply links itself. Problem solved :-)
* Reply link logic (displaying it) was wrong (for JAM). Now, all
replies (with a maximum of 10) to the message that is on-screen are
shown.
In addition, you may see a number between brackets, like this: (25).
That means that there is _another_ reply to the original message (it
can only show up if you are reading a reply to a certain message).
Pressing ALT-right will let you jump to that message.
An example:
You are reading message #5, it shows:
25 30
at the top. That would mean there are two replies to this message,
number 25 and number 30.
You press ctrl-right (to get a pop-up windows, displaying who wrote
both replies), and choose the first reply (number 25).
This message (number 25) may show:
550 (30)
This means that this is a reply to message 5, that there is a reply
to this message (the reply is number 50), and that there is _another_
reply to the original message (the original message was number 5),
and that the number of that other reply is number 30 (which is
exactly what message #5 showed us).
Confused? You should be!
Simple: if there is more than one reply to a message, you can press
ctrl-right, go to the first reply, and then keep on pressing
ALT-right to read all other replies as well. When you reached the end
of all replies, you press ctrl-left to go back to the original
message again..
Remeber, this only applies to JAM style areas.
* In *.MSG areas, use of 'INTLFORCE' could lead to two (!) INTL kludges
in some cases.
* Worked on the area scanning routines a bit (normal scanning, from the
Area Selection Screen - not the personal mailscan). For packed (RAMSG
pack) areas, scanning for new mail should be faster now.
New in alpha 10a:
-----------------
* The spacebar has the same function as <page down>. When the end of the
message is reached, however, it will function as <cursor right>. This
way you can read all pages of all messages in an area by just pressing
<space>.
* When an area defined in Squish.cfg (without a -$) was also defined in
areas.bbs (but now starting with $), timEd would see it as a *.MSG
area. Fixed.
* The delay built in 'End of area menu' is removed.
* Flushing of the keyboard buffer was changed. This should solve the
problems with the 'ALT-M' (Move/Copy/Forward) menu popping up when
the right arrow key was pressed..
* TimEd now also supports the Fastecho configs directly. Put
"FastechoCFG <path+name>" in timEd.cfg to have timEd read the
ECHOMAIL areas from fastecho.cfg. Yes, only the ECHOMAIL areas (just
like reading Squish.cfg).
* Maximum number of AKA's increased to 25.
* Added a new command to the ('maintenance/Util') menu that pops up if
'ALT-U' is pressed from the message reading screen: execute mail
processor. This command will write out the echotoss.log if (if
applicable) and execute 'mail.bat' (or mail.cmd for OS/2 systems).
You can use this to spawn your echomail processor, without the need
to exit timEd.
* The OS/2 version had problems with Squish indexes larger than 32 Kb
(+/- 2400 messages). This should be no problem anymore.
* Tried to fix weird problems with large *.MSG areas, and copying/moving
msgs to such an area from the list mode. Looks like strange compiler
bugs to me :-(
* In environments that do not use the 'opusdate' for *.MSG messages, the
MSGAPI could ruin a message if only the header was updated (messed up
kludges etc). I tried to work around that now...
* When defining an area in timEd.cfg, you can now also specify 'direct'
as a standard attribute with the -A switch (use 'd' for this attribute,
like -Apd for 'private' and 'direct').
* Macro's with a 'to-address' that had a nodenumber of 0 (like 2:280/0)
did not work correctly.
* The 'macro' keyword only worked if it had (exactly) one space behind
it..
* The 'ALT-H' (edit hello-strings) screen would only show the actual
contents of the 'hello-strings' when you were actually editing them
(just pressing ALT-H didn't show an overview of the actual strings). It
does now..
* AKA matching is now only active when entering a new message, not when
C)hanging a message (of header). You can still force a match by
pressing F2, of course...
* C)hange a message (or header) would trap on zero-length messages.
* If no echomail had been entered, timEd would write a zero-length
'echotoss.log' file. Not anymore! :-)
* Fixed a problem with the CC: checking routines. This could up in any
netmail message (even without CC:'s). It would cause lockups and
traps, and occurred if a message immediately started with a paragraph
longer than 256 characters..
* Fixed a problem that caused memory loss in *.MSG areas when creating
messages. It looks like this was also the cause of the memory loss
problems in the List mode.
* Forwarded messages can now easily keep the original subject. The
message at the top of a forwarded message now also shows the address
of the creator of the original message, and the date/time it was
written.
* Experimental JAM support. In timEd.cfg, use -J (instead of -$) to
denote a JAM style area. The Fastecho configs are read correctly for
JAM areas too..
An example of a JAM area declared in timEd.cfg:
EchoArea "Gerard (Art) software support" ARTWARE c:\msgs\art -J
Please note the -J at the end. That tells timEd we are dealing with a
JAM style area.