elinks(1) Manual Page

Restricts ELinks so it can run on an anonymous account. Local file browsing, downloads, and modification of options will be disabled. Execution of viewers is allowed, but entries in the association table can't be added or modified.

Automatically submit the first form in the given URLs.

Used internally when opening ELinks instances in new windows. The ID maps to information that will be used when creating the new instance. You don't want to use it.

Path of the directory ELinks will read and write its config and runtime state files to instead of ~/.elinks. If the path does not begin with a '/' it is assumed to be relative to your HOME directory.

Print a configuration file with options set to the built-in defaults to stdout.

Name of the configuration file that all configuration options will be read from and written to. It should be relative to config-dir.

Print help for configuration options and exit.

The default MIME type used for documents of unknown type.

When set, all keybindings from configuration files will be ignored. It forces use of default keybindings and will reset user-defined ones on save.

Print formatted plain-text versions of given URLs to stdout.

Codepage used when formatting dump output.

Width of the dump output.

Specify configuration file directives on the command-line which will be evaluated after all configuration files has been read. Example usage:

-eval 'set protocol.file.allow_special_files = 1'

Makes ELinks assume documents of unknown types are HTML. Useful when using ELinks as an external viewer from MUAs. This is equivalent to -default-mime-type text/html.

Print usage help and exit.

Restricts ELinks to work offline and only connect to servers with local addresses (ie. 127.0.0.1). No connections to remote servers will be permitted.

Print detailed usage help and exit.

Look up specified host and print all DNS resolved IP addresses.

Run ELinks as a separate instance instead of connecting to an existing instance. Note that normally no runtime state files (bookmarks, history, etc.) are written to the disk when this option is used. See also -touch-files.

Disables creation and use of files in the user specific home configuration directory (~/.elinks). It forces default configuration values to be used and disables saving of runtime state files.

Prevents printing of link number in dump output. Note that this really affects only -dump, nothing else.

Prevents printing of references (URIs) of document links in dump output. Note that this really affects only -dump, nothing else.

Control a remote ELinks instance by passing commands to it. The option takes an additional argument containing the method which should be invoked and any parameters that should be passed to it. For ease of use, the additional method argument can be omitted in which case any URL arguments will be opened in new tabs in the remote instance. Following is a list of the supported methods:

ID of session ring this ELinks session should connect to. ELinks works in so-called session rings, whereby all instances of ELinks are interconnected and share state (cache, bookmarks, cookies, and so on). By default, all ELinks instances connect to session ring 0. You can change that behaviour with this switch and form as many session rings as you want. Obviously, if the session-ring with this number doesn't exist yet, it's created and this 'ELinks' instance will become the master instance (that usually doesn't matter for you as a user much). Note that you usually don't want to use this unless you're a developer and you want to do some testing - if you want the ELinks instances each running standalone, rather use the -no-connect command-line option. Also note that normally no runtime state files are written to the disk when this option is used. See also -touch-files.

Print given URLs in source form to stdout.

When enabled, runtime state files (bookmarks, history, etc.) are written to disk, even when -no-connect or -session-ring is used. The option has no effect if not used in conjunction with any of these options.

The verbose level controls what messages are shown at start up and while running:

Print ELinks version information and exit.

The shell used for File → OS Shell on DOS/Windows and UNIX, respectively.

The program to use for external editor (when editing textareas).

The location of the directory containing configuration files. If not set the default is ~/.elinks/.

The command to run when selecting File → New window and if TWDISPLAY is defined (default twterm -e).

The command to run when selecting File → New window and if DISPLAY is defined (default xterm -e).

The host to proxy the various protocol traffic through.

A comma separated list of URLs which should not be proxied.

The path to the users home directory. Used when expanding ~/.

Homepage location (as in lynx(1)).

Site-wide configuration file.

Per-user config file, loaded after site-wide configuration.

Bookmarks file.

Cookies file.

Exmode history file.

Form history file.

History file containing most recently visited URLs.

GoTo URL dialog history file.

Browser scripting hooks.

Search history file.

Internal ELinks socket for communication between its instances.

Mappings of MIME types to external handlers.

Mappings of file extensions to MIME types.