From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Speakup in user space, why or why not?
Date: Mon, 3 Oct 2005 02:37:33 -0400 [thread overview]
Message-ID: <000001c5c7e4$f03ba9c0$6701a8c0@QUARK> (raw)
In-Reply-To: <m1EMJKR-00015cC@gene3.ait.iastate.edu>
Thank you for your email
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Gene Collins
Sent: Monday, October 03, 2005 1:58 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Speakup in user space, why or why not?
Hi Sina. If your question was ment to be philisophical in nature, as to why
Speakup was not originally designed as a user space program, than you don't
get to ignore the issues of installation and bootup messages.
You already know that it's possible to write a speakup like user space
program, because there are other apps out there that do parts of what you
want. So if your question truly is technical in nature, there is no reson
why Speakup can't be a user space program, except that nobody has done it
yet.
So if you really are after knowledge, tell me what you think you've learned.
Whining about my response to you and calling me names publicly doesn't give
you an out. The only reasons Speakup is in kernel space are the very ones
you want to ignore. Speakup is hiddenfrom all running applications on the
system. They don't get to bypass it, and having Speakup in kernel space
allows for talking installations, spoken bootup message, and in many cases,
spoken kernel error messages. If you want to dismiss those reasons, then
there is no reason why Speakup shouldn't be a user space app, except for the
reason of time and interest I have already mentioned. Go for it.
If on the other hand the point of raising this discussion is to try to
change Kirk's mind about future Speakup design, well, it's possible, but not
very likely.
Remember, name calling is not an exceptable response. Have a nice day.
Gene
_______________________________________________
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: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
Sina Bahram
` Gregory Nowak
` Garrett Klein
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Kenny Hitt
` Sina Bahram
` Lorenzo Taylor
` Sina Bahram
` Gene Collins
` Sina Bahram
` Gene Collins
` Sina Bahram [this message]
` Scott Howell
` Charles Hallenbeck
` Sina Bahram
` ace
` Sina Bahram
` Sina Bahram
` Lorenzo Taylor
` Sina Bahram
` Luke Yelavich
` Jim Grimsby
` Sina Bahram
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='000001c5c7e4$f03ba9c0$6701a8c0@QUARK' \
--to=sbahram@nc.rr.com \
--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).