Building elinks from source isn't too much of a problem, as I remember the instructions at the elinks homepage is fairly complete. The main thing for javascript is to make sure you have spidermonkey installed (that includes the dev package of spidermonkey) and the configure script should detect it and enable javascript. If that fails, there probably is a way to tell it where to find spidermonkey. The ability to choose the build options for packages in gentoo is one thing going for its package management system, whereas apt in debian requires multiple packages for the different build configurations. Javascript support is reasonable. It can't manage all javascript, but will get you by for the most common stuff. From Michael Whapples ----- Original Message ----- From: "Erik Heil" <eheil@xxxxxxxxxxxxxxxx> To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> Sent: Tuesday, March 27, 2007 9:26 PM Subject: Re: Elinks and Speakup support > Hi. This is not generally related to Gentoo, but I can telly for a fact > that if you use Debian's elinks, it is not built with bittorrent or > javascript suppport. Any of you know what is the best way to deal with > this? On a side note, I can't fiure out why it wouldn't bwe built without > javascript. BTW, how well does elinks work with Javascript? That is, how > does it handle such things as client-side popups and the like? B/c many > times, JavaScript is used to generate dialog boxes and for client-side > validation of data before it gets sent to the server, amonst other things. >
