What's the status of Notepad++ portability?

[sproaticus]

...Because it's writing stuff to my registry.

HKEY_CLASSES_ROOT\Notepad++_file
HKEY_CLASSES_ROOT\Notepad++_file\shell
HKEY_CLASSES_ROOT\Notepad++_file\shell\open
HKEY_CLASSES_ROOT\Notepad++_file\shell\open\command

I'm pretty sure I didn't ask it to associate any file extensions.

Curiously, there doesn't seem to be any significant changes to my HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE hives.

I'll be starting with a fresh VMWare image, but it'll take a while.

Has anyone else seen Notepad++ do this?

Jeremy

[Andrew Lee]

Yeah, I think it does that, but it doesn't register any of the file extensions until you add them under "Settings".

I suspect it is a generic placeholder written by the app that defines how Windows launches Notepad++ files. Any registered extensions will then point to this placeholder.

Don't think it affects portability, since you wouldn't use file assoications in the first place. But if you are concerned about "stealth", then it is another issue.

[Slythfox]

That can easily be fixed using an AutoIt script:

Code: Select all

Run(@ScriptDir & "\notepad++.exe", "")

 While 1
  If NOT ProcessExists("notepad++.exe") Then
   ; Delete registry entry.
   RegDelete("HKEY_CLASSES_ROOT\Notepad++_file\")
   ; Exit program.
   ExitLoop
   Exit
  EndIf
 WEnd

This will delete the registry notepad++ created after notepad++ is closed.

BTW, notepad++ (2.7) does not do this on my computer. I do have that shell option, but I can't find it in the registry.