Also created a release https://github.com/chcg/NPP_HexEdit/releases/tag/0.9.5.11, but due to the unclear situation with Jens I also don’t want to hijack.

Further gitrepos:

https://github.com/search?utf8=✓&q=hexedit+notepad%2B%2B&type=

See https://sourceforge.net/projects/locationnav/files/ latest update from 2012-07-24, so long before N++ x64 version.

Added to https://github.com/bruderstein/nppPluginManager/issues/67, for x64 you could add a PR at https://github.com/bruderstein/npp-plugins-x64 to update a plugin. Zip file is required, therefore SQLinFormNpp_5.1.80.zip is the latest version found in the list.

Fixed with v0.27.1, reported e.g. as https://github.com/ashkulz/NppFTP/issues/160

Hi,

I haven’t observed such behavior, the plugin is working just fine.
Is everything OK when you open ‘Settings…’ from the plugin’s menu?

BR

@dinkumoil All I can say is, thank you. I am very happy. I didn’t know to keep the the value of the attribute “PluginEntryName” as “TextFX Characters”.

Thanks for your reply
Too bad, it was really good as “behavior”

pnedev – Your fix worked for me (x86). Thank you for doing this.

@xiaokLinux

It occurred to me that line-change markings could also be generated as a side-effect (meaning you wouldn’t have to do ANYTHING to get them) of the technique for “find dialog automation” discussed in these threads:

https://notepad-plus-plus.org/community/topic/14181/execute-n-find-in-files-via-cmdline-script
https://notepad-plus-plus.org/community/topic/14130/hide-or-toggle-find-results-panel-with-keyboard-command

It is some amount of work, but it is still all Pythonscript, which you indicated you were somewhat familiar with in your original posting.

Basically you would use code to populate the fields in Notepad++'s Find/Replace interface, then press buttons (again via code) to do searches/replacements. Because Notepad++ itself would then take over and do the actual replacements, the line-change markings (from the plugin) would occur.