ml> NOTE: see the above? here it is again repaired... this repair took only
ml> two DELete keystrokes... the first at the end of that short line and the
ml> second at the end of another short line that appeared... thie
ml> reader/editor almost has it perfect but this minor fixing is no big
ml> deal... not like trying to repair chopped and/or missing words...

And there you were quoting my post from Mystic, so it seems Synchronet is
not at fault there.

ml> yes, definitely wrong but sorry to say the problem is and has always been
ml> in the editors that do not wrap and flow quoted text... it has been this
ml> way since the beginning of time for editors that do this...

Gotchya.

ml> in this case, both have the same margins... some have a shorter right
ml> margin... the quote prefix is pretty normal... [space]xx>[space]... that
ml> shoves the word "not" past the margin where it should be
wrapped to the
ml> next line but instead it is simply chopped off... now a statement that
ml> was negative reads as if it were positive...

I completely understand what you're saying. And the chopped text annoyed me
at one point too, so I asked for it to be fixed. :)

ml> you probably couldn't do it from remote but as a local only editor,
ml> possibly... the problem is that the bbs generally creates a temporary
ml> file for the editor to errmmm... edit... then when the editor exits, it
ml> saves the file and the bbs imports it into the message base... if the
ml> file has not changed, then the bbs may assume that the edit was aborted
ml> unless the editor exits with a specific errorlevel for an abort as
ml> opposed to normal termination... i rather doubt that nano and vi have
ml> such errorlevel exits capabilities... they are from a completely
ml> different world and mode of thinking... sysop/point editors are local
ml> editors that replace the bbs and its message base interface... they are a
ml> lot more than just editors because they do have to have the message base
ml> support built in...

Then I wouldn't have any interest in it. I still use my BBS all the time.
If I didn't run a BBS, I would have no reason to do any of this. :)

ml> the concept is really simple... starting at the top of the text to be
ml> quoted... determine if this is already quoted text or if this is a new
ml> quote and remember this (hint: boolean)... depending on which it is,
ml> inject the proper quote prefix (existing one plus '>' or the defined

[trim]

I have forwarded this part of the message to him, and mentioned the echo
we're discussing this in, in case he wants to get involved.

ml> i know... i was being nice and trying not to stir it all up again ;)

I'm over it. :)

ml> i dunno... there's two situations with them... one is the nonstandard
ml> format of the originaddr field... i can't make a private reply to that
ml> message based on the contents of that field as generated by synchronet...
ml> 
ml> the second situation is that of generating a MSGID for those messages
ml> without a MSGID... nick andre's posts are a perfect example... they do
ml> not have a MSGID because his system doesn't support FTS-0009...
ml> synchronet creating a MSGID and adding it to messages without one is the
ml> worst of the two situations because that message will not have the same
ml> MSGID on all systems... each synchronet system will create its own
ml> originaddr field as well as its own serial number and that blows
ml> duplicate detection all to hell...

I can see both of those points. I'm actually kinda baffled that it was
blown off and/or ignored as well. Maybe they only want one ball in their
yard to play with? :|

ml> that's the easy part... just remember that there can be more than two 
ml> initials... i would use spaces and periods to locate them... not commas
ml> or dashes, though... well, maybe dashes... depends on how they're handled
ml> by other software for this task...

It would be nice if he joined up in the conversation here. That would at
least show that he's interested anyways. :)

ml> possible but it was also a cheap shot...

LOL! Isn't that how things are usually handled on Fight-o-net? :)

ml>  NB> Oddly enough, Mystic is completely pascal, and seems to quote
ml>  NB> pretty damn good as far as the new proposals. Oddly enough, this
ml>  NB> software has been doing it since it's birth. :)

ml> maybe because the author saw the quote problem(s) from way back and never
ml> let it/them get into his software's editor(s) in the first place ;)

Very possible. Although I did notice something here (above). If I were to
actually quote something already quoted, it doesn't add the '>' to the
original, it adds a completely new one in front of the old. Though I guess
it's still better than now knowing who said what in the first place. :)

--- Mystic BBS v1.10 A21 (Linux)