Text 33106, 62 rader
Skriven 2013-01-28 16:31:00 av Nancy Backus (63287.cooking)
  Kommentar till text 33037 av MARK LEWIS (1:3634/12.42)
Ärende: Re: messages  was: mint
===============================
-=> Quoting Mark Lewis to Nancy Backus on 01-26-13  19:04 <=-

 ML>> the complete message(s) showed up here... i suspect that something
 ML>> mistook the  three dashes stephen used in a few places in the 
 ML>> recipe as tear lines and  decided that was the end of the 
 ML>> message... tearlines in [...]
 NB>> Ah... that makes sense...  I mentioned it to Stephen since one
 NB>> doesn't always know that glitches are happening... and it could
 NB>> have been something at his end, rather than in the message... 
 NB>> either way, not all the info was being transmitted....  :)

 ML> it is possible that you got it all but your reader cut it... kinda
 ML> like SLMR  and others of that era have been known to do...

As it turns out... I don't think it was dashes any more... I went back
to the packet in question and to my other packets of that day from other
bbses... the cutoff was only in my Holodeck packet, not in the others...
and in no case was it at the mock tearlines... Curiouser and curiouser.. 
 
 ML> let's try a test... there are four tests below... each is delimited by
 ML> a set of  dashes... two are "proper" tearlines (dashes with trailing
 ML> spaces) and two are  not...
 ML> -!-
 ML> can you see this test #1?
 ML> -!- 
 ML> what about this test #2?
 ML> --
 ML> and here's test #3...
 ML> -- 
 ML> and finally test #4...
 ML> hopefully my editor and the software on this point system will not
 ML> strip certain text attributes... but we'll see when you reply :) 

All four came through, and even here in my text editor, I can "see" the
trailing space after #2 and #4...  As it was a test, I paid attention to
the whole message both online reading at each bbs, and in each message
packet from all the bbses I grab from... Saw it perfectly everywhere. 
(and I noticed the feedback from some others who were elsewhere...)

Dunno what did the glitch... it only happened on Steve's messages, all
three of them in that particular packet, but at different points of the
message, never at a three dash point... and hasn't happened since.  I've
been using my old faithful BlueWave 2.20 DOS reader right along, nothing
different there... and the lengths of the messages weren't even
abnormal.  I've had much longer messages without anything choking on
them, in the same setup...  

My usual pattern is to read/reply from Holodeck, and to scan through the
messages in my other backup packets, only paging down through the
message if there's some ulterior motive rather than simple backup, which
is how I missed that it was only Holodeck's that somehow got clipped...
but, to be complete, those three messages were the only ones in even
that packet that had been clipped, so I haven't a clue still what did
it.  But I'm glad we've had the discussion... I think... (G)

ttyl          neb

... A long time ago in a galaxy far far away, or was it here?

___ Blue Wave/QWK v2.20
--- SBBSecho 2.20-Win32
 * Origin: The Holodeck  telnet://holo.homeip.net (1:261/1381)