G
garycubitt
Hi all,
I'm new to this group and I'm not sure if this is the right place to
be posting this question - so if this is the wrong place please could
you point me in the right direction.
The problem I'm having is as follows:
I have designed a perl script that acts as a wrapper to the sybase
command line querying tool sqsh. The wrapper uses pwp to
automatically log in to the sqsh process and allow the user to
interact with it through the perl script. The problem I have is that
the terminal configuration does not seem to follow through to the
pseudo terminal. For example if a sql query is entered that is
longer
the 25 chars and then the backspace key is used or the left arrow to
go back the line will start to move up the screen and will not flow
as
expected. Also from within sqsh it is possible to use vi, however
when I use vi nothing is visible until a (L) over the text and then I
can see it.
I'm really have no idea where to go to look for a possible solution
to
this - or even what may be causing it so I thought I'd give you guys
a
try!
The script uses the perl Comm.pl module to create the pseudo terminal
and start the child sqsh process.
Thanks
Gary
I'm new to this group and I'm not sure if this is the right place to
be posting this question - so if this is the wrong place please could
you point me in the right direction.
The problem I'm having is as follows:
I have designed a perl script that acts as a wrapper to the sybase
command line querying tool sqsh. The wrapper uses pwp to
automatically log in to the sqsh process and allow the user to
interact with it through the perl script. The problem I have is that
the terminal configuration does not seem to follow through to the
pseudo terminal. For example if a sql query is entered that is
longer
the 25 chars and then the backspace key is used or the left arrow to
go back the line will start to move up the screen and will not flow
as
expected. Also from within sqsh it is possible to use vi, however
when I use vi nothing is visible until a (L) over the text and then I
can see it.
I'm really have no idea where to go to look for a possible solution
to
this - or even what may be causing it so I thought I'd give you guys
a
try!
The script uses the perl Comm.pl module to create the pseudo terminal
and start the child sqsh process.
Thanks
Gary