-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Using forge in Windows breaks magit #84
Comments
Windows is supported. The Windows issue you have linked to is unrelated. That issue prevents the use of the mysql and psql backends on Window but Forge uses the sqlite backend. The error message provided by Emacsql seems quite clear:
You need to install a C compiler. I don't know how that is done on Windows. Maybe you could figure that out and then open a pull-request to add instructions to the Emacsql documentation to make it easier for others? |
I'll try to figure that out. Thanks for clarifying. |
Also, something off topic - I should say that I simply admire your work. Magit really changed the way I use git and I cannot work without it anymore. Thank you for this amazing piece software. |
magit/emacsql#46 seems to explain this issue, so there's nothing to do here. |
Sorry for reopening, but I encountered another issue. I gave up on setting up EmacsSQL on Windows and decided that it's okay not to use forge there. When a forge command is called when no sqlite binary is prsent it's aborted with The problem is that once forge is loaded, magit becomes unusable. Trying to get into I understand that the errors comes from one of forge's dependencies, but is it possible to make it so that it won't propagate into |
Fixed in 8ab946a |
Here is my configuration:
https://github.com/drrlvn/.emacs.d/blob/master/init.el#L792
It works well in macOS and Linux.
When running it in Windows, whenever I call
magit-status
an empty buffer opens and*Messages*
shows:It seems to be explained here. I'd understand if supporting Windows is too much of an effort, but perhaps it should be documented in the README if so.
The text was updated successfully, but these errors were encountered: