Yes, I have.
I tried
$(APP_PATH)\teraterm-4102\TTERMPRO $TO_UNIX_PATH{\C=$(SERIAL_PORT) \BAUD=$(SERIALMONITOR_BAUDRATE) \L=$(PROJECT_DIR)Log.txt \LA=E}
but it expanded as
C:\apps_Portable\CodeBlocks17ar\teraterm-4102\TTERMPRO {\C=3 \BAUD=1000000 \L=D:\KomplexCB\_Vysilani_100\Komplex00\Log.txt \LA=E}
But when I thought more about it today, I tried let the TERMINAL variable be
$(APP_PATH)\teraterm-4102\TTERMPRO \C=$(SERIAL_PORT) \BAUD=$(SERIALMONITOR_BAUDRATE) \L=$(PROJECT_DIR)Log.txt \LA=E
and the macro put in the Tools+
$TO_UNIX_PATH{$(TERMINAL)}
It expands now as
C:/apps_Portable/CodeBlocks17ar/teraterm-4102/TTERMPRO /C=3 /BAUD=1000000 /L=D:/KomplexCB/_Vysilani_100/Komplex00/Log.txt /LA=E
and it works
amazingly partially in Windows
The terminal application started
but the path to the Log.txt is ignored and the file is created in the terminal folder
If I try to convert the part back
$(APP_PATH)\teraterm-4102\TTERMPRO \C=$(SERIAL_PORT) \BAUD=$(SERIALMONITOR_BAUDRATE) \L=$TO_WINDOWS_PATH{$(PROJECT_DIR)}Log.txt \LA=E
the expansion contains the { } brackets again and the backslashes inside are slashes unfortunately
C:/apps_Portable/CodeBlocks17ar/teraterm-4102/TTERMPRO /C=3 /BAUD=1000000 /L={D:/KomplexCB/_Vysilani_100/Komplex00/}Log.txt /LA=E