Working with a UNIX system, I could not help the newline to be added at the end of the file - hope that is fine.
The "flanking blanks" problem I expect to also be of concern in the settings file, where I also added the quotes to make them detectable. However, since the settings' yaml is more likely to be created in a text editor rather than something exported via a spreadsheet, this should be an exception and so I decided against any warnings. And maybe the blanks are already removed while parsing the file, but some other weird barely detectable character may still sneak in, so the quotes are helpful, I think.
I preferred to have the filenames flanked by single quotes (') instead of the double (") since this is what UNIXy folks expect. I hope that is ok.
The promised patch addressing issue #106 .
Working with a UNIX system, I could not help the newline to be added at the end of the file - hope that is fine.
The "flanking blanks" problem I expect to also be of concern in the settings file, where I also added the quotes to make them detectable. However, since the settings' yaml is more likely to be created in a text editor rather than something exported via a spreadsheet, this should be an exception and so I decided against any warnings. And maybe the blanks are already removed while parsing the file, but some other weird barely detectable character may still sneak in, so the quotes are helpful, I think.
I preferred to have the filenames flanked by single quotes (') instead of the double (") since this is what UNIXy folks expect. I hope that is ok.