Notepad++ raises an error when closed
-
@Meta-Chuh
Thank you very much for the quick response.I followed the steps, this is what I observed:
- Running and closing the portable version didn’t raise the error message.
- Running and closing my version with
-noPlugin
made the error message go away, too.
This is the debug info I got from my version:
Notepad++ v7.6.4 (32-bit) Build time : Mar 6 2019 - 02:52:22 Path : C:\Users\bolandross\Documents\Programme\NotePad++\notepad++.exe Admin mode : OFF Local Conf mode : ON OS : Windows 10 (64-bit) Plugins : DSpellCheck.dll EmmetNPP.dll HTMLTag_unicode.dll mimeTools.dll NppConverter.dll NppExport.dll PreviewHTML.dll PyNPP.dll PythonScript.dll Tidy2.dll WebEdit.dll XMLTools.dll
Best regards
-
So it is very likely a plugin causing the problem, I suppose. If I were you I would try removing the spell check one and repeat the test.
-
@Alan-Kilborn said:
So it is very likely a plugin causing the problem, I suppose. If I were you I would try removing the spell check one and repeat the test.
You were right, removing DSpellCheck from the plugin folder, solved the problem.
How did you know?
And how can I debug the plugin further?
-
-
Hello, @bolandross, and All,
So, now, the goal is : which version of DSpellCheck are you using ?
Presently, the latest release is the
v1.4.11.0
versionIf necessary, download this latest version from below :
https://github.com/Predelnik/DSpellCheck/releases
Best Regards,
guy038
-
@guy038
Recently dspellcheck can not download and install spelling dictionaries, only manual installation of dictionaries. -
yes, you are absolutely correct.
currently you have to disableshow only recognized ones
to be able to download dictionaries.see here for the complete guide: https://notepad-plus-plus.org/community/topic/17416/spell-check
-
@Meta-Chuh
That’s how it works!
But what is the reason for this error? -
i do not know yet.
i did not search for this at the dspellcheck project or google yet, due to lack of time.
but maybe @Predelnik could help ? -
@guy038
Hey, thanks for the suggestions!I was using
v1.4.10.0
and updated tov1.4.11.0
, but unfortunately the problem stayed.