This reminds me
I did notice a bug in one of the file path nodes a while ago- I was in a real hurry at the time & forgot to log it as a bug. I will have a look & see if I can still reproduce it next week.
The problem was basically the the node interpreted a part of the path (from memory \t or \n or \r) as an escape (i.e line break, tab etc)
My fix at the time was to rename the folder/path so that it did not have the particular sequence.