#98 — Results window interpretation requires ""
by
Henning Stahlberg
—
last modified
Jun 21, 2012 06:42 PM
| State | Unconfirmed |
|---|---|
| Version: |
—
|
| Area | Functionality |
| Issue type | Bug |
| Severity | Critical |
| Submitted by | Henning Stahlberg |
| Submitted on | Jun 21, 2012 |
| Responsible |
—
|
| Target release: |
—
|
If I try to set a variable to a certain value with a Custom-1.script, then the parameter requires "".
echo "set SYN_Unbending = 1" >> LOGS/${scriptname}.results
does not do it.
But
echo "set SYN_Unbending = \"1\"" >> LOGS/${scriptname}.results
doesn't work either, because csh is filtering out the \".
How can we echo " into a results file?
Or, can we modify the results interpreter of 2dx_merge, so that parameters without the " can also be interpreted?
echo "set SYN_Unbending = 1" >> LOGS/${scriptname}.results
does not do it.
But
echo "set SYN_Unbending = \"1\"" >> LOGS/${scriptname}.results
doesn't work either, because csh is filtering out the \".
How can we echo " into a results file?
Or, can we modify the results interpreter of 2dx_merge, so that parameters without the " can also be interpreted?
No responses can be added.
If you can, please log in before submitting a reaction.
