Text problems with Cygwin >1.1.14 and TinyFugue

Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

The problem was first noticed with Cygwin 1.1.14 but I wanted to see if it
would persist in a later release, which it has.  I have noticed in in 1.1.15
as well.  When trying to use TinyFugue (http://tf.tcp.com/~hawkeye/tf) with
these versions of Cygwin I cannot enter text.  When I try to type anything I
am present with an unending stream of garbage. It bears a resemblance to
binary. The only way to quit tf with these versions of Cygwin is to close the
window.  I tried reconfiguring/recompiling against 1.1.15 but that did not
work. Backing out to 1.1.13-2, the last working version, does work.
Interestingly, the version compiled against 1.1.15 does work with the older
version of Cygwin. I built a version of tf with debugging symbols, but I was
unable to see any problems with what it is doing.  The problems are
independent of the shell I run tf under; I tried with bash and zsh and both
produced the same results.  I had the same problems regardless of whether or
not I used visual mode in tf as well.  Can anyone help?
--
Jonathan Fosburgh
AIX/SAN Administrator
Communications and Computer Services
UT MD Anderson Cancer Center
Houston, TX
IBM Certified Specialist - AIX v4.3 System Administration

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jeremy Hetzler]

At 07:59 AM 11/12/2002 -0600, Jonathan Fosburgh wrote:
>The problem was first noticed with Cygwin 1.1.14 but I wanted to see if it
>would persist in a later release, which it has.  I have noticed in in 1.1.15
>as well.  When trying to use TinyFugue (http://tf.tcp.com/~hawkeye/tf) with
>these versions of Cygwin I cannot enter text.  When I try to type anything I
>am present with an unending stream of garbage. It bears a resemblance to
>binary. The only way to quit tf with these versions of Cygwin is to close the
>window.  I tried reconfiguring/recompiling against 1.1.15 but that did not
>work. Backing out to 1.1.13-2, the last working version, does work.
>Interestingly, the version compiled against 1.1.15 does work with the older
>version of Cygwin. I built a version of tf with debugging symbols, but I was
>unable to see any problems with what it is doing.  The problems are
>independent of the shell I run tf under; I tried with bash and zsh and both
>produced the same results.  I had the same problems regardless of whether or
>not I used visual mode in tf as well.  Can anyone help?

Looks like a weird interaction between Cygwin, rxvt and tf. When you press 
a key, tf doesn't receive it. Instead, something starts printing what look 
like scancodes (lots of Ps, tildes, and ['s) out to the screen ad 
infinitum. If you kill tf, the keys you pressed while it was running show 
up in the rxvt buffer. (tf 4.0s1, Cygwin 1.3.15-2, rxvt 2.7.2, win2ksp3)

You might try switching to windows console as a workaround.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

On Tuesday 12 November 2002 09:10 pm, Jeremy Hetzler wrote:

When I tested under bash that was using the Cygwin console, which is cmd.exe. 
 HOwever, when I get a chance, I will reinstall 1.1.15 and try from a command 
prompt with no Cygwin shell, at least for comparison.
-- 
Jonathan Fosburgh
AIX/SAN Administrator
Communications and Computer Services
UT MD Anderson Cancer Center
Houston, TX
IBM Certified Specialist - AIX v4.3 System Administration

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

On Wednesday 13 November 2002 07:32 am, Jonathan Fosburgh wrote:
> On Tuesday 12 November 2002 09:10 pm, Jeremy Hetzler wrote:
>
> When I tested under bash that was using the Cygwin console, which is
> cmd.exe. HOwever, when I get a chance, I will reinstall 1.1.15 and try from
> a command prompt with no Cygwin shell, at least for comparison.
Same problem from the DOS prompt.  Also, I saw the same thing with the most 
recent snapshot of cygwin1.dll (11/6).  While playing around, I did notice  
that the characters I typed wound up being passed to the shell after I killed 
tf.
-- 
Jonathan Fosburgh
AIX/SAN Administrator
Communications and Computer Services
UT MD Anderson Cancer Center
Houston, TX
IBM Certified Specialist - AIX v4.3 System Administration

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Text Problems with Cygwin > 1.3.14 and TinyFugue WAS Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

> Same problem from the DOS prompt.  Also, I saw the same thing with the most
> recent snapshot of cygwin1.dll (11/6).  While playing around, I did notice
> that the characters I typed wound up being passed to the shell after I
> killed tf.
Does anyone still have snapshots of the cygwin dll from betweem 1.3.13-2 and 
1.3.14. Note, in the original subject and and messages I had somehow thought 
the current versions of Cygwin were 1.1.x, not 1.3.x. :) I am currently 
running 1.3.13 with no problems.  It is 1.3.14 and above that show this 
problem.
-- 
Jonathan Fosburgh
AIX/SAN Administrator
Communications and Computer Services
UT MD Anderson Cancer Center
Houston, TX
IBM Certified Specialist - AIX v4.3 System Administration

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Text Problems with Cygwin > 1.3.14 and TinyFugue WAS Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

On Friday 15 November 2002 08:46 am, you wrote:

> Does anyone still have snapshots of the cygwin dll from betweem 1.3.13-2
> and 1.3.14. Note, in the original subject and and messages I had somehow
> thought the current versions of Cygwin were 1.1.x, not 1.3.x. :) I am
> currently running 1.3.13 with no problems.  It is 1.3.14 and above that
> show this problem.

Curiouser and curiouser.  With 1.3.15 and the 11/20 snapshot I can run tf 
from within strace. That is, I can enter text into it and even connect to 
worlds.  That is not to say that I can *use* it, the output doesn't work 
quite correctly.  HTH.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Text Problems with Cygwin > 1.3.14 and TinyFugue WAS Re: Text problems with Cygwin >1.1.14 and TinyFugue

[Jonathan Fosburgh]

On Wednesday 20 November 2002 02:37 pm, you wrote:

>
> Curiouser and curiouser.  With 1.3.15 and the 11/20 snapshot I can run tf
> from within strace. That is, I can enter text into it and even connect to
> worlds.  That is not to say that I can *use* it, the output doesn't work
> quite correctly.  HTH.

SImply noting that the problem persists in 1.3.16.  I'll continue trying to 
look into it.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/