Re: LYNX-DEV Organization of -help output

[Al Gilman]

  From: Mike Brown <address@hidden>

  I'm toying with the 'lynx -help' output.  The list of command-line options
  is quite long and could use some better organization.  How do people feel
  about the list looking more like the example below?  Any suggestions?
  
The response to 'lynx -help' should fit in 80X24 characters, and
cover the basics.  It should end with instructions on how to get
more information, including reminding the user how to get to the
User's Guide.

In the H)elp tree, command line options should be a link directly
from the root help page and not first appear in the User's Guide
(it can stay physically in the User's Guide).  In the User's
guide it would be good to start with a global alphabetical
one-line-per-option summary to functional sections where there is
detail (more than now).  for example the discussion of -vikeys
is now:

        -vikeys
                enable vi-like key movement.

If it's not going to define what key functions included in the
vi-like group, it should hyperlink to where they are defined.

If there is to be a list this long, it should be 'lynx -options' or
something else.  And also end with a "for more information" instruction.

Note that there is the precedent of 'lynx -book' which argues that 
'lynx -help' should start lynx with lynx_help_main as the startfile.

$.02

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