What happens when you open a .cmd file with Notepad++ via (menu) File -> Open?
What happens when you drag & drop a .cmd file to the Notepad++ window? Please note: It seems that you run Notepad++ in Admin mode (your debug info states: Admin mode : ON). To be able to drag & drop files to the Notepad++ window it might be necessary to run Notepad++ as a normal user.
Please ensure that this failure is really caused by the AutoCodepage plugin. To do that move the folders of all your other plugins to an arbitrary location of your hard disk in order to prevent Notepad++ from loading them at startup. After that try to load a .cmd file using all possible methods (double-click, drag & drop to the window, File -> Open).
To ensure the failure isn't related to your installation please download a portable version of Notepad++ from the >>> original download site <<<. Please note: Running a portable version of Notepad++ doesn't change anything with your local installation, they are completely separated. But for this test they should not run at the same time, thus ensure that there is no running instance of Notepad++ before you start the portable version. Install the AutoCodepage plugin in the portable version and try to open a .cmd file by drag & drop to the notepad++.exe entry in an Explorer window. Try also to open it via File -> Open.
Please come back and report the results of your tests.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any variant of opening / loading a *.cmd in Notepad++ crashes Notepad++:
- File -> Open
- drag 'n drop
- command line: "notepad++.exe *.cmd"
- doubleklick on an *.cmd
- context menu "Edit with Notepad++"
Another usage sample:
Load *.cmd a) without AutoCodepage-plugin orb) with AutoCodepage-plugin and with an initial / mostly empty AutoCodepage.ini => no crash. Load a * .txt in another tab. *.txt tab is now active. Close Notepad++. Start Notepad++ with *.txt as an active Tab. Configure AutoCodepage as shown in first posting. Select Tab with *.cmd => crash
AutoCodepage-plugin as the only plugin: same behavior => crash
Admin mode or normal user mode: same behavior => crash
Portable or Desktop (installed) variant: same behavior => crash
Meanwhile tested three different PCs with the same new initial Windows 10 setup. A "some days used" user profile and PC . Two fresh PCs and a fresh, "unused" user profile: same behavior => crash
edit 15:18 syntaxupdate: added some *
Last edit: TGSF 2019-06-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems like you use the session feature of Notepad++ ((menu) Settings -> Preferences -> (register) Backup -> (check box) Remember current session for next launch). Can you confirm that?
I will set up a test environment in a VM:
Windows 10 v1709 x64 build 16299.1127
Notepad++ v7.7 x64 with Remember current session for next launch set active
AutoCodepage v1.2.3
This is a use case I haven't tested yet since I don't use the session feature.
Last edit: Andreas Heim 2019-06-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Conditions:
Windows 10 64-bit v 10.0.16299.785
Notepad++ v7.7 (64-bit)
Build time : May 19 2019 - 13:05:35
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : ON
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : AnalysePlugin.dll AutoCodepage ComparePlugin.dll
DSpellCheck.dll HTMLTag.dll JsMapParser.NppPlugin.dll JSMinNPP.dll mimeTools.dll
NppConverter.dll NppExec.dll NppExport.dll NPPJSONViewer.dll NppQrCode64.dll
NppToolBucket.dll NppXmlTreeviewPlugin.dll RunMe.dll XBrackets.dll XMLTools.dll
zoomdisabler_x64.dll
%APPDATA%\Notepad++\plugins\Config\AutoCodepage.ini
[Header]
Version=1.0
[Groups]
850er=active
[850er]
Codepage=45048
Language=12
Ext1=.CMD
Trying to start Notepad++ while opening a .cmd-file (doubleclick on a .cmd file) crashes Notepad++.
No crash on Windows 7 SP1 64-bit.
What happens when you open a .cmd file with Notepad++ via
(menu) File -> Open?What happens when you drag & drop a .cmd file to the Notepad++ window? Please note: It seems that you run Notepad++ in Admin mode (your debug info states:
Admin mode : ON). To be able to drag & drop files to the Notepad++ window it might be necessary to run Notepad++ as a normal user.Please ensure that this failure is really caused by the AutoCodepage plugin. To do that move the folders of all your other plugins to an arbitrary location of your hard disk in order to prevent Notepad++ from loading them at startup. After that try to load a .cmd file using all possible methods (double-click, drag & drop to the window,
File -> Open).To ensure the failure isn't related to your installation please download a portable version of Notepad++ from the >>> original download site <<<. Please note: Running a portable version of Notepad++ doesn't change anything with your local installation, they are completely separated. But for this test they should not run at the same time, thus ensure that there is no running instance of Notepad++ before you start the portable version. Install the AutoCodepage plugin in the portable version and try to open a .cmd file by drag & drop to the notepad++.exe entry in an Explorer window. Try also to open it via
File -> Open.Please come back and report the results of your tests.
Thank you for your quick response.
Any variant of opening / loading a *.cmd in Notepad++ crashes Notepad++:
- File -> Open
- drag 'n drop
- command line: "notepad++.exe *.cmd"
- doubleklick on an *.cmd
- context menu "Edit with Notepad++"
Another usage sample:
Load *.cmd a) without AutoCodepage-plugin orb) with AutoCodepage-plugin and with an initial / mostly empty AutoCodepage.ini => no crash. Load a * .txt in another tab. *.txt tab is now active. Close Notepad++. Start Notepad++ with *.txt as an active Tab. Configure AutoCodepage as shown in first posting. Select Tab with *.cmd => crash
AutoCodepage-plugin as the only plugin: same behavior => crash
Admin mode or normal user mode: same behavior => crash
Portable or Desktop (installed) variant: same behavior => crash
Meanwhile tested three different PCs with the same new initial Windows 10 setup. A "some days used" user profile and PC . Two fresh PCs and a fresh, "unused" user profile: same behavior => crash
edit 15:18 syntaxupdate: added some *
Last edit: TGSF 2019-06-05
Thank you for your thorough testing!
It seems like you use the session feature of Notepad++ (
(menu) Settings -> Preferences -> (register) Backup -> (check box) Remember current session for next launch). Can you confirm that?I will set up a test environment in a VM:
Remember current session for next launchset activeThis is a use case I haven't tested yet since I don't use the session feature.
Last edit: Andreas Heim 2019-06-05
@TGSF
I was able to fix the issue. You can download an updated version of the plugin's DLL file in the AutoCodepage repository.
Thank you for your bug report, much appreciated.
Last edit: Andreas Heim 2019-06-05
It works!
Thanks a lot. Version 1.2.4 doesn't crash Notepad++.
With NPP 8.7 (and before) this plugin v1.2.7 doesn't work any more. I cannot add groups. Clicking the + button does nothing.
Last edit: bege 2024-10-04
First of all, I would like to ask you to start a new thread for a new topic instead of reviving a already closed thread.
To answer your comment, you have to provide some data for the new group befor you can click the "Add" button, see here:
Last edit: Andreas Heim 2024-10-04