From: Justin Ekis <jekis@fastmail.us>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: configuring elinks how do I?
Date: Wed, 6 Apr 2005 18:30:15 -0400 [thread overview]
Message-ID: <20050406223015.GA4712@debian> (raw)
In-Reply-To: <20050406211648.GA1727@taylor.homelinux.net>
On Wed, Apr 06, 2005 at 05:16:48PM -0400, Lorenzo Taylor wrote:
>As for the URL you gave? elinks gave me a link to www.npr.org/programs/waitwait
>or something similar, which I clicked on and the page with the listen link came
>up. Links2 took me to this page after confirming that I really wanted to let
>the javascript redirect me to the URL. However the "Listen to the show" link
>does nothing at all in either elinks or links2.
It works for me in elinks. I get a dialog box asking what program I want
to use to open a file. You'll need MPlayer or something else that can
handle real audio streams.
I've been hearing that elinks Javascript support isn't very good, but
it's been working quite well here for quite a while now. I follow cvs
though, and maybe the stable 0.10 releases aren't getting the new
JavaScript stuff. I have procmail trash the commit messages for the
stable branch so I don't know what's been going into 0.10.x.
It seems strange to say that development code works better than stable
releases but for now as far as JavaScript goes that seems to be the
case.
If you feel like it, try checking out cvs head. The debian packaging
files are all there too so it's almost as easy to build. You'll need
automake and autoconf though. If 0.10 is as bad is it sounds you'll find
a huge improvement I think.
Hope this helps.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Sean McMahon
` Kenny Hitt
` Lorenzo Taylor
` Justin Ekis [this message]
` Kenny Hitt
` Sean McMahon
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=20050406223015.GA4712@debian \
--to=jekis@fastmail.us \
--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).