On Tuesday 04 March 2003 04:11 am, Charlie Chernohorsky wrote:
then, i've found a mistake at prompts2.c / getviewparams(): instead of... (i guess it was caused by inserting that truebytes explanation) nothing serious, it just miss-estimates..
I can increase the number of lines that diff catches on either side of changes. This will increase the diff file size, but the problem should go away.
really? well, i've thought that if the end-of-comment mark is placed wrong, so it is not caused by diff.. i can think about some cases where increasing line-catch could help, but i don't think that it's this one..
I'm sorry. You are correct, I mangled the code when I added the comments.
i didn't think about passing thru this with s*dots equal to vesa_*res but, anyway, it should not ever get there then (as Tim said)..!
so, now i can see that small move is reasonable, but something must be wrong if we get there with so small s*dots..
No, there is nothing wrong because normally we don't care about the result that VESAscroll returns in the ax register. Jonathan