Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 3169
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADE-XL: possible to change binding of "Open Terminal" button (launch xterm)?

dontpanic

Hi! I recently switched from IC617 to ICADV12.2 (64b.500.5), and now when I press the "Open Terminal" button in ADE-XL (results tab), two strange things happen:

1) It doesn't open the terminal on the results directory corresponding to the tab from which I click the button. Instead, it takes me to my home folder.

2) It doesn't seem to run the "xterm" command as defined in my .cshrc, where it's aliased to "xterm -rv" to reverse the colors. Instead, it seems to execute a raw 'xterm' command. Since I have my shell colors (prompt, filetypes, etc) configured for a dark background, the opened xterm has very bad contrast and becomes very difficult to use.

In IC617 these problems wouldn't occur: the terminal was opened in the results directories, and it executed xterm as aliased in my .cshrc (thus with the reversed colors).

Is there a way I can change what the "Open Terminal" button executes in ICADV12.2, to modify it to what IC617 was running?

Thanks and regards, Jorge.

  • Hi Jorge,

    I don't believe it would ever have picked up an alias from your .cshrc because it always ran the command via system() which uses "sh" rather than "csh". Nothing has changed in this respect for ages.

    I suspect that you may have had the cdsenv var set:

    adexl.gui openTerminalCommand

    (so try looking at envGetVal("adexl.gui" "openTerminalCommand") - if this isn't set, it simply launches "xterm -T 'testName' &" where testName is the name of the test. So you can change it yourself using:

    envSetVal("adexl.gui" "openTerminalCommand" 'string "xterm -rv")

    The working directory is set by ADE before it launches the xterm and then set back again afterwards. So you should be able to do:

    envSetVal("adexl.gui" "openTerminalCommand" 'string "pwd ; xterm -rv")

    (note you must put a space after pwd) and then it will print the working dir in the terminal that you launched virtuoso from before the xterm is launched. You might also want to type tracev(dirPath) in the CIW too before launching the terminal - then the directory should appear in the CIW that it's going to set it to. 

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Thanks for your prompt reply, Andrew! I indeed had the variable set to just 'xterm'; switching to 'xterm -rv' did the trick Slight smile

    W.r.t. the directory issue, your debugging suggestion pointed the culprit: a definition in my shell configuration indeed had the effect of redirecting to my home upon login (actually, it automatically changed to a folder, launched a script which needs to be launched from that location (as it extracts some info from the path--not my idea! :P), and then switched back to home). I removed this from my .cshrc and now everything is back to normal.

    Thanks a million for your help! Have a great weekend!!! Smiley

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.