If the lightbar file listing (prompts #434 and/or #435, I think) uses a
$T display code to ensure that too long description lines are cut off
and don't overflow to the next line, this sometimes affects the
rendering of ANSI file descriptions, where pipes and partial pipe codes might become visible as a result of the cutoff.

I probably should have used |$R instead. In the update I am about to upload I have tried to enable $T to take account of pipe codes in that situation.

Let me know how it goes after you test it. I didn't set up a good test for it as I am a little bit pressed for time tonight and I want to get through all the messages/tasks tonight. It might work but could be totally broken too so keep your current mystic binary just in case :)

... I'd love to help you out. Which way did you come in?

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

On 03 Jan 2023, g00r00 said the following...

I probably should have used |$R instead. In the update I am about to

I'm guilty for the $T there as the original doesn't perform any truncation. :)

I probably should have used |$R instead. In the update I am about to upload I have tried to enable $T to take account of pipe codes in that situation.

Thanks a lot! Seems to be working fine!

Best regards
Bj”rn

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

I probably should have used |$R instead. In the update I am about to

I'm guilty for the $T there as the original doesn't perform any truncation. :)

I am glad you did...

$R/L/C all work with pipe codes, so it was my mistake that $T wasn't doing it!

Thanks a lot! Seems to be working fine!

Thanks for letting me know. Saves me some time having to test it now! :)

... The only place I want data loss is on my credit card!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)