SGID: 46:1/102 47592442ZUTC: -0400
Zeus IITWILIGHT▐▄▄▄▄▄▄▄
▄▌▄▄▄▄▄▄▄▄░▄ ░▓▓█
░ ▀▀▀█████▌ ▐
▄█▀▀█▄▄█▀▀██▓▄
▀█▄▄▓░▀▀▀▀░█▓▓░
▄▄█▓█▌ ▓ ▓▓
▓▓▐▓▓▓ ▀▀▄
█▄▌▀ ▄▄▄▄▐▓▓▓▓
▐███▌ ░░ ▄
▒ ▌ ▐ ▀█▌
▒▒▒▌ ▐▒▒▒▌ ▐███▌
████▌ ░▓ ▓▓▒▒▒▌█
▓▓▓▒▐░▌█▌
▐▌▐▓▓ █▀▀░
▓▀▀ █░░░█ ▐
▀▌▀▓▒░▄▄▄▀▀▒▒░
░░▌▐▒▒▒░ ░▐▓▄ ▒▒▐▀▀▀▀▄▌
▐▒▒▀ ▓ ▀▄
▄ ░ ░▓▓█▀▀▀▀ █▄█▓▓░ ░▓░▓█
▀ ▄▄█▀ ▐█▄▀██▌▐░░░█▄▄▄▓
▓░▒▓▓▄ ▐▀▓░░
░░ ▄▐█▌ ▓ ▄▄▄▄▄▄▄
▄█ ▐▄▄▀▓░▄▓▓▓ ██
▄█▀▓ ░▓▐
▐█▌▐░▌▒░░░▄▄▄
▄▄ ░▓ ▐▄▄ ▀▌░▓
░▄▓▓ ▀▓░▄ ▐█
█████▌▐▐███▌ ▌▐███▌
▐▓▐█▄█ ▌▓░██▀
▐▌▄▄█ ▄▀▒▒▌
▄▄█ ▐▀█▄ ▌░▒░▓▐█
▌ ▒▓░▐█▌ ▐
█▓▐▄ ▐▓█▓▒▓█
▌ ▐▀▀ ▄▌▐░░▀ █
█▄█▌ ▄▌ ▀▀█ ▄█▌▄ █▌
▐▓▌ ▐█▌ ▐▄██▀
▌▐▌ █▀▀ ▐▄ ▐
▐▐▌▌ ▐███▌▌
▄▄█▌▀▀▀▀█▄▀
▀▀▀▀▀▀ ▄▄▄▄████▌ ▀▀
▀▀ ▄▄████ ▀▄
▐██ █▓▌ ███
▓█▌▐▌ ▀▀▀ ▐█▌
█▀▀▄▄▄▄▄▄▄▄▄ ▀▀▀ ▐▀▄█▀
▀▀▄▄▄▄▄▄▄ ▀▀▀▀▀ ▄▄▄▄▄
▄▄▄▄ █▓▌▄▄▄▄▄▄▄▐▓▄█
██ ▐▐ ▀▀▄▄▄▄▄▄
█▀▄█▐▀▀▀▀▀▀▐▀▀░
█▀█▀▀▀▀ ▐▄▄▀▀▄ ▀▀▀▀▀▀▀▀▀
▀██▓▓█ ▄▄▀▀ ▄▄▀
▐▐▓▓░░▌▌▀▀▐▀▀▀▀
▀▀▀▀▀▀▌▀▀▀ ▀▀▀▀▀▀ Fl
uph!▀ Operated by some cunt
Will save it, and if the blank is still there will atemp to edit it.
Skuz dA FlupHy Squirrel ate my
nuts.... ▄▄▓▒▀▐▄▌ ▐▄▄ ▄▓▐▓▄▄ ▄▌ ░▄
▌ 09! @ b7 member board▐▓▄
▄▄ ▐▓ ▄▐▓▌ ▐▓▌▐▌▐▓▌░▄▄▓▌ ▄▄▐▓▌ ▀▀▓▄▓▌▀█▄▓▌▐▓▌▀▀ ▐▓▌▐▓▌▓▌
@ http://bbsnexus.com/fluph
--- Mystic BBS v1.11 A3 (Windows) * Origin: fluph.darktech
.org (46:1/102)
--- FastEcho 1.46a
* Origin: flupH - fluph.darktech.org (46:1/102)

On 10/25/15, Skuz said the following...

Will save it, and if the blank is still there will atemp to edit it.

That one looked good I think, but the msg has two tear/origin lines.

Ttyl :-),
Al

--- Mystic BBS v1.11 A3 (Linux)
* Origin: The Rusty MailBox - Penticton, BC Canada (46:1/161)

