gutschke/wy60

"wyse60" compatible terminal emulator

wy60's Issues

Wy60 does not draw narrow border

The attached "menu" file contains Wy150 escape characters which should draw
narrow (1/2 pixel-wide) lines to generate a box on screen approx. 10
characters tall, and about 40 characters wide.  It works perfectly with a
Wyse 150 terminal, but Wy60 doesn't display anything.

Original issue reported on code.google.com by [email protected] on 1 Sep 2009 at 10:06

Attachments:

• menu

dim attribute non-functional

The Wy50/60 "dim" attribute appears to be non-functional.  I expected I
would need to write code for it, but I do see what appears to be some code
to handle DIM.

I realize that TERM=xterm doesn't have a "dim" capability, so I modified
the terminfo db by adding one for xterm, but it still doesn't get used by
Wy60.  I'm testing with a simple "tput dim", which works on a Wyse150
terminal, but not with Wy60.

Any pointers, or is the code just currently non-functional?

Original issue reported on code.google.com by [email protected] on 23 Nov 2009 at 6:00

Keyboard control codes for various terminals

A rather large set of (control) characters output by:

XTerm
Putty
Teraterm
Teraterm-mod1 (my mods to the keyboard map)
wy60 (stock wy60)
wy150 (wy60 mod for Wyse 150--patch to follow soon)
powerterm-wy60 (PowerTerm set to Wyse 60+ emulation)
powerterm-wy50 (apparently identical)
Wyse150+ (Model 9000983-01)

While I was reasonably careful recording these, watch out for the
occasional duplicate codes more than anything else.

My conclusions:
Putty can work with Wy60/150, but isn't close enough to XTerm for our
purposes, and doesn't allow key modifications without recompiling.
Termterm, with my manual modifications seems close enough to work with
Wy60/150.
PowerTerm doesn't try all that hard to really imitate Wyse, so it's
surprising it works as well as it does.
Wy150 is now a closer match to a Wyse 150+ terminal than PowerTerm.

Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 4:40

Attachments:

• keychars.tar.gz

wy60 hangs on start

What steps will reproduce the problem?
1. in a terminal window type 'wy60'

What is the expected output?
launches an interactive shell via the wy60 wrapper

What do you see instead?
Nothing, terminal session becomes completely unresponsive to ctrl-c, z, y etc. 
If I close the 
terminal, I see there are two wy60 processes left running which don't respond 
to TERM, so I have to 
kill -9.

What version of the product are you using? On what operating system?
2.0.9 compiled from source on Mac OS X 10.6.2

Please provide any additional information below.
Compilation seemed to go fine. wy60 -h and -v work fine, it's defintely a 
runnable app. I tried 
running it form inside Terminal.app and iTerm with same results. $TERM is set 
to 'linux', shell is 
zsh.

Original issue reported on code.google.com by [email protected] on 26 Nov 2009 at 2:19

Patch Wy60 for Wy150 compatibilty.

The changes I made are simple enough that a patch seems excessive.  Still,
I've attached one that will work.

Essentially, doing: 
  sed s/wy60/wy150/ 
on wy60.c got me 90% of the way there.  For my sanity I did so even where
it wasn't technically necessary, like descriptions, variables, etc.  

The other modifications I've made are as follows:

static char *cfgTerm            = "wy150";
static char *cfgInsertLine      = "\x1Bq";
static char *cfgShiftDelete     = "\x1BW";
static char *cfgShiftEnd        = "\x1BY";
static char *cfgShiftEndOfLine  = "\x1BY";
static char *cfgShiftInsert     = "\x1Bq";

  parseConfigurationFile(ETCDIR"/wy150.rc");
  parseConfigurationFile("/etc/wy150.rc");
                                "/.wy150rc");

This does NOT include the (simple) changes I made to get wy60 to treat
xterm as mono.

Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 6:26

Attachments:

• wy60-wy150-keys.diff

With TERM=xterm, wy60 behaves badly.

What steps will reproduce the problem?
1. Set: TERM=xterm
2. Start: wy60
3. Run: tput smul

What is the expected output? What do you see instead?

Should underline text.  Instead, turns fonts GREEN.  

What version of the product are you using? On what operating system?

2.0.9 on Linux (CentOS 5.0 - 5.3, Slackware 12.2, more...).  

Please provide any additional information below.

Setting TERM=vt220, pcvt25, etc. before starting wy60, will cause
underlining to work properly (but with a couple associated issues).

Pointers welcome, esp. where the relevant code lies.  I'm not too much of a
programmer, and the wy60 code has very few helpful comments.

Original issue reported on code.google.com by [email protected] on 28 Aug 2009 at 6:22

wy60 child process exits when INTR key pressed - linux 2.6.32-220.17.1.el6.i686

What steps will reproduce the problem?
1.Use wy60 to interface to a program that changes INTR (e.g. to escape)
2.When you type the INTR sequence, the child wy60 process receives SIGINT and 
exits because it uses the created pty as the control terminal
3.

What is the expected output? What do you see instead?

 Should keep running the application program
 Instead the connection terminates because the child wy60 process exits.

What version of the product are you using? On what operating system?

 wy60-2.0.9
 linux 2.6.32-220.17.1.el6.i686

Please provide any additional information below.

 I attached a patch that blocks SIGINT, and this fixes it for me.

Original issue reported on code.google.com by [email protected] on 8 Jul 2012 at 9:33

Attachments:

• wy60.c-patch