unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Caps Lock affects Ctrl+keys
Date: Mon, 20 Jan 2014 19:24:14 +0100	[thread overview]
Message-ID: <87d2jmwly0.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.12433.1390240051.10748.help-gnu-emacs@gnu.org

Jude DaShiell <jdashiel@shellworld.net> writes:

> I'm using linux-speakup

Did you try that for this particular problem or do you
use it habitually? I have been experimenting with stuff
like that, notably emacspeak (a script that starts
Emacs with a TTS extension), only it won't shut up
because it is intended for blind people. While I can't,
uh, visualize their situation(s), even to a blind
person that's a lot of noise. Problem was that I
couldn't configure it without having it loaded, and
that made me crazy after just a few keystrokes and
cursor movements. So I checked it out with 'aptitude
show' and found that it was based on espeak, which is
available in the Debian repos as a stand-alone-tool,
and so I wrote

es () {
	espeak -s 130 -k 20 -v en -f $1 -w `basename $1 .txt`.wav
}

to create sound files from text, and it should be a
small task to setup defuns to interact with it.

For a sound file example (and the text file used as
input), check out [1]. I don't know if it can replace
reading. It will certainly not be as enjoyable. But
what do you do? All tricks to compensate for the loss
of information intake should be explored...

> over here and I don't use g.u.i. stuff on Linux I
> have to do that at work and shouldn't have to at
> home.

Right on!

> The only way I found to clear this state was to
> reboot the amd64 k8 athelon and that cleared it.

What? :)

[1] http://user.it.uu.se/~embe8573/espeak_demo/

-- 
underground experts united:
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2014-01-20 18:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 11:57 Caps Lock affects Ctrl+keys Yuri Khan
2014-01-20 14:47 ` Jude DaShiell
2014-01-20 15:24   ` Yuri Khan
2014-01-20 17:47     ` Jude DaShiell
     [not found]     ` <mailman.12433.1390240051.10748.help-gnu-emacs@gnu.org>
2014-01-20 18:24       ` Emanuel Berg [this message]
     [not found]   ` <mailman.12400.1390231499.10748.help-gnu-emacs@gnu.org>
2014-01-20 17:23     ` Emanuel Berg
2014-01-20 18:30       ` Yuri Khan
     [not found]       ` <mailman.12445.1390242632.10748.help-gnu-emacs@gnu.org>
2014-01-20 18:53         ` Emanuel Berg
2014-01-20 20:38 ` Yuri Khan
     [not found] ` <mailman.12458.1390250342.10748.help-gnu-emacs@gnu.org>
2014-01-20 22:55   ` Emanuel Berg
2014-01-21  2:10   ` Emanuel Berg
2014-01-21  5:07     ` Yuri Khan
     [not found]     ` <mailman.12490.1390280831.10748.help-gnu-emacs@gnu.org>
2014-01-21 17:38       ` Emanuel Berg
2014-01-24 14:38     ` Yuri Khan
2014-01-24 15:56       ` Stefan Monnier
     [not found]     ` <mailman.12684.1390574300.10748.help-gnu-emacs@gnu.org>
2014-01-24 15:22       ` Dan Espen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87d2jmwly0.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.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).