Jump to content

Issue Information

  • #000152

  • Issue

  • 0 - None Assigned

  • Fixed

  • 4.0 (Build not known)

  • 4.0.1212

Issue Confirmations

  • Yes (0)No (0)

Regression with custom commands

Posted by eyebex on 04 September 2011 - 07:09 PM

In build 1211, there seems to be a regression with custom command for terminal sessions. If you want the custom command to immediately execute (instead of just being pasted into the terminal, waiting for you to press enter), you needed to simply add a return in the line defining the custom command. This trailing return seems to get stripped when upgrading to build 1211 from a previous build, resulting in the command to be again just pasted into the terminal, instead of being executed. Adding the trailing return again, however, now executes the command and pastes a second return to the console, resulting in the prompt to be printed again.

Maybe this is a Unix vs DOS line-ending issue in the custom command configuration?

changed status to: Confirmed

changed status to: Fixed

Fixed in 4.0 Build 1212

0 user(s) are reading this issue

0 members, 0 guests, 0 anonymous users