1
0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00
Go to file
M. Levinson 26473f72f5 Python: Give goto_url_hook only one argument, like follow_url_hook.
On Dec 31, 2006, at 11:30am, Kalle Olavi Niemitalo writes:
>src/scripting/python/hooks.c (script_hook_url) calls hooks as
>goto_url_hook(new-url, current-url) and follow_url_hook(new-url).
>It has a comment saying that the current-url parameter exists
>only for compatibility and that the script can instead use
>elinks.current_url().  However, the current-url parameter was
>added in commit 87e27b9b3e and is
>not in ELinks 0.11.2, so any compatibility problems would only
>hit people who have been using 0.12.GIT snapshots.  Can we remove
>the second parameter now before releasing ELinks 0.12pre1?

The decision isn't up to me, but I think this is a good idea. Here's a
patch that would update the documentation and hooks.py, as well as hooks.c.

FYI, if this patch is applied then anyone who's still trying to use a
goto_url_hook that expects a second argument will get a "Browser scripting
error" dialog box that says:

	An error occurred while running a Python script:

	TypeError: goto_url_hook() takes exactly 2 arguments (1 given)
2007-01-01 17:45:36 +02:00
config Improve CPPFLAGS usage 2006-11-22 20:16:18 +01:00
contrib Python: Give goto_url_hook only one argument, like follow_url_hook. 2007-01-01 17:45:36 +02:00
debian Autogenerate .vimrc files and put the master in config/vimrc 2006-01-15 18:38:58 +01:00
doc Python: Give goto_url_hook only one argument, like follow_url_hook. 2007-01-01 17:45:36 +02:00
po po/Makefile (update-po): Remove cd $(srcdir). 2007-01-01 17:12:45 +02:00
src Python: Give goto_url_hook only one argument, like follow_url_hook. 2007-01-01 17:45:36 +02:00
test Add simple script to testing the various features of the -remote option 2006-12-04 21:50:01 +01:00
Unicode Bug 381: Store codepage-to-Unicode mappings as dense arrays. 2006-09-24 16:55:29 +03:00
.gitignore Autogenerate .vimrc files and put the master in config/vimrc 2006-01-15 18:38:58 +01:00
ABOUT-NLS Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
AUTHORS Convert AUTHORS file to use UTF-8 encoding 2006-11-11 14:48:34 +01:00
autogen.sh We loves us some autoheader 2005-09-27 23:23:38 +02:00
BUGS Drop .or from elinks.or.cz. 2005-12-29 04:35:02 +00:00
ChangeLog Tidyup. 2006-02-23 00:57:44 +01:00
configure.in Tidyup separation of configuration items 2006-12-10 01:30:16 +01:00
COPYING Clarify the GPL upgrades policy a bit, and propose an addition 2005-09-17 03:33:36 +02:00
features.conf Bug 841, CVE-2006-5925: Prevent enabling the SMB protocol. 2006-11-18 20:39:01 +02:00
INSTALL Remove some suspiciously looking empty lines 2006-01-19 02:23:01 +01:00
Makefile Regenerate Makefile.config automatically if config.status has changed. 2005-12-06 14:59:06 +01:00
Makefile.config.in Define datarootdir in Makefile.config.in, for better Autoconf compatibility. 2006-09-17 17:55:53 +03:00
Makefile.lib Remove cmd_installsrcdata. 2006-12-17 16:25:12 +02:00
NEWS Lots of NEWS. All important and many unimportant changes are listed. 2007-01-01 15:55:10 +02:00
README Drop .or from elinks.or.cz. 2005-12-29 04:35:02 +00:00
SITES SITES: Add 'Fan sites' and t_a's starshine.org inside 2006-11-08 19:46:20 +01:00
THANKS THANKS: Remove link to HSTI webpage as the domain is for sale. 2006-11-08 20:53:01 +02:00
TODO Drop .or from elinks.or.cz. 2005-12-29 04:35:02 +00:00

ELinks - an advanced web browser
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ELinks is an advanced and well-established feature-rich text mode web
(HTTP/FTP/..) browser. ELinks can render both frames and tables, is highly
customizable and can be extended via scripts. It is very portable and runs
on a variety of platforms.

The ELinks official website is available at

	http://elinks.cz/

Please see the SITES file for mirrors or other recommended sites.  If you
want to install ELinks on your computer, see the INSTALL file for further
instructions.

A good start point is documentation files available in doc/, especially the
file named index.txt.

If you want to request features or report bugs, see community information at
http://elinks.cz/community.html and feedback information available at
http://elinks.cz/feedback.html.

If you want to write some patches, please first read the doc/hacking.txt
document.

If you want to add a new language or update the translation for an existing
one, please read po/README document.

If you want to write some documentation, well, you're welcome! ;)



Historical notes
~~~~~~~~~~~~~~~~

Initially, ELinks was a development version of Links (Lynx-like text WWW
browser), with more liberal features policy and development style.  Its purpose
was to provide an alternative to Links, and to test and tune various new
features, but still provide good rock-solid releases inside stable branches.

Why not contribute to Links instead?  Well, first I made a bunch of patches for
the original Links, but Mikulas wasn't around to integrate them, so I started
releasing my fork. When he came back, a significant number of them got refused
because Mikulas did not like them, as he just wouldn't have any use for them
himself.  He wants to keep Links with a relatively closed feature set and merge
only new features which he himself needs.  It has advantages that the tree is
very narrow and the code is small and contains very little bloat.

ELinks, on the contrary, aims to provide a full-featured web browser, superior
to both lynx and w3m and with the power (but not slowness and memory usage) of
Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating
of the code, the development is driven in the course of modularization and
separation of add-on modules (like cookies, bookmarks, ssl, scripting etc).

For more details about ELinks history, please see

	http://elinks.cz/history.html

If you are more interested in the history and various Links clones and versions,
you can examine the website at

	http://links.sf.net/




vim: textwidth=80