"[WARN] - couldn't find a match for" happens when project path contains spaces.

[snap9]

Everything was working fine, 100% when my project folder was located in ~/Desktop/site

That's where all the .scss and corresponding .css files are located. No complex directory structure. All files directly inside ~/Desktop/site

Now I rename the folder on the Desktop from "site" to "site 2" (or anything containing spaces). That's the ONLY change I make. Everything else stays the same. Now the "[WARN] - couldn't find a match for" problem starts happening. Tikana can't match the files anymore.

I'm on OS X 10.10.1.

I'm sure you can reproduce if you have access to a Mac, or maybe this also happens on Windows or Linux. I don't know. What do you think?

[timdmackey]

Just ran into this problem myself—I spent the last three hours trying to figure out why the heck takana wasn't working, and almost gave up before I finally narrowed it down to there being a space in the file path I was accessing. My guess is that Takana is failing to convert the space " " to it's url encoded value "%20" when comparing paths. Please fix this so no else wastes the amount of time that I had to!

[JulianCataldo]

Ran into the same problem too,
tried to fiddle with symbolic links (with no spaces in path) but got no luck ;(