-
Notifications
You must be signed in to change notification settings - Fork 34
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
Notepad++'s Plugin Manager fails to install #80
Comments
Dictionaries for Aspell for windows are separate installers. You can Best regards, Sergey Semushin On Wed, Jun 29, 2016 at 12:08 AM, Andova Begarin [email protected]
|
Thank you very much. Turns out I had done something wrong: Installed the Aspell program but not the dictionary. Doing the latter fixed it. (Still, Plugin Manager does not install DSpellCheck. Works fine with manual install.) |
@AndovaBegarin Do you still have a problem in installing DSpellCheck with PluginManager https://github.com/bruderstein/nppPluginManager/releases/tag/v1.4.9 ? I don't see such an issue. |
I had some trouble with installing on Windows XP machine. Maybe that's the case? For me it was probably caused by the fact that maybe Windows XP needs something additional to support downloading through https. But almost any plugin now is on https so probably it should be resolved on a client side. |
See bruderstein/nppPluginManager#40. PM depends on the windows ssl/tls implementation and that one is not updated to support TLS 1.1, what causes issues with current https servers enforcing the usage of the more secure protocols. |
Ok I think it's sad but it's most likely Plugin Manager/Windows XP interaction problem, so I'm closing this for now, feel free to reopen if my guess was incorrect. @chcg thanks for the link! |
Trying to install this from Notepad++'s Plugin Manager fails (v6.9.1). Not certain why. Manually downloading:
and extracting the DLL seems to work. But I get the error:
Even though:
exists as I did install Aspell.
(I must be doing something wrong...)
The text was updated successfully, but these errors were encountered: