command line options

[This file lists all available command line options for netrik invocation. See index.txt or index.html for an overview of available netrik documentation.]

Note: netrik is still in early developement state; options are subject to changes.

Force usage of netrik's default text colors (white on black for normal text), even if the terminal has other defaults. Without this option, netrik tries to adopt to the terminal's default. (Thus keeping the light background of most xterms.)
When using the pager, this causes a page that contains extremely long words to be rendered wider than the screen, instead of breaking the word. Note however that side scrolling isn't implemented yet -- you won't be able to see the end of the line when using this option... In dump mode, this option causes usage of the default width of 80 columns instead of what the terminal definiton says. (Words are always broken in dump mode.)
Stop on any HTML syntax errors encountered. A short error description is printed. (This description may not be terribly useful at times...) This mode is primarily intended for HTML debugging. (Note however that netrik may oversee some errors; but most are reported.)
--normal-html (default)
Do not stop on HTML syntax errors. Error descriptions are printed for every error, but netrik tries to parse the page anyhow. Workarounds are used for some typical syntax errors (e.g. unescaped '<' or '&' characters); other errors are ignored. After the whole page is loaded, if some error(s) were found a warning is printed (according to the severity of the worst encountered bug), and the pager starts after a keypress.
This mode is identical to --normal-html, except that no warning is printed and no key is awaited if only simple errors with known workaround were encountered, which probably won't disturb layouting. Usage is discouraged. (See syntax_error.* for details.)
In this mode no warning is printed for any syntax errors, even if they might cause heavily broken layouting. Don't use!
Before displaying (or dumping) the page, some intermediate layouting stages are shown. (This output is described in the README.) Try it -- it's quite intersting to watch netrik work :-) It can be also useful to find HTML errors in a page, as it dumps the page while loading/parsing it. (This option is not available if compiled with --disable-debug to ./configure)
Issue a warning when encountering an unknown HTML element or attribute. This is probably only useful for debugging purposes, as there are quite a lot of (legal) HTML facilities netrik doesn't know.
Just dump the file given as argument to the screen and quit, instead of starting the pager. (The page is layouted correctly.)
Ignore the "http_proxy" and "HTTP_PROXY" environment variables with --builtin-http. (No effect on wget!)
Use wget to retrieve pages from a HTTP server, instead of the builtin HTTP handling code. Note that HTTP redirects in most cases cause relative links in the page to be broken when using wget. The builtin HTTP code seems to work good now; using wget shouldn't be necessary. (FTP pages however are always loaded via wget.)
When jumping to an anchor (following a link with a fragment identifiert), the page will be scrolled (if possible) so that the anchor will stand just below the screen top. (In the second line, which is the first line in which links can be activated.) By default, the anchor is at about 1/5 of the screen height below the top.