offer an option to keep the plugin anyway

+1

What I’ve done before to avoid this issue is you can rename your plugin. For example the installer removes DSpellCheck.dll I’ve just renamed it to DSpellCheck2.dll and it never warns me about it again :)

I did a few tests with BOM files and it seems that now “Encode in UTF-8” does remove the BOM. This makes total sense but it turned the previous logic upside down.

“I added a 32 bit plugin to 64 bit.”

That’s not going to work. The plugin must be recompiled by the author to be a 64-bit executable before it will work with 64 bit Notepad++.

The problem is the Plugin Manager itself is not 64bit. There are a few 64bit plugins currently available. @Sai-Prasanth Your best option is to just manually copy any DLLs into the plugins directory of Notepad++. Even with older versions of Notepad++ I’ve never had luck trying to use the menu to import plugins.

Looks like x64 version of npp is new? So maybe no spell check plugin available for it yet? If I need spell checking should I use 32 bit npp instead?

Sorry, I am new to npp. Not in tune with where development is at.

Beautiful piece of work though!

Use $0 instead of &.

I run Notepad++ on Linux with the help of “Wine” (originally an acronym for “Wine Is Not an Emulator”) it works great too! have used NP++ on Windows since it was new !
It’s still my favorite editor of all time.

They have downloads for Mac OS here: https://wiki.winehq.org/MacOSX

Mac OS X - WineHQ binary packages for the development and staging branches for Mac OS X 10.8 and higher

@dail Thanks! I’d Googled for the problem, but didn’t find the stuff on GitHub. That fixed it!

Hello Pavel,

Thank you for your remarkable work.
I’m sure that when you release Compare Plugin v2 many NPP users would be as appreciative and grateful as I am.

Best regards.