From kazabe at gmail.com Mon Jun 8 15:24:37 2009 From: kazabe at gmail.com (kazabe) Date: Mon Jun 8 15:25:12 2009 Subject: [As-users] differences between aterm and the tty1 Message-ID: Hi. Im using a cobol app in my linux server. All the station run on windows actually, and use putty to access to the server. Now im migrating the station to linux, but im detecting a problem when the user need to access to the remote application. If the desktop try to access from the tty1 to the server, all the app work perfectly. But if try to access from a X console (we try with aterm and gnome-terminal) the app lost too many issues. Some function keys dont work, cant be displayed to fullscreen, the menu orders are wrong, etc. Is posible use in aterm all the features obtained in the tty1? Thanks in advance ?Existen dos cosas infinitas: el universo y la estupidez humana... y no estoy muy seguro de la primera? : Albert Einstein From lists-kyle at foobox.homelinux.net Tue Jun 16 15:25:57 2009 From: lists-kyle at foobox.homelinux.net (Kyle Liddell) Date: Tue Jun 16 15:26:12 2009 Subject: [As-users] Issues with aterm with screen or old/different unix Message-ID: <20090616202557.GA4411@athlon> Can anybody give me help with these two problems? 1. Using mutt (for example) inside aterm on some systems causes some special characters to be displayed incorrectly. In mutt, when viewing a thread of emails, the arrow symbols are junk characters, and if a non-ascii character is on a line, it will usually cause the next line to be blank. aterm on fedora and debian do this, aterm on gentoo works fine. (aterm on gentoo and fedora are compiled from latest source, on debian it's the binary in testing.) If I use xterm on fedora and debian, everything works fine. 2. Many non-linux systems I use don't know about aterm, so, for example, running 'top' doesn't work correctly, and emacs won't run. Solaris gives messages like "top: no termcap entry for a `rxvt' terminal", and aterm on AIX sort of works, but some things grumble a bit. If I set TERM="xterm", then things seem to play nice. I'm not really sure where the problem lies with terminals, and I'm not sure of the Right Way to fix it... Thanks, Kyle From as_ml at vaevictus.net Tue Jun 16 15:53:32 2009 From: as_ml at vaevictus.net (Nathan 'Vaevictus' Mahon) Date: Tue Jun 16 15:58:54 2009 Subject: [As-users] Issues with aterm with screen or old/different unix In-Reply-To: <20090616202557.GA4411@athlon> References: <20090616202557.GA4411@athlon> Message-ID: <4A38064C.5030702@vaevictus.net> First, I should preface this with aterm is deprecated in favor of urxvt, aka. rxvt-unicode. Second, we go to the second problem. If your OS's don't have a termcap for either rxvt or aterm, you need to get one installed. It may be a problem on some OS's ... and may be a big problem on others. using the wrong term settings will cause some of your issues in problem #1. Lastly, you need to a.) have termcap settings for rxvt, xterm will work somewhat, but you'll see special character issues. b.) unicode will never work properly under aterm. c.) in addition to the TERM settings, you need proper locale, lang, and font settings, *and* you need each layer of your terminal to be speaking the same thing. aterm connected to screen connected to mutt is 3 layers. This is becoming more and more of a problem as OS's continue to make unicode the default. Your discrepancy between fedora and gentoo may be that fedora is defaulting a setting differently than gentoo is. xterm supports unicode, so I'd imagine that you're running into some unicode, if "everything works fine" with it. :) what's your LANG set to in your shells? n8 Kyle Liddell wrote: > Can anybody give me help with these two problems? > > 1. Using mutt (for example) inside aterm on some systems causes some special characters to be displayed incorrectly. In mutt, when viewing a thread of emails, the arrow symbols are junk characters, and if a non-ascii character is on a line, it will usually cause the next line to be blank. aterm on fedora and debian do this, aterm on gentoo works fine. (aterm on gentoo and fedora are compiled from latest source, on debian it's the binary in testing.) If I use xterm on fedora and debian, everything works fine. > > 2. Many non-linux systems I use don't know about aterm, so, for example, running 'top' doesn't work correctly, and emacs won't run. Solaris gives messages like "top: no termcap entry for a `rxvt' terminal", and aterm on AIX sort of works, but some things grumble a bit. If I set TERM="xterm", then things seem to play nice. > > I'm not really sure where the problem lies with terminals, and I'm not sure of the Right Way to fix it... > > Thanks, > Kyle > _______________________________________________ > As-users mailing list > As-users@afterstep.org > http://mail.afterstep.org/mailman/listinfo/as-users > From lists-kyle at foobox.homelinux.net Thu Jun 18 04:23:05 2009 From: lists-kyle at foobox.homelinux.net (lists-kyle@foobox.homelinux.net) Date: Thu Jun 18 04:23:57 2009 Subject: [As-users] Issues with aterm with screen or old/different unix In-Reply-To: <4A38064C.5030702@vaevictus.net> References: <20090616202557.GA4411@athlon> <4A38064C.5030702@vaevictus.net> Message-ID: <20090618092305.GA3832@foobox.homelinux.net> I installed terminfo files for rxvt-unicode and screen, and now Solaris and AIX play nice. It turned out that on my gentoo system, LANG was set to en_US, and everywhere else it is en_US.UTF-8. I switched over to UTF-8, and installed urxvt, and now the problems are gone. Thanks! (apologies for duplicate/bad mail) On Tue, Jun 16, 2009 at 04:53:32PM -0400, Nathan 'Vaevictus' Mahon wrote: > First, I should preface this with aterm is deprecated in favor of urxvt, > aka. rxvt-unicode. > > Second, we go to the second problem. If your OS's don't have a termcap > for either rxvt or aterm, you need to get one installed. It may be a > problem on some OS's ... and may be a big problem on others. using the > wrong term settings will cause some of your issues in problem #1. > Lastly, you need to a.) have termcap settings for rxvt, xterm will work > somewhat, but you'll see special character issues. b.) unicode will > never work properly under aterm. c.) in addition to the TERM settings, > you need proper locale, lang, and font settings, *and* you need each > layer of your terminal to be speaking the same thing. aterm connected > to screen connected to mutt is 3 layers. > > This is becoming more and more of a problem as OS's continue to make > unicode the default. Your discrepancy between fedora and gentoo may be > that fedora is defaulting a setting differently than gentoo is. xterm > supports unicode, so I'd imagine that you're running into some unicode, > if "everything works fine" with it. :) > > what's your LANG set to in your shells? > > n8 >