Copyright © 1997-2013,2014 by Thomas E. Dickey
Lynx is a fully featured World-Wide Web browser for users on both Unix and VMS platforms who are connected to those systems via cursor-addressable, character-cell terminals or emulators. That includes VT100 terminals, and desktop-based software packages emulating VT100 terminals (e.g., Kermit, Procomm, etc.).
I got involved with Lynx development by working with Jim Spath on an auto-configure script for Lynx. I have also made changes for Lynx that allow you to build it using the color support in the ncurses library. Since the release of Lynx 2.8 in early 1998, I have been acting as the patch coordinator for a group of people (including myself) doing ongoing development on Lynx. Besides ongoing support for the configure script, etc., I have done work to make lynx more robust (e.g., secure).
See the changelog for details:
Lynx's sources are stored on isc.org in PRCS archives. Klaus Weide set up PRCS 1.1.1 in 1997 on a previous host (slcc.edu). Jim Spath and I migrated this to isc.org in 1999 (using PRCS 1.2.15).
Each commit in PRCS becomes a patch-release for Lynx.
Our version numbering for Lynx confuses some people. PRCS provides for having a non-numeric portion of a branch identifier. We use this for cycling through the development, pre-release and release versions. The first patch towards the next release is marked with that target release's version. Thus
I also maintain my local archives in RCS. Originally, this recorded only the patch-releases of Lynx in PRCS. There were a few reasons for this:
However, since early 2004, I have committed most changes first to RCS, then applied the current change-set to PRCS. The end result is much the same; PRCS assigns the patch-version number in a few files, while most are marked with the "LynxId" RCS-tag. It allows me to keep closer track of individual changes.
Before each patch-release, I (usually) do a test-build on Windows. That builds several flavors, which I use in testing. Along with that, since 2007, I have made packages for a few of these executables:
This is the older color-scheme used by Lynx, from 1996. Links and form-fields are colored.
It happens that this flavor of the Windows executables requires OpenSSL to run. Your machine may already have OpenSSL installed; many programs use it. If not, you might find the "light" version from this page useful. In particular, you would need these DLLs, either in Lynx's directory or in your system32 directory:
I have tested Lynx using those DLLs in Lynx's directory.
The other installers do not require OpenSSL.
The "color-style" refers to the newer scheme where different HTML tags can be colored. It gives a better sense of the page's structure than highlighting links, and has been the default configuration since release 2.8.6 in October 2006.
Both of the curses configurations are built using PDCurses.
This is built using the slang library. The color scheme is like the first installer (essentially only coloring links and form-fields), but slang provides brighter background colors in a console window.
That said, here are links to the Lynx installers on my website:
All files are here: ftp://invisible-island.net/lynx/
Here is a link to the documentation files which are part of
I use this part of my website for test-builds of current code.
The Lynx Help Page