From: Ryan Mann <rmann@rmisp.net>
To: <speakup@braille.uwo.ca>
Subject: Re: a few things
Date: Sun, 16 Sep 2001 20:29:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0109162027370.18283-100000@rmnet> (raw)
In-Reply-To: <Pine.LNX.3.96.1010916145129.256A-100000@deedra>
Make config gives a text only interface to the kernel configuration where
you just answer y or n for everything that you want to include in the
kernel.
On Sun, 16 Sep 2001, Deedra Waters wrote:
> um.. what's the difference between the two? and am I going to have to go
> back to the kernel with out speech to fix this?:p
>
> On Sun, 16 Sep 2001, Gregory Nowak wrote:
>
> > do make config instead of make menuconfig.
> > Greg
> >
> >
> > On Sun, Sep 16, 2001 at 12:46:25PM -0400, Deedra Waters wrote:
> > > Well, after a couple of days of fighting with my computer I finally
> > > got to install the cvs updates for speakup. I got a crash course in
> > > recompiling my kernel but did fine there. Hear's something I noticed
> > > though and not sure if there is another way around this... When I was
> > > recompiling the kernel in the menus it appears tha speakup seems to have
> > > trouble tracking things like when I'd up and down arrow between items I
> > > could never really be sure what item I had selected or not...
> > > This has suddenly become a problem in the sense that I recompiled the
> > > kerneljust fine with no errors, but apparrently didn't select the right
> > > speech synthisizer. I'm not really sure how to get around that/fix it,
> > > I've got someone who's been teaching me... But am mor curious as to wether
> > > there is a better way to work with speakup in menues like that... If
> > > anyone has suggestions I'd appreciate it.
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> 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: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters
` Gregory Nowak
` Deedra Waters
` Ryan Mann [this message]
` Janina Sajka
` Raul A. Gallegos
` Buddy Brannan
` Kirk Reiser
` Deedra Waters
` Cláudio Haase
` Deedra Waters
` Cláudio Haase
` Janina Sajka
` Deedra Waters
` Janina Sajka
-- strict thread matches above, loose matches on Subject: below --
A " Michael Whapples
` Justin Ekis
` Michael Whapples
` Justin Ekis
` Michael Whapples
a " Deedra Waters
` Kerry Hoath
Deedra Waters
Gregory Nowak
Gregory Nowak
Gregory Nowak
Holmes, Steve
` Janina Sajka
Holmes, Steve
` Tommy Moore
` Janina Sajka
` Deedra Waters
` Chris Schulte
` Janina Sajka
` Janina Sajka
Holmes, Steve
` Janina Sajka
Holmes, Steve
` Tommy Moore
` Deedra Waters
` Deedra Waters
` Buddy Brannan
` Janina Sajka
` Janina Sajka
` Deedra Waters
` Janina Sajka
` Kirk Wood
` Gregory Nowak
` Kerry Hoath
` John Covici
Debian with speakup Kenny Hitt
` Tommy Moore
` Kenny Hitt
` a few things Deedra Waters
` Kirk Wood
` Deedra Waters
` Janina Sajka
` Deedra Waters
` Janina Sajka
` Gregory Nowak
` Kirk Wood
` 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.33.0109162027370.18283-100000@rmnet \
--to=rmann@rmisp.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).