mirror of
https://github.com/rkd77/elinks.git
synced 2024-10-01 03:36:26 -04:00
a229adb19a
By default some Python warning messages would be written to standard error by the interpreter. To prevent these warnings from making a mess of the ELinks screen, all warnings were turned into exceptions so they could be caught and displayed through the usual report_scripting_error() mechanism. With Python 3.2, this approach backfires: A new class of ResourceWarnings that are filtered by default (and hence would *not* have been written to standard error) are now turned into exceptions, and these exceptions can't be caught because they're emitted from the interpreter's cleanup code. As a result, the uncaught exceptions would make a mess of the ELinks screen. The new solution is to replace Python's standard library function warnings.showwarning() with one that turns warning messages into exceptions. This means we'll wait until a warning would have been written to standard error before turning it into an exception, so other warnings that would never have reached that point because they're filtered will remain unseen. (The behavior of warning messages is described in the documentation for the "warnings" module from Python's standard library.) |
||
|---|---|---|
| config | ||
| contrib | ||
| doc | ||
| po | ||
| src | ||
| test | ||
| Unicode | ||
| .gitignore | ||
| .mailmap | ||
| ABOUT-NLS | ||
| AUTHORS | ||
| autogen.sh | ||
| BUGS | ||
| ChangeLog | ||
| configure.in | ||
| COPYING | ||
| features.conf | ||
| INSTALL | ||
| Makefile | ||
| Makefile.config.in | ||
| Makefile.lib | ||
| NEWS | ||
| README | ||
| SITES | ||
| THANKS | ||
| TODO | ||
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 starting point is documentation files available in doc/, especially the file 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 aims to keep Links at a relatively closed feature set and merge only new features which he himself needs. It has the advantage 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