LYNX-DEV Advice requested on tracing an HTML problem

[Anthony M Addyman]

I need to use Lynx (DOS-386 and OS/2) - both v2.7.1 - to access some
information created by a Notes Domino server. I am getting a Bad HTML
message. Clearly, I should use tracing to try and pin-down the cause of the
problem. As a newcomer to Lynx I suspect the use of form-data with Forms,
but I need to identify the problem, before I can dream of finding a fix or
workaround. When I try adding -trace to the command line I get a rapidly
scrolling trace of the 20K or so of HTML. Can this be piped to a file, or
otherwise controlled? References on the list to the use of trace to
identify such problems suggests I am missing something here.

A second question - one of etiquette(?) A couple of others have generously
created Lynx for DOS-386 and OS/2 and made the binaries available. As I
normally use the WATCOM C/C++ compiler for 386DOS apps (and prefer it to
the other three compilers I have) am I likely to upset anyone if I should
find the problem, fix it, but have used this compiler for the purpose.
Obviously, there would be a need for yet more #ifdefs to cope with the
personality of yet another compiler (and curses)
TIA
Tony Addyman


;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;