Re: expect script doesnt pass graphics chars correctly
- From: Jeremy Cook <jeremy.cook@xxxxxxxxxxx>
- Date: Tue, 20 May 2008 14:55:11 +0200
Ok, thanks for that. In the end I managed to solve my problem using 'empty' in a bash shell script. Much simpler than expect, but it does what I need.
Jeremy
vitic wrote:
On May 19, 7:07 am, Jeremy Cook <jeremy.c...@xxxxxxxxxxx> wrote:.Hi folks,
My expect script needs to automate login to a terminal server which is
running a text based interface. The text based program assumes "scoansi"
terminal type and "ibm850" character encoding.
When I carry out the login steps by hand everything works beautifully
and the ansi graphics look good (well as good as it gets...). However
when I try to automate this with expect, something is going wrong with
the terminal emulation/setup/whatever and the graphics characters do not
show properly. I feel it must be some sort of tty mode issue, but have
not been able to find a solution. Any and all comments are welcome.
A transcript of my script:
#!/usr/bin/expect -f
spawn -nottyinit ssh -t some...@xxxxxxxxxxxx
set ssh $spawn_id
expect "*?assword: "
send -- "yadayada\r"
expect "\u0005"
stty -echo
send -- "okydoky\r"
stty raw -echo
interact -reset -output $ssh
Now I can interact, but all of the graphics chars are garbled.
eg ?Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"Ã"
instead of -----------------
Any ideas? Or can I jump out of expect somehow at the end (I dont need
it anymore once the last send has been done).
Jeremy
About 5 years ago I used expect to automate terminal based SAP
administration. I had the same problem with the ANSI terminal and as
far I can remember now, there was no way around it. What you see on
the screen is not what Expect sees. The terminal driver translates the
characters to be suitable for your screen and you don't see any
control sequences but Expect does. Also, the drawing of the text on
the terminal screen does not always happen sequentially (any part of
the screen can be repainted at any time by the terminal driver).
Meanwhile, expect reads everything sequentially. What I have done is
discard irrelevant data and only look for distinct peaces of relevant
data. It is somewhat a brute force programming and is not very exact,
although it worked just fine for me. First, use the autoexect script
to record your entire session and then modify the captured session to
suit your needs. The Expect book also mentions the same problem and
the advice has been similar to what I have done, as far as I can
remember.
Hope that helps,
---Victor
- References:
- expect script doesnt pass graphics chars correctly
- From: Jeremy Cook
- Re: expect script doesnt pass graphics chars correctly
- From: vitic
- expect script doesnt pass graphics chars correctly
- Prev by Date: Re: exportSelection and KDE freeze?
- Next by Date: Re: exportSelection and KDE freeze?
- Previous by thread: Re: expect script doesnt pass graphics chars correctly
- Next by thread: Freewrap Help: I can't copy a VFS mounted file to local directory
- Index(es):
Relevant Pages
|
