Correct.
On Tue, Jun 18, 2013 at 1:26 PM, Tor <tor.viktors...@gmail.com> wrote: > Yes, it works now. I did an entirely new build from scratch using the > instructions in the README and it worked flawlessly this time. > > I also agree that my path problem is in the domain of Node.js knowledge > since the error I got manifested itself in the node-gyp build tool which is > native to Node.js yes? > > / Tor > > > On Tuesday, June 18, 2013 11:33:18 AM UTC+2, Tim Wienk wrote: > >> Firstly, thanks again for trying things out and reporting the problems. >> >> Regarding the Python problem, I guess setting up Python (or NodeJS for >> that matter) correctly is a bit out of scope for the MooTools Website >> project, but perhaps a note would be in order. The "PATH" environment >> variable is generally a list of directories in which to find >> executables, so adding just the directory should do it, but I'm not >> too experienced with developing on Windows anyway. >> >> Regarding the splitMarkdownMetaData.js, could you try if it works >> unchanged now? The regular expression is changed slightly, if it works >> on Windows systems now without adding an explicit carriage return >> check, that'd be nice. >> >> Cheers, >> >> Tim. >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "MooTools Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mootools-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mootools-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
