Grant Edwards <[EMAIL PROTECTED]> wrote: > First, make it work. Then make it work right. Then worry > about how fast it is.
> "Premature optimization..." That could be - but then again, most of the comments I've seen for that particular issue are for rather old releases. >> It seems to use a quadratic algorithm for remembering where >> the links point, or something. I wrote a very crude but very >> fast renderer in C that I can post if someone wants it, which >> is what I use for this purpose. > If lynx really is too slow, try w3m or links. Both do a better > job of rendering anyway. They lay out tables more/less as expected (though navigation in tables for links seems to be an afterthought). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- http://mail.python.org/mailman/listinfo/python-list
