From: Jacob Schmude <jacobs@ncinter.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Rolling My Own
Date: Tue, 2 Jan 2001 15:19:20 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.31.0101021515460.1568-100000@jspc.jspc.localhost> (raw)
In-Reply-To: <Pine.LNX.4.30.0101021027300.23518-100000@TekRD.grg.afb.net>
Hi
OK I don't know about the pine thing, but here's how I replaced the
bell tone (not recompiling):
Find your local setup script. Don't know what it is in caldera,
slackware's is /etc/rc.d/rc.local. Put the line:
setterm -bfreq $FREQUENCY
$FREQUENCY is, of course, the frequency you'd want. The default is
somewhere around 750. When I put this in /etc/rc.d/rc.local in slackware,
it took effect for all consoles.
On Tue, 2 Jan 2001, Janina Sajka wrote:
> Hello All -- and Happy New Year to all:
>
> Like many of you, I've become comfortable with compiling applications and
> rolling out linux kernels with Speakup compiled in. Well, OK, I've become
> somewhat comfortable with the basics. In other words, I'm ready to take
> the next tentative step. For me, this means tweaking some of my pet peaves
> with my computer into behaving like I want them to behave, rather than
> living with the defaults.
>
> I have two tweaks that I want to put into effect:
>
> 1.) The system bell stinks, imho. I hate that 1 kHz (or whatever) tone
> that one gets with Ctrl-G, ASCII char 7, or %BELL, or whatever the heck
> it's called in one programming environment or other. I want something
> else. The something else I want I can already effect in a simple shell
> script. Where and how do I make this the default? I presume this is
> somewhere in the kernel code as a call of some sort that I would
> substitute my own call with. Gak, what terrible grammar, but I suspect
> you'll get the idea;
>
> 2.) I intend to keep using Pine. Because I have Caldera on my portable
> system, I have to compile from sources if I want to upgrade to the latest
> and greatest. This gives me the opportunity to tweak, hopefully, how the
> Pine index is displayed. In other words, I want to change the order of
> summary info Pine will display when a folder's index is on screen;
>
> Any advice on the above would be greatly appreciated.
> --
>
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
>
> janina@afb.net
> (202) 408-8175
> http://www.afb.org/gov.html
>
>
> The invention of the printing press has been named the crowning
> achievement of the past millennium. Yet, electronic publishing will soon
> eclipse it. Read our White Paper: "Surpassing Gutenberg" available at:
>
> http://www.afb.org/ebook.html
>
> Are you developing software? Make it accessible to blind computer users.
> Read http://www.afb.org/technology/accessapp.html to learn how.
>
>
>
> _______________________________________________
> 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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Chris Nestrud
` Jacob Schmude [this message]
` Jason Fayre
` Janina Sajka
` Chris Nestrud
` Janina Sajka
` Ari Moisio
` John Covici
` Janina Sajka
` Geoff Shang
` Janina Sajka
Holmes, Steve
` 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=Pine.LNX.4.31.0101021515460.1568-100000@jspc.jspc.localhost \
--to=jacobs@ncinter.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).