public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: links 2.1 and elinks was Re: Slackware is dropping Gnome
Date: Tue, 5 Apr 2005 12:38:19 -0500	[thread overview]
Message-ID: <20050405173819.GA7653@blackbox> (raw)
In-Reply-To: <20050404202032.GB2190@lnx3.holmesgrown.com>

Hi.

On Mon, Apr 04, 2005 at 01:20:34PM -0700, Steve Holmes wrote:
> 
> I'm still on pre15; didn't realize newer versions came out that
> recently.  Has there been improvements to javascript support in these
> later versions?
> 

There are several changes mentioned in the CHANGELOG file, but mostly
with other features and functions.  Remember, the biggest problem with
links 2.1 wasn't it's javascript, but not supporting other things like
cookies and http authorization.  Both of those seem to have been fixed
now.

> 
> I may have confused things a bit.  Yes, it was spidermonkey I was
> thinking of.  I recall reading the various requirements to get
> elinks going and at the time, it seemed overwelming to me.  Maybe it
> isn't all that bad but for some reason, I thought I heard that
> spidermonkey had some strange quirks.  Is elinks that good a deal?
> 

I like it.  For me, spidermonkey was just an apt-get command.  At this
time, I no longer use the cat except in some scripts I haven't updated.
The links 2.1 javascript is more complete, but elinks has 
features not in links2.1.
I start out on a site with elinks and try links 2.1 if I have problems
with javascript.

Hope this helps.
          Kenny


  reply	other threads:[~ UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Adam Myrow
 ` Gregory Nowak
   ` Adam Myrow
     ` Joseph C. Lininger
       ` Re[2]: " Farhan
       ` Kenny Hitt
         ` Chris Hofstader
           ` Kenny Hitt
             ` Chris Hofstader
     [not found]               ` <20050402155416.GA13919@blackbox>
                 ` Kenny Hitt
                   ` jim grimsby
                     ` hank smith
                     ` Kenny Hitt
                       ` jim grimsby
             ` Adam Myrow
               ` Kenny Hitt
                 ` Gregory Nowak
                   ` Janina Sajka
                   ` Kenny Hitt
                 ` Steve Holmes
                   ` links 2.1 and elinks was " Kenny Hitt
                     ` Trevor Astrope
                     ` Steve Holmes
                       ` Kenny Hitt [this message]
                         ` Steve Holmes
                           ` Igor Gueths
                             ` Sean McMahon
                               ` Kenny Hitt
                                 ` Lorenzo Taylor
                                   ` Justin Ekis
                                     ` Lorenzo Taylor
                                       ` jim grimsby
                                         ` Lorenzo Taylor
                                         ` Lorenzo Taylor
                                           ` jim grimsby
                   ` Gregory Nowak
         ` Laura Eaves
           ` Ned
             ` Laura Eaves
           ` Kenny Hitt
             ` Laura Eaves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050405173819.GA7653@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).