Failed to Open Init File/Eager Command Line Parsing
surrealwaffle opened this issue · 1 comments
surrealwaffle commented
chimera does not reproduce Halo's behavior when reading the argument supplied for the -exec switch.
For instance, when supplying -exec "init.txt"
, chimera will attempt to load the file "init.txt", double quotes included. Furthermore, -exec "in it.txt"
will result in loading the file "in, double quote included.
This isn't exactly a major issue; simply avoid whitespace in your init file paths and do not supply those paths in quotes.
SnowyMouse commented
Thank you for bringing this to my attention.
Fixed in 84b8f25