Hi all,

I'm having a text wrapping issue on certain messages which is becoming a
little annoying. I find that certain echomail messages aren't being displayed correctly in the msg reader and some text is off screen and not being formatted inside 80 chars, whereas other messages are fine.

I've also noticed that local messages are doing the same when allowing the
text to auto wrap at the end of each line. It displays perfectly in the
editor every time but when reading, the text overshoots the max screen width
on some lines.

I have msg_editor.ini set to a max width of 79 chars and I also tried defaulting back to the original Mystic ansimrd file (as we have a modified version for Topaz font) but it's the same output.

The only way I can overcome this when writing msgs, is perform a CR at the
end of every line to stop the auto wrap.

Does this sound familiar to anyone?

Cheers!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Retro32 BBS (21:1/215)

On 10 Apr 2024, fuzion said the following...

I've also noticed that local messages are doing the same when allowing
the text to auto wrap at the end of each line. It displays perfectly in the editor every time but when reading, the text overshoots the max
screen width on some lines.

when you say "max screen width" what exactly do you mean? do you mean something you've set somewhere in your theme, or do you mean the actual width mystic thinks the terminal is?

imagine: you log into a bbs with a 40 column theme, and your terminal is 60 columns wide. mystic selects the 40 column one cause 80 won't fit, but mystic also knows you have 60 columns and will wrap messages to that width.

as for the editor.. mystic won't insert line endings if it doesn't have to (only if you press enter explicitely) .. if it did, whatever bbses your message made it to would be wrapped to something arbitrary, potentially wasting screen space for users with wide terminals.

it's likely the width you're setting for the editor is only for aesthetic reasons

somebody with a wide theme bbs might be able to elaborate (or fix something i messed up)

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

I'm having a text wrapping issue on certain messages which is becoming a I'm having a text wrapping issue on certain messages which is becoming a little annoying. I find that certain echomail messages aren't being displayed correctly in the msg reader and some text is off screen and
not being formatted inside 80 chars, whereas other messages are fine.

I have the same issue when I try to write messages on
these networked pages. I have to manually insert a CR
before the lines get very long or else they overlap.

... If a pig loses its voice, is it disgruntled?

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: From the depths of Bunker 3 (21:1/130)

Hi there,

I have the same issue when I try to write messages on
these networked pages. I have to manually insert a CR
before the lines get very long or else they overlap.

It's as if there is a slight problem with the reader in
some way. Do you find that when you see a message that
overlaps in the msg reader and hit EDIT, that particular
message is formatted perfectly in the message editor?

I also noticed you are running the Win version of Mystic
like myself, it would be interesting to see if the Linux
guys are finding the same thing.

Cheers!

... It's all about the subculture, man!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Retro32 BBS (21:1/215)

Hi,

when you say "max screen width" what exactly do you mean? do you mean something you've set somewhere in your theme, or do you mean the actual width mystic thinks the terminal is?

I actually meant max column width, "max screen width" was a bad term to
use and probably a little confusing. :) I'm just running 80 columns in my clients and in the editor to suit.

imagine: you log into a bbs with a 40 column theme, and your terminal is 60 columns wide. mystic selects the 40 column one cause 80 won't fit,
but mystic also knows you have 60 columns and will wrap messages to that width.

The msg reader doesn't seem to be "down wrapping" messages that are wider than 80 cols, hence the missing text. If I see an echomail that I can't read properly, I just hit EDIT to load the msg editor and it displays perfectly. It's just strange that the reader isn't formatting the text as it should but the editor can.

it's likely the width you're setting for the editor is only for aesthetic reasons

I haven't done anything funky with the editor. It's just set to the standard
79 columns in the msg_editor config.

Do you have any problems similar to this running the Win version of Mystic?

Cheers!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Retro32 BBS (21:1/215)

On 11 Apr 2024, fuzion said the following...

The msg reader doesn't seem to be "down wrapping" messages that are
wider than 80 cols, hence the missing text. If I see an echomail that I can't read properly, I just hit EDIT to load the msg editor and it displays perfectly. It's just strange that the reader isn't formatting
the text as it should but the editor can.

it's definitely strange if there's part of the messages you can't read at all.. does it happen in both the modern reader and the old school one?

Do you have any problems similar to this running the Win version of Mystic?

not that i've seen. though there were some similar sounding qwerks from when i moved my bbs to linux for a few months (line endings stored internally perhaps?) and old messages from before the swap behaved weird

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

Hi,

Thanks for the comeback.

it's definitely strange if there's part of the messages you can't read
at all.. does it happen in both the modern reader and the old school fu> one?

I use DcTelnet on the Amiga/PI and SyncTerm/Netrunner on PC and it's the same on all clients. I think I can safely say it's the reader just not recognising auto returns.

I'm unsure if there is any config data anywhere I can look at for the
reader, now I've confirmed it's not an issue with our modded ansimrd file.

Cheers.

... [cLiCK].. carrier lost. Who picked up the phone??

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Retro32 BBS (21:1/215)