Currently when a terminal ENQ is sent from the host (Example: echo -en "\005") vx connectbot sends back the $TERM value, with no trailing CR or LF.
The correct string for a vt220 is technically an escape sequence like "ESC[?62;1;2;6;7;8;9c" where the different numbers describe different capabilities and options of the particular terminal (vs the terminal type). Sometimes the host software requires this.
Many terminals and emulators also let the user define what to send back for answerback, including a way to define special bytes like carriage return, so the user can specify a response like "myterm-foo^M" or "mystring\013" etc. Then on the host it's very easy for a "read" shell command to issue the ^E and read the response back. Sometimes the host environment depends on this.
I know development is essentially halted on this project at this time, and I am free to try to hack on it myself. I am posting this basically for reference.
Currently when a terminal ENQ is sent from the host (Example: echo -en "\005") vx connectbot sends back the $TERM value, with no trailing CR or LF.
The correct string for a vt220 is technically an escape sequence like "ESC[?62;1;2;6;7;8;9c" where the different numbers describe different capabilities and options of the particular terminal (vs the terminal type). Sometimes the host software requires this.
Many terminals and emulators also let the user define what to send back for answerback, including a way to define special bytes like carriage return, so the user can specify a response like "myterm-foo^M" or "mystring\013" etc. Then on the host it's very easy for a "read" shell command to issue the ^E and read the response back. Sometimes the host environment depends on this.
I know development is essentially halted on this project at this time, and I am free to try to hack on it myself. I am posting this basically for reference.