From: Kenny Hitt <kenny@hittsjunk.net>
To: Sean McMahon <smcmahon@usgs.gov>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: configuring elinks how do I?
Date: Wed, 6 Apr 2005 16:08:54 -0500 [thread overview]
Message-ID: <20050406210854.GA5224@blackbox> (raw)
In-Reply-To: <001101c53ad6$64b086f0$77ac7682@azwaterDOM.wr.usgs.gov>
Hi.
Leave cursor tracking turned on and use the options manager instead of
the menus to configure elinks.
For your other questions, read the docs. It is explained very well in
the documentation with the source code.
Kenny
On Wed, Apr 06, 2005 at 11:27:58AM -0700, Sean McMahon wrote:
> First a comment, congrats again to Shane for creating a new speakup iso for
> Debian. Even I could install it. Next, how do I configure elinks? It seems
> when I go to save my options it says it's saving but when I go back into the
> browser, things like numbering aren't saved. I also need some help on how to
> make speakup no where I'm at. It seems with cursoring off, I hear the menus,
> but if there is two options at the current line, I can't use the speakup review
> keys because they still read the page I visited before entering the menu system.
> Finally, what option do I enable for javascript support? I went to a page that
> identified itself to elinks as having javascript, but the script couldn't
> execute. I did not get the unsupported url scheme you get from lynx the cat.
> The particular url I was focused on was http://waitwait.npr.orgg. From there go
> to the link that says listen to the show or listen. Could just be bad
> scripting, but I don't know where else I should test elinks.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Sean McMahon
` Kenny Hitt [this message]
` Lorenzo Taylor
` Justin Ekis
` 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=20050406210854.GA5224@blackbox \
--to=kenny@hittsjunk.net \
--cc=smcmahon@usgs.gov \
--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).