From: Shawn Kirkpatrick <shawn@shawnk.ca>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: bleeps and does anyone use goto
Date: Sun, 11 Sep 2016 23:00:11 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1609112247090.9776@odyssey> (raw)
In-Reply-To: <20160911222009.GA4177@my-p4>
I would use goto but in my kernel this doesn't work propperly at all. I'm on
a slightly older kernel version so maybe this has been fixed in a later
version.
What I'd like to have is the ability to map going to a specific line to a
key. I'm thinking of imitating the review mode feature in the old artic
vision program where pressing a through y takes you to the given line, a for
line 1, b for line 2, etc. Not having this feature has kept me from using
speakup for any serious work. Having the ability to move quickly to a given
point is a must for me.
Does speakup really not have an on-screen find? That would be long overdue
I'd say.
On Sun, 11 Sep 2016, David wrote:
> Yes, you cannot call kd_sound from within an interrupt.
> I set a 10 ms timer and let it fire when I am long out of the speakup code.
> Does anyone use goto? it is a lot of code for what Ithink is not a good
> feature. two features I would like to add are:
> collumn mode and on screen find. and drop that cussed goto.
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
David
` Zachary Kline
` Chuck Hallenbeck
` Willem van der Walt
` Shawn Kirkpatrick [this message]
` Gregory Nowak
` Shawn Kirkpatrick
` Al Sten-Clanton
` Tom Fowle
` Jude DaShiell
` Hart Larry
` Brian Buhrow
` Kirk Reiser
` Janina Sajka
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=alpine.DEB.2.10.1609112247090.9776@odyssey \
--to=shawn@shawnk.ca \
--cc=speakup@linux-speakup.org \
/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).