I have a script that logs in the user, does interact, then waits for the user to send internal commands, using "~" as the escape.

I am doing exact pattern matching:

Code:

interact {        "~login" {                login                }        "~bye" {                set suspend 1                exec kill -9 $PID                return                }         -echo "~ossi" {                ossi                }        }

The problem is that my xterm Function keys are defined to send certain strings when pressed (this a requirement of the remote application), and all the strings end in "~", such as "\033[11~" for F1. So when I'm connected to the host and press F1, nothing happens b/c the script is waiting to see if this is an internal command. I have to hit F1/enter.

I could use a different set of key mappings, or add a newline character into the current mapping, but I was wondering if there's some way in expect I could suppress this behavior.

I also could change the "~" escape character, but unfortunately it's needed for legacy reasons. Any thoughts appreciated.

on 03/06/08 at 16:54:45, jaymzter wrote:

I also could change the "~" escape character, but unfortunately it's needed for legacy reasons. Any thoughts appreciated.

Is that as both the escape character AND on the key mappings?  You can change neiher of them?  If so, what was the legacy solution?


By "~" I was referring to the escape character. The legacy solution would connect you to a system which required emulation of various terminal types, and used "~" for its internal commands.

The strings for these terminals are defined here http://www.jaymzworld.com/pages/sat.shtml. I was using "SUNT", but I think I will just try the w2ktt, as it doesn't use a "~".

---