-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows support #66
Comments
Thanks, @joinr. In few days, we will share an initial version of Notespace v4, and it will be interesting to check if the problem persists there. |
https://github.com/scicloj/notespace/blob/master/src/scicloj/notespace/v4/watch.clj#L6 fails on windows since sun.nio.fs.UnixPath doesn't exist. examining the usage to determine a portable way to do this; can't load at all. ;;scicloj.notespace.v4.path/real-path returns nil for temp files, which are picked up by the regex. ;;this prevents us from picking up emacs tempfiles which error out ;;watch imports a unix-specific class, when a portable interface would work fine.. The JS side is still jacked up with the same earlier error, TypeError: ca is null (slew of minified gibberish elided). |
Tried installing my own checked out version of gorilla-notes with |
I think WSL dodges the issue though (that can be fixed using my little patch though). fwiw it looks like there may have been a similar issue in clerk, but that seems to work fine. I may try the shadow-cljs variant as well. |
@joinr Thanks for the clerk tip. Switching my project to that. Hope notespace resolves this issue. |
Given:
and a dependency on [scicloj/notespace "3-beta9"]
, evaluating (notespace.api/init-with-browser) gives me:
(notespace.api/eval-this-notespace ) leaders to an error in the JS on the browser side and a blank page.
Invoking (listen) yields a similar error in gorilla-notes js:
TypeError: ca is null (slew of minified gibberish elided).
I have no idea where to start trying to debug this, but am interested in getting it working for some recent tutorials I would like to develop. As I recall, gorilla had issues with windows before (I remember talking with the lead like a year ago, trying to get stuff working). Seems like this is a transitive issue with gorilla maybe.
The text was updated successfully, but these errors were encountered: