Re: LYNX-DEV Advice requested on tracing an HTML problem

[Jason F. McBrayer]

Anthony M Addyman <address@hidden> writes:

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

Under OS/2 with my Lynx 2.7.1 port, redirecting the trace output works
just fine if your shell supports redirection of stderr.  Cmd.exe does
so just fine, just type "lynx -trace 2> tracelog" or some such.  I
don't know about Lynx for DOS-386.

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

I don't think it's a matter of ettiquette.  Just be sure to use your
own set of defines that don't conflict with any others in use and that
are appropriate to your compiler, and add an entry to the makefile to
use those defines.  E.g., don't mess with the os2 entry, make an
os2-watcom entry in the makefile.  That said, I _strongly_ recommend
that you use EMX/GCC with OS/2 and DJGPP with DOS.  Most of the
libraries that you will need are readily available for those
compilers, and your fixes will be easier to merge in with both the
standard distribution and the patches for OS/2 and DOS.

Jason F. McBrayer
address@hidden
OS/2 Lynx information at http://studentweb.tulane.edu/~jmcbray/lynx/.
(binaries and source patches)
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;