Subj : Re: Message Pointers on n
To : G00R00
From : WKITTY42
Date : Thu Jan 31 2019 07:20 pm
On 09/10/14, g00r00 said the following...
g0> wk> jump up to the next post in a thread (mystic doesn't yet support this
g0>
g0> Mystic has supported this since 1997. What doesn't work for you?
referto and seealso in the headers always show 0 on imported messages... they
appear to work fine on locally written messages... may be this is because mutil
doesn't yet have a message linking function that is run after tossing the
mail??
g0> wk> when (if?) the JAM (and SQUish) capabilities are fully implemented,
g0> wk> things should be clearer and easier to follow...
g0>
g0> What exactly isn't fully implemented? Just because you want the last
g0> read pointers to work differently than they do doesn't mean its not
g0> "fully implemented" :)
nonononononoon... i'm not saying that i want them to work differently... there
are two read pointers... at least in JAM areas... lastread and highread...
highread is the highest message read in an area whereas lastread is the actual
message i'm on when leaving a message area... they may both be the same number
but not always... it is a basic feature of JAM areas that i've not seen in
operation in mystic...
