ac>> BTW, what are your future plans for MsgEd?

> You've heard of hot potatos, haven't you?  :-)  I certainly
> plan to fix reported bugs, and I will entertain simple
> enhancements.

ac> Ok, I have some enhancements and some fixes for you:

ac>   * Perform net/node matching in NetAreas.

ac>     E.g. I have three point addresses (3:633/267.1{at}fidonet, 3:635/727.4 &
ac>     3:632/103.9) all sharing the same NetArea.  When I send netmail to
ac>     3:635/727.1, I want MsgEd to use my 3:635/727.4 address, and _not_
ac>     default to 3:633/267.1.

That sounds messy.  I believe you can change your name dynamically.
How did you expect it to guess the address to use?


Oi, I saw that!

ac>   * Read ^aAREA: line created by the WIMM personal mail scanner.
ac>     User hits Alt+N.  User gets the area list.  Area list automatically
ac>     points to PUBLIC_DOMAIN.

That's a very good idea.  But should it automatically select
PUBLIC_DOMAIN or should it just remain highlighted there, ready
for you to hit enter?  I think automated would be great.  I'd
even use it myself then.  But will reading of the AREA tag and
then automatically choosing the area upset anyone?  I wonder if
Alt-Q and Alt-R should automatically reply in the other area,
but Alt-N should behave as it does now?

ac>   * User cannot edit origin line.

MSGED always rewrites the origin line when it is saving to disk.
You shouldn't be mucking around with control lines anyway, anymore
than you should be able to edit the MSGID.  A definite "NO"
there I'm afraid.  You can set up a different origin line on an
area by area basis though.

ac>   * Alt+H for Help doesn't work anymore.  Maybe I'm too braindead to
ac>     know how enable it. :-)

It works for me.

ac>   * When kludge lines are turned on (Alt+V), and user returns from
is sometimes
ac>     added before the original.

I tried this lots of times, but I couldn't reproduce it.  Please
let me know how to reproduce it, as that is a definite bug if 
you can!

> I will also look at lifting the next
> restrictions on messagebase size (I expect there to be
> restrictions at the 32767, 65535 and 100000 levels).
> Hopefully I can lift that to 2 gig once and for all.

ac> Do these restrictions apply while within the internal editor, or after a
ac> message has been saved?

I'm not sure.  I had just seen code with that sort of assumption
in it.  Which would have caused random failures!  E.g. one thing
I noticed at the 65535 limit was you go in and look at message
number 1000, and when you came out and went back in, you were
back to message number 1!

BFN.  Paul.
@EOT:

---