Zeus IITWILIGHT
▄▄▄▄▄▄▄ ▄▌ ▄▄▄▄▄▄▄
░▓▓█░ ▀▀▀█████▌ ▐▄█▀▀█ ▄▄█▀▀█ █▓▄ ▀█▄▄▓░▀▀▀▀░█▓▓░ ▄▄█
▓ ▓▓▓ ▐▓▓▓ ▀▀▄█▄▌ ▀ ▄▄▄▄ ▐▓▓▓▓ ▐███▌ ░░ ▄▒ ▌ ▐ ▀

ah looks right.

|15[xtcbox.org] - |05T|08.|03N|08.|07A |15+ |03XTC

--- Mystic BBS v1.11 A3 (Windows)
* Origin: fluph.darktech.org (46:1/102)

Will save it, and if the blank is still there will atemp to edit it.

That one looked good I think, but the msg has two tear/origin lines.

For now there is nothing we can do about ANSI messages having multiple origin lines unless the tosser can be told to stop adding tear/origins when it thinks they're missing. I don't know if that is a FastEcho option or not.

The problem only occures with 3rd party tossers and ONLY when an ANSI embedded message is edited and resaved I believe. Mystic's tosser of course does not have this problem.

I have an idea work around to the problem I just haven't tried to implement it yet.

--- Mystic BBS v1.11 A3 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

25 Oct 15 05:53, you wrote to Al:

For now there is nothing we can do about ANSI messages having multiple origin lines unless the tosser can be told to stop adding tear/origins when it thinks they're missing. I don't know if that is a FastEcho
option or not.

Well with fastecho in advanced options there are Keep tearline clean Y/N
and Retear Y/N also a place add Tearline (blank) or whatever, Fastecho 1.46a

Keep tearlines clean Y/N mine is NO, causing --- Mystic 1.11
With this option enabled, all echomail messages scanned
by FastEcho SCAN will have an 'empty' Tearline ('---').
This way all unwanted texts, advertisements etc. being
put there by your mail editor for example will be suppressed.

Retear, Tearline Y/N mine is NO

You may specify a tearline that will replace the
existing tearline when exporting echomail messages if
'Retear' is set to 'Yes'.
Remember that - if specified - a tearline MUST NOT
contain meaningless information or just 'rubbish'.
Further, the tearline MUST NOT contain the same
information the ^APID-kludge of your editor already
contains or the ^ATID-kludge FastEcho adds to each message.
The length of a tearline is limited to 35 characters
including preceeding '--- ' which is automatically added by FastEcho.
--- GoldED+/W32-MSVC 1.1.5-b20150715
* Origin: flupH - fluph.darktech.org (46:1/102)

Well with fastecho in advanced options there are Keep tearline clean Y/N and Retear Y/N also a place add Tearline (blank) or whatever, Fastecho 1.46a

Yep there is no option to tell it not to add a tearline if its missing, Fastecho just always does it. But I understand why it does it.

For now the only thing to do is:

1) Just deal with it because it only happens when an existing ANSI
embedded message is edited (so not often) and almost no networks are going
to allow the ANSI embedded messages because it looks like nothing to most
BBS softwares.

2) Use Mystic's tosser instead of FastEcho.

I have an idea on how to fix it though but its going to take a bunch of
coding to work around this.

--- Mystic BBS v1.11 A3 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

26 Oct 15 00:00, you wrote to me:

Yep there is no option to tell it not to add a tearline if its
missing, Fastecho just always does it. But I understand why it does

Yeah, that is correct.. This issue is so rare and not a big deal to me.

2) Use Mystic's tosser instead of FastEcho.

This is going to happen sometime, just not in any hurry it do it. I wouldn't take long to switch over to full native mystic.

I have an idea on how to fix it though but its going to take a bunch
of coding to work around this.

I wouldn't waste any of your time coding a work around. IMO, it is more of a Fastecho flaw, or option that never made it to the drawing board.

--- GoldED+/W32-MSVC 1.1.5-b20150715
* Origin: flupH - fluph.darktech.org (46:1/102)

On 10/25/15, Skuz said the following...

Well with fastecho in advanced options there are Keep tearline clean Y/N and Retear Y/N also a place add Tearline (blank) or whatever, Fastecho 1.46a

you can also do this...

SET FEOPT=STRIPTEAR

to completely strip tear lines off of exported messages ;)

see section 8.7 in the FE docs... i think it starts on page 141...

i actually use

SET FEOPT=STRIPTEAR,NOTID,NOAFIX

