-
Notifications
You must be signed in to change notification settings - Fork 0
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
Interest #2
Comments
Thank you! I'm getting more and more motivated to actually polish the package and make it useful for others :) I'm currently using it almost exclusively for jumping to files in projects - it already 100% replaced If you plan to try it out anyway, please be careful: although I haven't seen it for some time, it's still possible for the module to cause a segfault and a hard crash of the whole Emacs. Also, don't recompile the module while it's loaded into running Emacs: I got a few crashes before I realized this. So, if you change the Nim code, close Emacs before recompiling. I'll update the README with a warning about that later. Also, remember to please let me know about any problems you might have while trying to make it work on your system! I don't have that much experience with native DLLs, so I expect there's a lot to improve in terms of building and configuring the package. |
I cleaned up the |
Couldn't work on this last week due to falling ill a bit, but there's progress today. I rewrote the helpers for calling Emacs API from Nim templates to macros, which allowed me to hide the need for passing around the |
Nice, I had a chance to try it on OSX and building fails (readme says it's linux only but I thought I'd try on OSX).
|
Oh, that's interesting. I don't have a macOS available at the moment, but I know Nim should be able to compile dylibs on it (as well as dlls on Windows), so in theory, it should be possible to make it work. I've had a similar problem on Linux once ("previous implicit declaration", etc.), though I don't remember exactly what it was about. I'll look into it and ask around for hints on the Nim forum. |
Indeed really interesting, trying it out now! |
Thanks @Trisk3lion, I'll add a note to the README about requiring Nim 1.4. I'm not sure if we really need it, but I was getting some mysterious crashes while using the default GC which went away after switching to ARC. The performance is also better, and I don't have any cycles in the data, so there are no demerits for using it, other than needing the latest Nim. As for the status update this time: I just implemented proper interop with Elisp signals and throws (they're translated to Nim exceptions and back). I will need to add a few more helpers for getting and decomposing values from the Emacs side ( It's going a bit slower now that I'm back at work, but there's good progress. I want to focus on moving the config to the Emacs side, then on returning the full |
I moved most of the configuration to the Elisp side. I found a nice trick for implementing Next: a bit of a cleanup, then returning full Everything works for me, but I did a bit of refactoring to implement this, so the code could be potentially less stable for a while. Should be back to rock-solid after the next round of cleanups. |
Just commenting and throwing my interest out there. This looks really cool and I'll definitely be trying this soon.
Good luck!
The text was updated successfully, but these errors were encountered: