I wonder if newer versions of Mystic cut all long lines (paragraphs)
after 255 characters. So I'm writing some more words until I reach 256 chars to test, if this is really the case. Bla bla bla bla .... If I'm right, this line should be cut off right now. If I'm wrong, you still
can read this.
On 04-01-20 10:15, Oli wrote to All <=-
I wonder if newer versions of Mystic cut all long lines (paragraphs)
after 255 characters. So I'm writing some more words until I reach 256 chars to test, if this is really the case. Bla bla bla bla .... If I'm right, this line should be cut off right now. If I'm wrong, you still
can read this.
* Origin: kakistocracy (2:280/464.47)
I wonder if newer versions of Mystic cut all long lines
(paragraphs) after 255 characters. So I'm writing some more words
until I reach 256 chars to test, if this is really the case. Bla
bla bla bla .... If I'm right, this line should be cut off right
now. If I'm wrong, you still can read this.
I don't have the /latest/ prealpha but have a relatively recent one.
I wonder if newer versions of Mystic cut all long lines (paragraphs) after255
characters. So I'm writing some more words until I reach 256 chars to test,if
this is really the case. Bla bla bla bla .... If I'm right, this line shouldbe
cut off right now. If I'm wrong, you still can read this.
I wonder if newer versions of Mystic cut all long lines (paragraphs) after 255 characters. So I'm writing some more words until I reach 256 chars to t, if this is really the case. Bla bla bla bla .... If I'm right,
this line should be
cut off right now. If I'm wrong, you still can read this.
I wonder if newer versions of Mystic cut all long lines (paragraphs) after255
characters. So I'm writing some more words until I reach 256 chars to test,if
this is really the case. Bla bla bla bla .... If I'm right, this line shouldbe
cut off right now. If I'm wrong, you still can read this.
Yeah. Happens outside of the BBS-realm:
https://i.imgur.com/CfayWxW.png
I have 80 x 25-and-over terminals.
This is from Alpine running on FBSD goodness ...
But as you see, bad behaviours is easily rehabilated just by replying :D
I wonder if newer versions of Mystic cut all long lines (paragraphs) after255 characters. So I'm
writing some more words until I reach 256 chars to test, if this is reallythe case. Bla bla bla bla
.... If I'm right, this line should be cut off right now. If I'm wrong, youstill can read this.
i've not wrapped the above but yes, the long line is broken in two between "be" and "cut" as you can
see above... my terminal window is 226 columns wide...
My suspicion is that it started with 2020/03/26 and it might even be
fixed in th e latest pre-alpha 2020/03/29. There is one Hub in fsxnet
that is running this v ersion, the others running 2020/03/12 and are
still wrapping the long lines at 7 9 characters.
They shouldn't be getting cut off at 256 characters, the line length is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that would be a bug.
They shouldn't be getting cut off at 256 characters, the line length
is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that
would be a bug.
On 03 Apr 2020 at 02:13a, g00r00 pondered and said...
They shouldn't be getting cut off at 256 characters, the line
length is unlimited (or at least that is the intention) with the
latest pre-alpha. If you find otherwise please let me know
because that would be a bug.
What I'll work to do is update all three HUBs running Mystic to the
latest pre-alpha so everything is on the same playing field. Then we
can see what's happening and let you know. Cheers.
Hi Paul,
On 2020-04-10 14:13:52, I wrote to you:
@MSGID: 3:770/100 651d79ff
@PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188
292/854
Or is this a hickup on that system that shows up twice in the
path?
It was. I noticed there already was a message in this area with the
above MSGID... Sorry for the noice. ;)
AREA:MYSTIC
@FMAIL BAD: Message too old (2020-04-10 14:10:26)
@FMAIL SRC: 2:292/854
@FMAIL DEST: 2:280/464
@TID: Mystic BBS 1.12 A46
@MSGID: 3:770/100 651d79ff
@REPLY: 1:129/215 5faf9ad6
@TZUTC: 1300
@DATE: 00 00 03:00:00
On 03 Apr 2020 at 02:13a, g00r00 pondered and said...
--- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100) SEEN-BY: 203/0 221/1 229/426 261/38 280/464 292/140 854 8125 335/364 SEEN-BY: 801/188 189 190 194 197
@PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188 292/854
@MSGID: 3:770/100 651d79ff
@PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188 292/854
Or is this a hickup on that system that shows up twice in the path?
They shouldn't be getting cut off at 256 characters, the line length
is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that
would be a bug.
Interesting. At least two nodes in fsxnet received bad packages with scrambled messages. The origin line of 292/854 were in the To, From or Subject field. There were also some empty messages in this area with 2:292/854 in the origin line, but otherwise completely empty. But how do we
know that 292/384 is causing the problems? It could be 261/38 too (less likely though).
Using something like this with fidoweb-style echo routing has to
create some problems at some point. Like loops and dupes.
This is indeed the case. I did some testing yesterday with..
Mystic BBS v1.12 A46 Linux/64 Compiled 2020/04/09 22:56:56.
Please let us know if you would like further testing/input.
Ttyl :-),
Al
This is indeed the case. I did some testing yesterday with..
Mystic BBS v1.12 A46 Linux/64 Compiled 2020/04/09 22:56:56.
Please let us know if you would like further testing/input.
what happened to the subject
and your name?
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 89:46:21 |
Calls: | 2,069 |
Calls today: | 2 |
Files: | 11,134 |
Messages: | 946,775 |