Thomas Dickey dixit: > When it goes to display a screen, it uses a line-number within the formatted > page. But the line number for the same text in the normal and > source views is not necessarily close to the same value, except when you're > right at the beginning of the page.
Okay, let me try to rephrase it: Suppose you open a large, 100 KiB or so, HTML page and scroll down several pages. Your screen now displays formatted lines 1000-1024 and your cursor is on line 1020 on a hyperlink. My suggestion would be that on '\' lynx now tries to find the line number of the source line which is responsible for the line 1000 of the formatted view, and then starts displaying from there. The only issue with that might be that between (formatted) 1000 and (formatted) 1020 - the hyperlink/cursor line - are only 20 lines, but in the HTML view might be several 100 (think of embedded JS). But it's better than a non-determined behaviour, and you could document that on toggling views the "top corner of the screen" (formatted line 1000, in my example) stays the same. > Or perhaps you were talking about making the whole feature optional. No, just changing it (so it works). //mirabile -- > [...] Echtzeit hat weniger mit "Speed"[...] zu tun, sondern damit, da� der > richtige Proze� voraussagbar rechtzeitig sein Zeitscheibchen bekommt. Wir haben uns[...] geeinigt, dass das verwendete Echtzeit-Betriebssystem[...] weil selbst einfachste Operationen *echt* *Zeit* brauchen. (aus d.a.s.r) _______________________________________________ Lynx-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lynx-dev
