From: "Thomas D. Ward" <tward1978@earthlink.net>
To: Speakup List <speakup@braille.uwo.ca>
Subject: Possible problem with term types?
Date: Sun, 4 May 2003 11:45:09 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0305041129470.20372-100000@localhost.localdomain> (raw)
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.
next reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas D. Ward [this message]
` Tommy Moore
` Thomas D. Ward
` William F. Acker WB2FLW +1-303-722-7209
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.44.0305041129470.20372-100000@localhost.localdomain \
--to=tward1978@earthlink.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).