-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Plugin seems not to work with Logseq 0.10.2 #48
Comments
0.10.2 not working, 0.10.1 works for me. Windows 10. P.s. would be nice feature if you could add checkbox to plugin settings for when you press Ctrl + S to commit, that it either push or dont push to remote. Sometimes i dont want to push to remote, and just work locally but it always gives me error when i Ctrl + S that it has no remote to push to and its annoying. Plugin works great, thank you! |
The Developer Tools console contains the following message when the plugin is enabled in 0.10.2:
It is also worth noting that the inbuilt Logseq auto-commit functionality doesn't seem to be working in 0.10.2. I rolled back to 0.10.1 and the Git functionality is working again. This "Plugin API" enhancement may be a factor? logseq/logseq#10399 |
same . windows 11, logseq 10.2 . Last commit from the author of this plugin was 5 month ago. Maybe some alternatives, except 101 ? |
even 10.3 version. When i press ctrl+S - red bot brgins to blink, but nothing happens |
Same here; Logseq 0.10.3 on Windows 11 |
Same issue; Logseq 0.10.3; Win 10 |
Same here; Logseq 0.10.3; macOS Sonoma 14.2.1(23C71) |
A quick patch PR for the latest Logseq release #50 |
🎉 This issue has been resolved in version 1.5.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
confirming, it works on 0.10.3 windows 10, thank you |
Just updated Logseq to v0.10.2 (Ubuntu - Logseq-linux-x64-0.10.2.appimage) and:
Uninstalled, restarted Logseq, re-installed and still non functional.
Switched back to v.0.9.19 version of Logseq and it functions as expected again.
The text was updated successfully, but these errors were encountered: