TeraTerm 'disconnect' command unlinks MACRO (From Forum Message #86029)
From Forum Help [#86029]
I use a MACRO to connect to usb com ports. I have two issues with this:
A) If the com port i specify to connect with connect '/C=...' UPPON MACRO STARTUP does not exist, the .ttl script will terminate and close... (why? i dont want that). Alternatively, is there a way to list all available usb com port devices and THEN try to connect to each of those?
B) After connecting to a COM port, using the command 'disconnect 0' or 'disconnect 1', the MACRO closes/terminates. (How can i terminate the connection to the host (COM port) only, without terminating Teraterm?)
;Code that disconnects my macro when trying to connect to a port that does not exist, UPPON MACRO STARTUP:
;both com-ports 3 and 6 are available for connection. The others are not.
timeout = 4
connect '/C=1' ;this disconnects my MACRO. I dont want it to disconnect my macro.
;Code that closes my link to MACRO when using the 'disconnect command:
;both comport 3 and 6 are available for connection. The others are not.
connect '/C=3' ;this connects as normal.
disconnect 0 ;this closes my TeraTerm (I dont want it to close my teraTerm
dispstr 'TT is still active'
When the connection type is TCP/IP, "Auto window close" setting affects close or not close Tera Term window.
But when the connection type is Serial, Tera Term is not closed. It is a specification.
(A) 'connect' macro command do 2 actions.
It is written in command help. https://ttssh2.osdn.jp/manual/4/en/macro/command/connect.html
After connect '/C=...' failed, Tera Term is not connected to serial port, but Tera Term is alive. The link between MACRO and Tera Term is alive too.
To close linked Tera Term, call 'closett' macro command.
Or you can reuse linked Tera Term. To connect different remote host (serial port), call 'connect' macro command.
(B) Not reproduced in my environment.
'disconnect' macro command does not close Tera Term window.
Thank you, i re-stated my ticked Details. Can you check it again?
I am more specific not to the problem. I am also attaching the .INI file for you to make a better test.
My test script behaves as expected in my env.
In my env with your TERATERM.INI, my script behaves as expected too.
What about in your env?