Re: TN5250 problem

Thanks. I decided to go ahead and create the file. I may go ahead and copy
it to the /usr/local/etc location to be safe. :-)




-----Original Message-----
From: linux5250-bounces@xxxxxxxxxxxx [mailto:linux5250-bounces@xxxxxxxxxxxx]
On Behalf Of Scott Klement
Sent: Thursday, May 27, 2010 2:34 PM
To: Linux 5250 Development Project
Subject: Re: [LINUX5250] TN5250 problem

Hello,

The "+uninhibited"... uh, does something that I've completely
forgotten :-) I'm sure somebody will pipe up and tell you what it
does.

+uninhibited prevents you from having to hit "Error Reset" every time
you get an error. In other words, you see the error, but it doesn't put
your 5250 terminal into "input inhibited" state. Instead, it simply
lets you continue typing.

...This points out that there are are several options that you can
specify in .tn5250rc that would be cumbersome to specify evey time on
the command line. Of course you can specify every option on the
command line, but keeping them in .tn5250rc simplifies things and
make it easy to see just what options your session starts with.
Using .tn5250rc isn't required, but it sure is nice.

He isn't typing them at the command line every time.

The question was about whether there's any advantage to putting the
options into a .tn5250rc file vs. coding it directly in a "launcher" (an
icon that launches a program in KDE or Gnome or a similar environment)

Given that, I don't see any reason to use a .tn5250rc file, unless you
prefer it.

For those of us who like to be able to run tn5250 as a command, using a
.tn5250rc saves us a lot of typing. It's also useful when multiple
users share the same computer, because you can set the settings in one
place (/usr/local/etc/tn5250rc) instead of setting them separately for
each user.

If it doesn't apply to your circumstance, feel free to not use it. We
certainly don't expect every user to use every feature of tn5250.