You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason that I fail to understand, in some cases, Windows loads some .dlls in PATH directories instead of in the directory of the executable. And this can cause a myriad of problems (if those .dll are of different versions of the lib which are in the bundle, ...). One workaround is simply to set an empty PATH before running liam2/main.exe
This can be done via cmd:
cmd /c "set PATH=; && "$(NPP_DIRECTORY)\..\..\..\liam2\main" run "$(FULL_CURRENT_PATH)" -i"
It might also be doable via nppexec "ENV_SET" command.
For some reason that I fail to understand, in some cases, Windows loads some .dlls in PATH directories instead of in the directory of the executable. And this can cause a myriad of problems (if those .dll are of different versions of the lib which are in the bundle, ...). One workaround is simply to set an empty PATH before running liam2/main.exe
This can be done via cmd:
It might also be doable via nppexec "ENV_SET" command.
See section 4.2 at:
http://www.cin.ufpe.br/~aedv/Notepad++Portable/App/Notepad++_ansi/plugins/doc/NppExec_Manual.txt
The text was updated successfully, but these errors were encountered: