| Anonymous | Login | 2026-02-17 18:16 CST | ![]() |
| My View | View Issues |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0000340 | Rosetta | [All Projects] Input Handling | public | 2014-06-23 12:11 | 2014-06-23 12:11 | ||||||||
| Reporter | rmoretti | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | new | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | |||||||||||||
| Fixed in Version | |||||||||||||
| Summary | 0000340: Printing of commandline removes quotes | ||||||||||||
| Description | If you provide a quoted commandline variable to Rosetta (for example, you use the property of -s that will concatenated PDB files), when it's printed in the log file it will become unquoted. E.g. the command: score_jd2.linuxgccrelease -s "protein.pdb ligand.pdb" Will be printed as core.init: command: score_jd2.linuxgccrelease -s protein.pdb ligand.pdb in the log file. The commands with and without quotes have very different behaviors. | ||||||||||||
| Additional Information | When printing, we should probably check for things like spaces, and if present add quotes to make things copy-pastable. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Application(s) Affected | any | ||||||||||||
| Command Line Used | many | ||||||||||||
| Developer Options | |||||||||||||
| Fixed in SVN Version | |||||||||||||
| Attached Files | |||||||||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2014-06-23 12:11 | rmoretti | New Issue | |
| Copyright © 2000 - 2012 MantisBT Group |