This pull request addresses Issue #37
Obviously it is customary to run CoffeeScript under Node.js. For Windows users, it is common to compile Node.js with Cygwin in order to use CoffeeScript. However, Cygwin expects it's own style of absolute paths (prefixed with /cygdrive/C), which of course expand-file-name does not expand to. Given these restrictions, at the present time coffee-mode's file compilation functionality does not work on Windows.
I've implemented three things:
Finally, I tweaked coffee-command-compile to leverage these settings when the system-type is windows-nt.
Without these changes, this mode's file compilation functionality does not work on Windows for the "canonical" setup of CoffeeScript on Node.js.
Add support for Cygwin-style absolute paths, which makes using the fi…
…le compilation feature of CoffeeScript mode possible on Windows systems where Node.js is compiled with Cygwin
Create function to encapsulate logic of supporting Cygwin-based Windo…
…ws paths, use in coffee-command-compile
Second commit encapsulates the system check and Cygwin path support in a single function, coffee-universal-path. Returns the regular expanded file name for all other systems, like this mode already does.