Search results for query: *

Hm... mabye it will be easier to understand if put it like this: > set cmd {ls -al} then I want to execute that command, but not using exec (since that doesnt work for my specific commands). What's annoying is that ls -al works really fine if i type it in myself at the prompt. But i dosen't...

But it's in my tcl script I have a problem executing my command. I have a proucedure proc execute {command} { } where commad is a command that I want PrimeTime to execute like: "report_timing -from point1 -to point2". But I can't get the shell to execute that.

No it's not. But it's a program based around a TCL-shell. So all the scripts for the program can use TCL commands. So the prompt works both as a TCL-shell and for entering PrimeTime commands.

I am running a program called PrimeTime that does timing analysis on integrated circuits. When you start PrimeTime you get a prompt pt> From this prompt you can use TCL commands and internal PrimTime commands. An example of an internal command could be: report_timing -from point1 -to point2...

The problem is that I can not use exec because it is not a shell command that I want to execute. It is a command to the program that gives me the tcl-prompt.

I can not pass commands with arguments to the shell. To make a simple example: tcl> set b "ls" tcl> $b will run ls tcl> set b "ls -al" tcl> $b will complain about "ls" not being a kown command. I know that you can easily execute shell commands with exec. But i...