This file documents the Lua scripting interface of the ELinks web browser.
Lua scripting capabilities permit users to customize the ELinks behaviour to unusual degree - they allow automatic rewriting of HTML code of the received documents, rewriting of the URLs entered by user etc. You can even write your own bookmarks system with Lua. See also contrib/lua/ for some examples of the possibilities of ELinks Lua support.
Please do not confuse Lua scripting with JavaScript, EcmaScript, VBScript and similar. Those are embedded in page, allowing per-document scripting related to its presentation and providing some degree of interactivity etc. On the contrary, the current Lua support permits scripts to be embedded to the browser directly, changing the behaviour of the browser, not the document.
The original Lua support (in the form of Links-Lua fork of original Links) was written by Peter Wang and Cliff Cunnington. There are some rough edges remaining, but is suitable for everyday use (I have been using it every day for a year).
The Lua scripting support comes with the stock ELinks distribution, no additional patches and tweaks should be needed.
The web site of the original Links-Lua is at http://links.sourceforge.net/links-lua/. Some older patches against regular Links are available at http://www.sourceforge.net/projects/links/, but they are not being maintained.
Lua can be found at http://www.lua.org/.
The Lua support has only been tested under Linux, although it should work under other platforms that ELinks and Lua support (perhaps with some changes to source code?).
Also, note that many of the scripts given here assume a Unix system. Your mileage will definitely vary on other platforms.
Before you can compile ELinks with Lua support, you must compile and install
Lua. The following instructions are for a Linux system. People on other
systems should try to enable popen
support, but this is not necessary
(you will lose a bit of functionality though).
tar.gz
or zip
somewhere.
cd
into the lua
directory.
config
in a text editor and uncomment the POPEN
line.
make; make so; make sobin; make install
.
On systems without shared object support, simply run make; make install
instead.
Since ELinks 0.11.0, only version 5.0 of Lua is supported. Future versions of ELinks will probably support Lua 5.1 too; see bug 742.
Follow the instructions for building ELinks (it is the standard
./configure; make; make install
procedure). During the configure
step make sure that Lua has been detected on your system.
Simply start ELinks as you normally would. To check you have Lua support compiled in, open up the "Help | About" dialog box. It should list "Scripting (Lua)" under "Features". If not, make sure you do not have other copies of ELinks running, or start ELinks again with the "-no-connect" option on the command-line.
Out of the box, ELinks with Lua will do nothing different from regular ELinks. You need to write some scripts.
The Lua support is based on the idea of hooks. A hook is a function that gets called at a particular point during the execution of ELinks. To make ELinks do what you want, you can add and edit such hooks.
The Lua support also adds an extra dialog box, which you can open while in
ELinks with the comma (,
) key. Here you can enter Lua expressions for
evaluation, or override it to do something different.
And finally, you can bind keystrokes to Lua functions. These keystrokes won't let you do any more than is possible with the Lua Console, but they're more convenient.
Note that this document assumes you have some knowledge of programming in Lua. For that, you should refer to the Lua reference manual (http://www.lua.org/docs.html). In fact, the language is relatively trivial, though. You could already do wonders with simply refactoring the example scripts.
On startup, ELinks reads in two Lua scripts. Firstly, a system-wide
configuration file called /etc/elinks/hooks.lua
, then a file in your home
directory called ~/.config/elinks/hooks.lua
. From these files, you can include
other Lua files with dofile
, if necessary.
To see what kind of things you should put in here, look at
contrib/lua/hooks.lua
.
The following hooks are available.
nil
). It should return a string, which is the URL
that ELinks should follow, or nil
to cancel the operation.
nil
to stop
ELinks following the URL
nil
if there were no
modifications.
nil
to use the default proxy of the protocol.
This hook is passed the string that the user entered into the "Lua
Console" dialog box. It should return two values: the type of action
to take (run
, eval
, goto-url
or nil
), and
a second argument, which is the shell command to run or the Lua
expression to evaluate. Examples:
return "run", "someprogram"
will attempt to run the program
someprogram
.
return "eval", "somefunction(1+2)"
will attempt to call the Lua
function somefunction
with an argument, 3.
return "goto_url", "http://www.bogus.com"
will ask ELinks to visit
the URL "http://www.bogus.com".
return nil
will do nothing.
As well as providing hooks, ELinks provides some functions in addition to the standard Lua functions.
The standard Lua function os.setlocale
affects ELinks' idea of
the system locale, which ELinks uses for the "System" charset, for the
"System" language, and for formatting dates. This may however have to
be changed in a future version of ELinks, in order to properly support
terminal-specific system locales.
nil
if none is
selected.
nil
if none.
width
, just as some lines may be wider than the screen when
viewing documents online.
command
and reads in all the data from stdout, until there
is no more. This is a hack, because for some reason the standard Lua
function file:read
seems to crash ELinks when used in pipe-reading
mode.
string
without waiting for it to exit. Beware
that you must not read or write to stdin and stdout. And unlike the
standard Lua function os.execute
, the return value is meaningless.
Returns a unique name for a temporary file, or nil
if no
such name is available. The returned string includes the
directory name. Unlike the standard Lua function
os.tmpname
, this one generates ELinks-related names
(currently with "elinks" at the beginning of the name).
The tmpname
function creates the file but does not
guarantee exclusive access to it: another process may delete the
file and recreate it. This exposes you to symlink attacks by other
users. To avoid the risk, use io.tmpfile
instead; unfortunately,
it does not tell you the name of the file.
keymap
must be the string "main"
. Keystroke is a
keystroke as you would write it in the ELinks config file
~/.config/elinks/elinks.conf
. The function function
should take no
arguments, and should return the same values as lua_console_hook
.
1
if successful, nil
if arguments are invalid, or nothing
at all if out of memory. The first three arguments
must be strings, and the user can then edit them in input
fields. There are also OK and Cancel buttons in the
dialog. If the user presses OK, ELinks calls function
with the three edited strings as arguments, and it should
return similar values as in lua_console_hook
.
1
if successful, nil
if arguments are
invalid, or nothing at all if out of memory. All arguments
except the last one must be strings, and ELinks places them
in input fields in the dialog. There can be at most 5 such
strings. There are also OK and Cancel buttons in the
dialog. If the user presses OK, ELinks calls function
with the edited strings as arguments, and it should return
similar values as in lua_console_hook
.
option
must be
the name of the option as a string. ELinks then tries to
convert the second argument value
to match the type of the
option. If successful, set_option
returns value
, else
nil
.
option
must be the name of the option as a string. If the option
does not exist, get_option
returns nil
.
There is one more little thing which Links-Lua adds, which will not be
described in detail here. It is the fake "user:" protocol, which can be used
when writing your own addons. It allows you to generate web pages containing
links to "user://blahblah", which can be intercepted by the follow_url_hook
(among other things) to perform unusual actions. For a concrete example, see
the bookmark addon.
This chapter contains some example scripts that you can use. All of them come
from contrib/lua/hooks.lua
. I really recommend you to see it directly
instead of copying code out of this document. Also, not everything in there is
covered here.
If you would like to contribute scripts, that would be great! Please send them to me at tjaden@users.sourceforge.net. Cliff and I plan to start a script repository, provided we get some contributions. As for script ideas, you'll just have to be a little creative :-)
Also take a look at the contrib/lua/
directory in the ELinks distribution.
Note that Peter and Cliff don't maintain the Lua support intensively anymore,
thus it would be probably nice to Cc me (pasky@ucw.cz) if you want
to contribute some patch, so that I would be able to add it to the ELinks
distribution.
There are some web sites that I visit often. Bookmarks are okay, but they are separate from the "Go to URL" dialog box, so I keep forgetting to use them. Also, when I visit a search engine home page, all I really want to do is enter a search term.
The following script allows me to type certain strings into the "Go to URL" dialog box, and it will convert them to the URL I actually want to visit. As a bonus, it allows me perform some searches on sites like Google without loading up the front page first.
The “URI rewriting” feature of ELinks handles many of the same tasks as the Lua hook shown here, and you can conveniently configure it via the option manager. It is not quite as versatile, though.
function match (prefix, url) return string.sub (url, 1, string.len (prefix)) == prefix end function strip (str) return string.gsub (str, "^%s*(.-)%s*$", "%1") end function plusify (str) return string.gsub (str, "%s", "+") end function goto_url_hook (url, current_url) -- Google search (e.g. ,gg unix browsers). if match (",gg", url) then url = plusify (strip (string.sub (url, 4))) return "http://www.google.com/search?q="..url.."&btnG=Google+Search" -- Freshmeat search. elseif match (",fm", url) then url = plusify (strip (string.sub (url, 4))) return "http://www.freshmeat.net/search/?q="..url -- Dictionary.com search (e.g. ,dict congenial). elseif match (",dict", url) then url = plusify (strip (string.sub (url, 6))) return "http://www.dictionary.com/cgi-bin/dict.pl?db=%2A&term="..url -- RPM search (e.g. ,rpm links). elseif match (",rpm", url) then url = plusify (strip (string.sub (url, 5))) return "http://www.rpmfind.net/linux/rpm2html/search.php?query=" ..url.."&submit=Search+..." -- Netcraft.com search (e.g. ,whatis www.google.com). elseif match (",whatis", url) then url = plusify (strip (string.sub (url, 8))) return "http://uptime.netcraft.com/up/graph/?host="..url -- LinuxToday home page. elseif match (",lt", url) then return "http://linuxtoday.com/" -- Weather forecast for Melbourne, Australia. elseif match (",forecast", url) then return "http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDV10450.txt" -- Unmatched else return url end end
By adding an extra snippet of code to the previous example, we can make ELinks
expand pathnames such as ~/foo/bar
and ~user/zappo
, like in the shell
and other Unix programs.
function goto_url_hook (url, current_url) . . -- Expand ~ to home directories. elseif match ("~", url) then if string.sub(url, 2, 2) == "/" then -- ~/foo return os.getenv ("HOME")..string.sub(url, 2) else -- ~foo/bar return "/home/"..string.sub(url, 2) end . .
Many web pages nowadays have columns to the left and right of the text, which are utterly useless. If you happen to be viewing the page in a 80x25 screen, the text you want to read ends up crammed into a tiny space in the centre. We use ELinks Lua support to manipulate the HTML before it reaches the parser.
This recipe is out of date for the web site.
Linux Today has two problems when viewed in ELinks: the useless columns on the left and the right and all the text appears in cyan. Here is a quick recipe to fix that:
-- Plain string.find (no metacharacters) function sstrfind (s, pattern) return string.find (s, pattern, 1, true) end function pre_format_html_hook (url, html) -- Strip the left and right columns from Linux Today pages -- and change the font colour to white. if sstrfind (url, "linuxtoday.com") then if sstrfind (url, "news_story") then html = string.gsub (html, '<TABLE CELLSPACING="0".-</TABLE>', '', 1) html = string.gsub (html, '<TR BGCOLOR="#FFF.-</TR></TABLE>', '', 1) else html = string.gsub (html, 'WIDTH="120">\n<TR.+</TABLE></TD>', '>', 1) end html = string.gsub (html, '<A HREF="http://www.internet.com.-</A>', '') html = string.gsub (html, "<IFRAME.-</IFRAME>", "") -- emphasis in text is lost return string.gsub (html, 'text="#002244"', 'text="#001133"', 1) end return nil end
This recipe is out of date for the web site.
Here is a simpler example, for http://www.linuxgames.com/.
function pre_format_html_hook (url, html) . . elseif string.find (url, "linuxgames.com", 1, true) then return string.gsub (html, "<CENTER>.-</center>", "", 1) . .
ELinks already supports gzipped files natively.
Sometimes documents come gzipped in order to save space, but then you need to uncompress them to read them with ELinks. Here is a recipe to handle gzipped files on a Unix system.
This recipe opens a temporary file insecurely.
function pre_format_html_hook (url, html) . . -- Handle gzip'd files within reasonable size. if string.find (url, "%.gz$") and string.len (html) < 65536 then local name = tmpname () local file = io.open (name, "wb") file:write (html) file:close () html = pipe_read ("(gzip -dc "..name.." || cat "..name..") 2>/dev/null") os.remove (name) return html end . .
Printing a web page with ELinks usually involves quite a few steps: Save the current document onto disk. Run it through ELinks on the command-line (so it fits into 80 columns) to generate a plain text version. Remove the 80th column from the text version, as it will make printers wrap down to the next line. Finally, run the processed file through `lpr', then delete it.
The following functions allow you to print web pages directly from ELinks,
using lpr' or `enscript'. Type `lpr()
or enscript()
in the Lua Console to
run them. (In the hooks.lua
, I have also made it so you can just type lpr
or enscript
.)
The io.popen
function is not available on all platforms.
function pipe_formatted_to (program) local lp, errmsg = io.popen (program, "w") if lp == nil then error (errmsg) else lp:write (current_document_formatted (79)) lp:close () end end -- Send the current document to `lpr'. function lpr () pipe_formatted_to ("lpr") end -- Send the current document to `enscript'. function enscript () pipe_formatted_to ("enscript -fCourier8") end
If you come across a brain-dead web page that is totally unreadable with ELinks, you'd probably want to open it with a graphical browser. The following function opens the current document in Netscape.
You can also use the built-in “URI passing” feature for this.
-- When starting Netscape: Set to `nil' if you do not want -- to open a new window for each document. netscape_new_window = 1 -- Open current document in Netscape. function netscape () local new = netscape_new_window and ",new_window" or "" execute ("( netscape -remote 'openURL("..current_url ()..new..")'" .." || netscape '"..current_url ().."' ) 2>/dev/null &") end
Many people would like to have a bookmark system with categories (note that ELinks already supports that, marketing name Hierarchical bookmarks), and also to be able to view them and search for them in an HTML page. I have written an alternative bookmark system (for ELinks), which some people may like better than the standard bookmark system.