elinks.conf.5

elinks下lynx是最重要的二个文本浏览器, 在linux下非常实用, elinks也是gentoo安装过程中默认使用的浏览器, 这是elinks源代码

.TP
\(bu
2: is name in addition
.TP
\(bu
3: is hreflang in addition
.TP
\(bu
4: is type in addition
.TP
\(bu
5: is everything
.LP
.RE
.IP

.TP
document\&.html\&.underline_links [0|1] (default: 0)
Underline links\&.

.TP
document\&.html\&.wrap_nbsp [0|1] (default: 0)
If set do not honour non breaking space (the nbsp entity) but allow to wrap the text\&. This can help keeping the width of documents down so no horizontal scrolling is needed\&.

.TP
document\&.plain
Options concerning the display of plain text pages\&.

.TP
document\&.plain\&.display_links [0|1] (default: 0)
Display URIs in the document as links\&.

.TP
document\&.plain\&.compress_empty_lines [0|1] (default: 0)
Compress successive empty lines to only one in displayed text\&.

.TP
document\&.uri_passing
Rules for passing URIs to external commands\&.

.TP
document\&.uri_passing\&._template_ <str> (default: "")
A rule for passing URI to an external command\&. The format is: %c in the string means the current URL %% in the string means '%' Do _not_ put single\- or double\-quotes around %c\&.

.TP
ecmascript
ECMAScript options\&.

.TP
ecmascript\&.enable [0|1] (default: 1)
Whether to run those scripts inside of documents\&.

.TP
ecmascript\&.error_reporting [0|1] (default: 0)
Open a message box when a script reports an error\&.

.TP
ecmascript\&.ignore_noscript [0|1] (default: 0)
Whether to ignore content enclosed by the <noscript> tag when ECMAScript is enabled\&.

.TP
ecmascript\&.max_exec_time <num> (default: 5)
Maximum execution time in seconds for a script\&.

.TP
ecmascript\&.block_window_opening [0|1] (default: 0)
Whether to disallow scripts to open new windows or tabs\&.

.TP
infofiles
Options for information files in ~/\&.elinks\&.

.TP
infofiles\&.save_interval <num> (default: 300)
Interval at which to trigger information files in ~/\&.elinks to be saved to disk if they has changed (seconds; 0 to disable)

.TP
infofiles\&.secure_save [0|1] (default: 1)
First write data to unique temporary file, then rename this file upon successfully finishing this\&. Note that this relates only to config files, not downloaded files\&. You may want to disable it if you are using some exotic permissions for concerned files\&. Secure file saving is automagically disabled if file is symlink\&. Warning: some systems (ie\&. OS/2, Win32) require that destination file doesn't exist when rename(3) is called, breaking atomicity, and reducing reliability of this feature\&.

.TP
infofiles\&.secure_save_fsync [0|1] (default: 1)
When using secure file saving, call fsync(3), if the OS supports it, to force the OS immediately to write the data to permanent storage\&. This is optional for those who wish to avoid excessive disk I/O\&.

.TP
mime
MIME\-related options (handlers of various MIME types)\&.

.TP
mime\&.extension
Extension <\-> MIME type association\&.

.TP
mime\&.extension\&._template_ <str> (default: "")
MIME\-type matching this file extension ('*' is used here in place of '\&.')\&.

.TP
mime\&.handler
A file type handler is a set of information about how to use an external program to view a file\&. It is possible to refer to it for several MIME types -- e\&.g\&., you can define an 'image' handler to which mime\&.type\&.image\&.png, mime\&.type\&.image\&.jpeg, and so on will refer; or one might define a handler for a more specific type of file -- e\&.g\&., PDF files\&. Note you must define both a MIME handler and a MIME type association for it to work\&.

.TP
mime\&.handler\&._template_
Description of this handler\&.

.TP
mime\&.handler\&._template_\&._template_
System\-specific handler description (ie\&. unix, unix\-xwin, ...)\&.

.TP
mime\&.handler\&._template_\&._template_\&.ask [0|1] (default: 1)
Ask before opening\&.

.TP
mime\&.handler\&._template_\&._template_\&.block [0|1] (default: 1)
Block the terminal when the handler is running\&.

.TP
mime\&.handler\&._template_\&._template_\&.program <str> (default: "")
External viewer for this file type\&. '%' in this string will be substituted by a file name\&.

.TP
mime\&.mailcap
Options for mailcap support\&.

.TP
mime\&.mailcap\&.enable [0|1] (default: 1)
Enable mailcap support\&.

.TP
mime\&.mailcap\&.path <str> (default: "~/\&.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap:/usr/share/mailcap:/usr/share/misc/mailcap")
Mailcap search path\&. Colon\-separated list of files\&. Leave as "" to use MAILCAP environment variable instead\&.

.TP
mime\&.mailcap\&.ask [0|1] (default: 1)
Ask before using the handlers defined by mailcap\&.

.TP
mime\&.mailcap\&.description <num> (default: 0)
Type of description to show in "what to do with this file" query dialog:

.RS
.TP 3
\(bu
0: is show "mailcap"
.TP
\(bu
1: is show program to be run
.TP
\(bu
2: is show mailcap description field if any; "mailcap" otherwise
.LP
.RE
.IP

.TP
mime\&.mailcap\&.prioritize [0|1] (default: 1)
Prioritize entries by the order of the files in the mailcap path\&. This means that wildcard entries (like: image/*) will also be checked before deciding the handler\&.

.TP
mime\&.mimetypes
Options for the support of mime\&.types files\&. These files can be used to find the content type of an URL by looking at the extension of the file name\&.

.TP
mime\&.mimetypes\&.enable [0|1] (default: 1)
Enable mime\&.types support\&.

.TP
mime\&.mimetypes\&.path <str> (default: "~/\&.mime\&.types:/etc/mime\&.types:/usr/etc/mime\&.types:/usr/local/etc/mime\&.types:/usr/share/mime\&.types:/usr/share/misc/mime\&.types")
The search path for mime\&.types files\&. Colon\-separated list of files\&.

.TP
mime\&.type
Handler <\-> MIME type association\&. The first sub\-tree is the MIME class while the second sub\-tree is the MIME type (ie\&. image/gif handler will reside at mime\&.type\&.image\&.gif)\&. Each MIME type option should contain (case\-sensitive) name of the MIME handler (its properties are stored at mime\&.handler\&.<name>)\&.

.TP
mime\&.type\&._template_
Handler matching this MIME\-type class ('*' is used here in place of '\&.')\&.

.TP
mime\&.type\&._template_\&._template_ <str> (default: "")
Handler matching this MIME\-type name ('*' is used here in place of '\&.')\&.

.TP
mime\&.default_type <str> (default: "application/octet\-stream")
Document MIME\-type to assume by default (when we are unable to guess it properly from known information about the document)\&.

.TP
protocol
Protocol specific options\&.

.TP
protocol\&.bittorrent
BitTorrent specific options\&.

.TP
protocol\&.bittorrent\&.ports
Port range allowed to be used for listening on\&.

.TP
protocol\&.bittorrent\&.ports\&.min <num> (default: 6881)
The minimum port to try and listen on\&.

.TP
protocol\&.bittorrent\&.ports\&.max <num> (default: 6999)
The maximum port to try and listen on\&.

.TP
protocol\&.bittorrent\&.tracker
Tracker options\&.

.TP
protocol\&.bittorrent\&.tracker\&.compact [0|1] (default: 0)
Whether to request that the tracker returns peer info in compact format\&. Note, the compact format only supports IPv4 addresses\&.

.TP
protocol\&.bittorrent\&.tracker\&.interval <num> (default: 0)
The number of seconds to wait between periodically contacting the tracker for announcing progress and requesting more peers\&. Set to zero to use the interval requested by the tracker\&.

.TP
protocol\&.bittorrent\&.tracker\&.ip_address <str> (default: "")
What IP address to report to the tracker\&. If set to "" no IP address will be sent and the tracker will automatically determine an appropriate IP address\&.

.TP
protocol\&.bittorrent\&.tracker\&.key <str> (default: "")
An additional identification that is not shared with any users\&. It is intended to allow a client to prove their identity should their IP address change\&. It is an optional parameter, but some trackers require this parameter\&. If set to "" no user key will be sent to the tracker\&.

.TP
protocol\&.bittorrent\&.tracker\&.numwant <num> (default: 50)
The maximum number of peers to request from the tracker\&. Set to 0 to use the server default\&.

.TP
protocol\&.bittorrent\&.tracker\&.min_skip_size <num> (default: 20)
The minimum number of peers to have in the current peer info pool before skipping requesting of more peers\&. I\&.e\&. setting numwant to zero\&. Set to 0 to not have any limit\&.

.TP
protocol\&.bittorrent\&.peerwire
Lowlevel peer\-wire options\&.

.TP
protocol\&.bittorrent\&.peerwire\&.connections <num> (default: 55)
The maximum number of allowed connections to both active and non\-active peers\&. By increasing the number of allowed connections, the chance of finding good peers to download from is increased\&. However, too many connections can lead to TCP congestion\&. If the maximum is reached all new incoming connections will be closed\&.

.TP
protocol\&.bittorrent\&.peerwire\&.max_message_length <num> (default: 8388608)
The maximum length of messages to accept over the wire\&. Larger values will cause the connection to be dropped\&.

.TP
protocol\&.bittorrent\&.peerwire\&.max_request_length <num> (default: 8388608)
The maximum length to allow for incoming requests\&. Larger requests will cause the connection to be dropped\&.

.TP
protocol\&.bittorrent\&.peerwire\&.request_length <num> (default: 16384)
How many bytes to query for per request\&. This is complementary to the max_request_length option\&. If the configured length is bigger than the piece length it will be truncated\&.

.TP
protocol\&.bittorrent\&.peerwire\&.timeout <num> (default: 300)
The number of seconds to wait before closing a socket on which nothing has been received or sent\&.

.TP
protocol\&.bittorrent\&.peerwire\&.pool_size <num> (default: 55)
Maximum number of items in the peer pool\&. The peer pool contains information used for establishing connections to new peers\&. Set to 0 to have unlimited size\&.

.TP
protocol\&.bittorrent\&.piece_cache_size <num> (default: 1048576)
The maximum amount of memory used to hold recently downloaded pieces\&. Set to 0 to have unlimited size\&.

.TP
protocol\&.bittorrent\&.max_uploads <num> (default: 7)
The maximum number of uploads to allow at once\&.

.TP
protocol\&.bittorrent\&.min_uploads <num> (default: 2)
The minimum number of uploads which should at least be used for new connections\&.

.TP
protocol\&.bittorrent\&.request_queue_size <num> (default: 5)
How many piece requests to continuously keep in queue\&. Pipelining of requests is essential to saturate connections and get a good connection performance and thus a faster download\&. However, a very big queue size can lead to wasting bandwidth near the end of the connection since remaining piece blocks will be requested from multiple peers\&.

.TP
protocol\&.bittorrent\&.choke_interval <num> (default: 10)
The number of seconds between updating the connection state and most importantly choke and unchoke peer connections\&. The choke period should be big enough for newly unchoked connections to get started but small enough to not allow freeriders too much room for stealing bandwidth\&.

.TP
protocol\&.bittorrent\&.rarest_first_cutoff <num> (default: 4)
The number of pieces to obtain before switching piece selection strategy from random to rarest first\&.

.TP
protocol\&.bittorrent\&.allow_blacklist [0|1] (default: 1)
Allow blacklisting of buggy peers\&.

.TP
protocol\&.file
Options specific to local browsing\&.

.TP
protocol\&.file\&.cgi
Local CGI specific options\&.

.TP
protocol\&.file\&.cgi\&.path <str> (default: "")
Colon separated list of directories, where CGI scripts are stored\&.

.TP
protocol\&.file\&.cgi\&.policy [0|1] (default: 0)
Whether to execute local CGI scripts\&.

.TP
protocol\&.file\&.allow_special_files [0|1] (default: 0)
Whether to allow reading from non\-regular files\&. Note this can be dangerous; reading /dev/urandom or /dev/zero can ruin your day!

.TP
protocol\&.file\&.show_hidden_files [0|1] (default: 1)
When set to false, files with name starting with a dot will be hidden in local directories listing\&.

.TP
protocol\&.file\&.try_encoding_extensions [0|1] (default: 1)
When set, if we can't open a file named 'filename', we'll try to open 'filename' with some encoding extension appended (ie\&. 'filename\&.gz'); it depends on the supported encodings\&.

.TP
protocol\&.fsp
FSP specific options\&.

.TP
protocol\&.fsp\&.sort [0|1] (default: 1)
Whether to sort entries in directory listings\&.

.TP
protocol\&.ftp
FTP specific options\&.

.TP
protocol\&.ftp\&.proxy
FTP proxy configuration\&.

.TP
protocol\&.ftp\&.proxy\&.host <str> (default: "")
Host and port\-number (host:port) of the FTP proxy, or blank\&. If it's blank, FTP_PROXY environment variable is checked as well\&.

.TP
protocol\&.ftp\&.anon_passwd <str> (default: "some@host\&.domain")
FTP anonymous password to be sent\&.

.TP
protocol\&.ftp\&.use_pasv [0|1] (default: 1)
Use PASV instead of PORT (passive vs active mode, IPv4 only)\&.

.TP
protocol\&.ftp\&.use_epsv [0|1] (default: 0)
Use EPSV instead of EPRT (passive vs active mode, IPv6 only)\&.

.TP
protocol\&.http
HTTP\-specific options\&.

.TP
protocol\&.http\&.bugs
Server\-side HTTP bugs workarounds\&.

.TP
protocol\&.http\&.bugs\&.accept_charset [0|1] (default: 1)
The Accept\-Charset header is quite long and sending it can trigger bugs in some rarely found servers\&.

.TP
protocol\&.http\&.bugs\&.allow_blacklist [0|1] (default: 1)
Allow blacklisting of buggy servers\&.

.TP
protocol\&.http\&.bugs\&.broken_302_redirect [0|1] (default: 1)
Broken 302 redirect (violates RFC but compatible with Netscape)\&. This is a problem for a lot of web discussion boards and the like\&. If they will do strange things to you, try to play with this\&.

.TP
protocol\&.http\&.bugs\&.post_no_keepalive [0|1] (default: 0)
Disable keepalive connection after POST request\&.

.TP
protocol\&.http\&.bugs\&.http10 [0|1] (default: 0)
Use HTTP/1\&.0 protocol instead of HTTP/1\&.1\&.

.TP
protocol\&.http\&.proxy
HTTP proxy configuration\&.

.TP
protocol\&.http\&.proxy\&.host <str> (default: "")
Host and port\-number (host:port) of the HTTP proxy, or blank\&. If it's blank, HTTP_PROXY environment variable is checked as well\&.

.TP
protocol\&.http\&.proxy\&.user <str> (default: "")
Proxy authentication username\&.

.TP
protocol\&.http\&.proxy\&.passwd <str> (default: "")
Proxy authentication password\&.

.TP
protocol\&.http\&.referer
HTTP referer sending options\&. HTTP referer is a special header sent in the HTTP requests, which is supposed to contain the previous page visited by the browser\&. This way, the server can know what link did you follow when accessing that page\&. However, this behaviour can unfortunately considerably affect privacy and can lead even to a security problem on some badly designed web pages\&.

.TP
protocol\&.http\&.referer\&.policy <num> (default: 3)
Mode of sending HTTP referer:

.RS
.TP 3
\(bu
0: is send no referer
.TP
\(bu
1: is send current URL as referer
.TP
\(bu
2: is send fixed fake referer
.TP
\(bu
3: is send previous URL as referer (correct, but insecure)
.LP
.RE
.IP

.TP
protocol\&.http\&.referer\&.fake <str> (default: "")
Fake referer to be sent when policy is 2\&.

.TP
protocol\&.http\&.accept_language <str> (default: "")
Send Accept\-Language header\&.

.TP
protocol\&.http\&.accept_ui_language [0|1] (default: 1)
Request localised versions of documents from web\-servers (using the Accept\-Language header) using the language you have configured for \fIELinks\fR' user\-interface (this also affects navigator\&.language ECMAScript value available to scripts)\&. Note that some see this as a potential security risk because it tells web\-masters and the FBI sniffers about your language preference\&.

.TP