* Possible problem with term types?
@ Thomas D. Ward
` Tommy Moore
` William F. Acker WB2FLW +1-303-722-7209
0 siblings, 2 replies; 4+ messages in thread
From: Thomas D. Ward @ UTC (permalink / raw)
To: Speakup List
Hello, list.
For a couple of versions of Red Hat now I've noticed a problem I've not
been able to nail down the problem. When a sub shell such as screen, su, etc
are launched speak up and even yasr want to read the bash prompt every
single time a key is pressed.
However, when I switched my shell from bash to csh this problem completely
vanished. Is this a general bash problem or does Red Hat have some problem
handling term types when sub shells like screen are launched?
If anyone has a fix for bash working properly in screen please let me
know. Otherwise I'll just have to stay with csh which seams to work fine.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Possible problem with term types?
Possible problem with term types? Thomas D. Ward
@ ` Tommy Moore
` Thomas D. Ward
` William F. Acker WB2FLW +1-303-722-7209
1 sibling, 1 reply; 4+ messages in thread
From: Tommy Moore @ UTC (permalink / raw)
To: speakup
This sort of behavior occur with RH 9? I know it did with 8.0 and
never really figured out why it did.
This also happens with Mandrake systems I've found as well so its not
strictly in RH.
I've only really used one mandrake system so I can't exactly say which
version it was either.
Was quite some time ago. Maybe over a year ago.
Tommy
On Sun, May 04, 2003 at 11:45:09AM -0400, Thomas D. Ward wrote:
>
> Hello, list.
> For a couple of versions of Red Hat now I've noticed a problem I've not
> been able to nail down the problem. When a sub shell such as screen, su, etc
> are launched speak up and even yasr want to read the bash prompt every
> single time a key is pressed.
> However, when I switched my shell from bash to csh this problem completely
> vanished. Is this a general bash problem or does Red Hat have some problem
> handling term types when sub shells like screen are launched?
> If anyone has a fix for bash working properly in screen please let me
> know. Otherwise I'll just have to stay with csh which seams to work fine.
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Possible problem with term types?
` Tommy Moore
@ ` Thomas D. Ward
0 siblings, 0 replies; 4+ messages in thread
From: Thomas D. Ward @ UTC (permalink / raw)
To: speakup
Yes, that is correct. it does happen on Mandrake as well.
I've not installed speakup on any Mandrake systems, but yasr has an
identical problem on Mandrake Linux as with Red Hat.
On Sun, 4 May 2003, Tommy Moore wrote:
> This sort of behavior occur with RH 9? I know it did with 8.0 and
> never really figured out why it did.
> This also happens with Mandrake systems I've found as well so its not
> strictly in RH.
> I've only really used one mandrake system so I can't exactly say which
> version it was either.
> Was quite some time ago. Maybe over a year ago.
>
> Tommy
>
> On Sun, May 04, 2003 at 11:45:09AM -0400, Thomas D. Ward wrote:
> >
> > Hello, list.
> > For a couple of versions of Red Hat now I've noticed a problem I've not
> > been able to nail down the problem. When a sub shell such as screen, su, etc
> > are launched speak up and even yasr want to read the bash prompt every
> > single time a key is pressed.
> > However, when I switched my shell from bash to csh this problem completely
> > vanished. Is this a general bash problem or does Red Hat have some problem
> > handling term types when sub shells like screen are launched?
> > If anyone has a fix for bash working properly in screen please let me
> > know. Otherwise I'll just have to stay with csh which seams to work fine.
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Possible problem with term types?
Possible problem with term types? Thomas D. Ward
` Tommy Moore
@ ` William F. Acker WB2FLW +1-303-722-7209
1 sibling, 0 replies; 4+ messages in thread
From: William F. Acker WB2FLW +1-303-722-7209 @ UTC (permalink / raw)
To: Speakup List
Hi,
The problem is caused by the Unicode support introduced in RH8.0. If
you look in /etc/sysconfig/i18n, you'll probably find a statement like:
LANG="en_US.UTF-8"
You can copy the file to your home directory as .i18n, note the leading
dot. You can then edit the line to read: LANG="en_US"
If you want the original Unix sorting rules found in RH before 7X, say:
LANG="C"
HTH.
--
Bill in Denver
On Sun, 4 May 2003, Thomas D. Ward wrote:
>
> Hello, list.
> For a couple of versions of Red Hat now I've noticed a problem I've not
> been able to nail down the problem. When a sub shell such as screen, su, etc
> are launched speak up and even yasr want to read the bash prompt every
> single time a key is pressed.
> However, when I switched my shell from bash to csh this problem completely
> vanished. Is this a general bash problem or does Red Hat have some problem
> handling term types when sub shells like screen are launched?
> If anyone has a fix for bash working properly in screen please let me
> know. Otherwise I'll just have to stay with csh which seams to work fine.
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Possible problem with term types? Thomas D. Ward
` Tommy Moore
` Thomas D. Ward
` William F. Acker WB2FLW +1-303-722-7209
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).