on my main system... NOTID prevents the TID control line from being added, IIRC... i don't find it documented, though, and it may be obsolete now... i don't even find it in the binary with the others...

--- Mystic BBS v1.10 A57 (Windows)
* Origin: (46:1/132)

On 10/26/15, g00r00 said the following...

Well with fastecho in advanced options there are Keep tearline clean and Retear Y/N also a place add Tearline (blank) or whatever, Fastech 1.46a

Yep there is no option to tell it not to add a tearline if its missing, Fastecho just always does it. But I understand why it does it.

ummm... see my previous post? ;)

--- Mystic BBS v1.10 A57 (Windows)
* Origin: (46:1/132)

27 Oct 15 09:51, you wrote to me:

to completely strip tear lines off of exported messages ;)
see section 8.7 in the FE docs... i think it starts on page 141...

Thanks man, I most of missed reading that part back in 1994..

SET FEOPT=STRIPTEAR,NOTID,NOAFIX
on my main system... NOTID prevents the TID control line from being

Also, good to know.. glad that i can count on you to fix my foobar ;)
---
* Origin: SET FEOPT=ASK_wkitty42 (46:1/102)

ummm... see my previous post? ;)

Unfortunately I don't think that will work either. It can't see the tear to begin with, with due to the ANSI embedding. This is why its adding its own
to begin with. If it can't see it and adds one, it won't be able to see it
to strip it either.

--- Mystic BBS v1.11 A4 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

On 10/27/15, Skuz said the following...

to completely strip tear lines off of exported messages ;)
see section 8.7 in the FE docs... i think it starts on page 141...

Thanks man, I most of missed reading that part back in 1994..

hahaha... it was the first change i implemented when we got the beta that offered the option... i've run without a tear line on most every system i
have when i've been able to since then ;)

SET FEOPT=STRIPTEAR,NOTID,NOAFIX
on my main system... NOTID prevents the TID control line from being

Also, good to know.. glad that i can count on you to fix my foobar ;)

t'ain't nuttin' like that :) just helping when and where i can O:)

---
* Origin: SET FEOPT=ASK_wkitty42 (46:1/102)

i like it! hahahahahahaha...

--- Mystic BBS v1.10 A57 (Windows)
* Origin: (46:1/132)

On 10/27/15, g00r00 said the following...

ummm... see my previous post? ;)

Unfortunately I don't think that will work either. It can't see the
tear to begin with, with due to the ANSI embedding. This is why its adding its own to begin with. If it can't see it and adds one, it won't be able to see it to strip it either.

somewhere in one of my posts about this i wrote to ensure that there's a CRLF before the tear line... either tack it on to the end of the message body before the tear line is added or make it part of the tear line writing code... that will flat out ensure that it is on its own line and starting in column 0 (or 1 depending on how one counts) ;)

it is the KIS principle at its working best O:)

--- Mystic BBS v1.10 A57 (Windows)
* Origin: (46:1/132)

somewhere in one of my posts about this i wrote to ensure that there's a CRLF before the tear line... either tack it on to the end of the message body before the tear line is added or make it part of the tear line

Oh I know but thats not how the ANSI embedded messages are. Keep in mind this is only a "problem" with ANSI embedded messages (which FidoNet doesnt support anyway, I dont think)... and its only a problem in a certain situation that almost never happens...

Mystic adds on the tear and origin in plain text for an ANSI message and all is fine during export. BUT if you save it and then EDIT an ANSI embedded message (which should almost never happen), Mystic can do nothing but load it as if its an ANSI file, basically. Its hard to explain but then its saved in the same way that you would draw a big ANSI in TheDraw at a line length of 79 characters.

That means the tear/origin are there but it might be like

ESC[2;12mAAAAAAAAAAAA[ESC1;34mBBBBBBBB--- Mystic BBS v1.10 (Winodws)ESC[1B * Origin: Some crap hereESC[1B

I hope that helps explain. I guess I'm trying to say its that its a very compact message and column 1 often wont be whats in the first column because its just tightly integrated ANSI codes.

My brain isnt too clear right now so sorry if this doesn't help at all. It probably has to do with the 4 fat tires and like half a bottle of wine I've had tonight! :p

--- Mystic BBS v1.11 A4 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

Unfortunately I don't think that will work either. It can't see the
tear to begin with, with due to the ANSI embedding. This is why its adding its own to begin with. If it can't see it and adds one, it won't be able to see it to strip it either.

that possible fix you were talking about, how would it work?

|15[xtcbox.org] - |05T|08.|03N|08.|07A |15+ |03XTC

--- Mystic BBS v1.11 A3 (Windows)
* Origin: fluph.darktech.org (46:1/102)