Cntrl+C to escape from browsw window

[Brian K. White]

On 10/5/2011 9:04 AM, calvin covington wrote:
> Hi
>
> I'm supporting filepro applications for a client in another state who
> has a fresh install of filepro 5.6 on a new AMD Athalon II Server
> running CentOS 5.6
>
> When I ssh into his system from my Centos 5.5 desktop from a tty screen,
> the filepro screens look fine.  However, in the applications, I can't
> exit from a browse window using cntl+c cntrl+c   (cntrl+c works as it
> should everywhere else I've tried it)
>
> He is having the same problem at the local level.  He is using Anita as
> an emulator on his pc terminals.
>
> (I have a current copy of his filepro applications on my system and
> everything works fine)

What are TERM and PFTERM?

PFTERM should be empty, or else it should be the same as TERM
(there is a reason for the existence of PFTERM and it is specifically to 
allow it to be different than TERM, but that is a very unusual need)

PFTERM overrides TERM so if PFTERM is set, fp will look at that instead 
of TERM

I would normally just assume no PFTERM, but it is one way to arrive at a 
discrepancy like you describe where only fp misbehaves, so I have to 
complicate things by mentioning it and having you check it.

Next, assuming no PFTERM, what is TERM?

Find that entry in fp/termcap

What is the LY= field in that entry?

Run "stty -a"
What is the "intr = ...;"

Wait, are you saying ctrl-c works elsewhere in fp, JUST not in a browse 
window?

-- 
bkw


>
>> From my location, if I connect to his system via a gnome terminal, the
> filepro borders are screwy and the cntrl+c does not function within the
> browse window -- otherwise things work.    If I connect via Anita from a
> pc, filepro screens look fine, but the cntrl+c still doesn't work from
> the within a browse window.
>
> I have 4 other remote Centos/filePro installs that I support (basically
> the same filepro applications) on which this cntrl+c thing is not a
> problem.
>
> I have copied my /appl/fp/termcap onto the new server, yet get the same
> results.  Our i18n files are identical.
>
> What are we missing?
>
>
> Thanks in advance
>
> Calvin
>
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>