I tried installing Python v3.0.24 msi, and zip Full, but I don’t see it anywhere in the Plugins section. Initially, I installed 2.1. I uninstalled it and tried installing v3.0.24, but 2.1 is still there.

What am I doing wrong?

Since you just gave a high-level description, rather than any actual data, it’s really hard to tell.

I uninstalled it and tried installing v3.0.24, but 2.1 is still there.

Then you didn’t uninstall it. Please note that under many conditions, the Plugins Admin uninstall button doesn’t work if Notepad++ has accessed the PythonScript plugin at all that run, because it’s loaded the DLL into memory, and thus cannot delete the file – so if you have any AT START, that virtually guarantees that uninstall button won’t work. (I believe there was an Issue or PR to try to make uinstall button more reliable, but I don’t remember whether that was implemented, or whether it was even feasible.) So, anyway, your best bet is to exit Notepad++ completely, and delete C:\Program Files\Notepad++\plugins\PythonScript\.

P.S. I didn’t try any of the v3.0.24 x64, PluginAdmin, Min, or TclTk.

You didn’t try the 64-bit version of PythonScript? The last time you shared Debug Info (and the time before that) you were using 64-bit Notepad++. So why would you try anything but 64-bit PythonScript. It is 100% guaranteed that it will not work if you try to use the 32-bit PythonScript with a 64-bit Notepad++.

If you ran the 32-bit MSI on a 64-bit OS, it would have tried to install the plugin into C:\Program Files (x86)\Notepad++\Plugins\PythonScript , which, of course, couldn’t be seen if you are running the 64-bit Notepad++ executable at C:\Program Files\Notepad++\notepad++.exe .

If you tried one of the zips, you didn’t say where you put it, or what the directory hierarchy would have been. But if you were still seeing PythonScript 2.1 in Notepad++, it means you didn’t put it in the right place. And I have no clue where you would have put it.

So the things you will need to do:

Run Notepad++ as normal, and verify with Debug Info that you are using 64-bit, and that it is running from c:\Program Files\Notepad++ . If you don’t get it working after these instructions, you must share your Debug Info, otherwise it will be impossible to give you better instructions. The rest of these instructions will assume normal installation directory, normal 64-bit Notepad++ Exit Notepad+++ completely. No instances running. Go to C:\Program Files\Notepad++\plugins\PythonScript\ . If there’s anything in there, remove it (and the directory) Grab PythonScript_Full_3.0.24.0_x64_PluginAdmin.zip (I don’t use the MSI, so cannot give reliable instructions for that MSI installation method). Unzip it so that the following exist: C:\Program Files\Notepad++\plugins\PythonScript\PythonScript.dll C:\Program Files\Notepad++\plugins\PythonScript\python312.dll C:\Program Files\Notepad++\plugins\PythonScript\doc\ C:\Program Files\Notepad++\plugins\PythonScript\lib\ C:\Program Files\Notepad++\plugins\PythonScript\scripts\
If those aren’t all there, you didn’t unzip things correctly. Start Notepad++. It should show PythonScript in the Plugins menu, and Plugins > Python Script > About should show plugin version 3.0.24.0 with Python 3.12.0
3ba2f6f7-5bfc-4a38-9546-9bfbe945a8eb-image.png

If it’s not working for you after following those instructions, you must share

?-menu’s Debug Info dir "c:\Program Files\Notepad++" dir "c:\Program Files\Notepad++\Plugins" dir "c:\Program Files\Notepad++\Plugins\PythonScript"

@Evelyn-Walker ,

I tested the behavior you described. In Notepad++ the Ctrl+L (Delete Line) command

That is wrong terminology, as already described above. Ctrl+L is Line Cut, not Line Delete. To use the wrong terms causes confusion for everyone. From the OP, it was acceptible, because they didn’t know better. But to post like you are an authority, but to use the incorrect terminology, is detrimental to yourself and anyone who reads the answers here.

internally performs a cut-like operation,

Of course it does. It’s literally Line Cut, so it definitionally affects the clipboard

which means the deleted line is temporarily placed into the clipboard.

It’s no more “temporarily” on the clipboard than any Ctrl+C or Ctrl+X is “temporarily” in the clipboard. It’s in the clipboard until something else replaces it, just like every other clipboard action.

Use Ctrl+Shift+L (if configured) or another plugin/command that deletes the line without copying it.

Did you come up with that alternative all on your own, or did you just reiterate what @guy038 and I had already said?

Alternatively, copy the text again after performing line deletions if you still need it in the clipboard.

That’s horrible advice.

If preserving clipboard content during line deletion is important, it could be considered as a feature request rather than a bug.

No it couldn’t, because the feature already exists. Line Delete already exists as Ctrl+Shift+L: use Line Delete if you don’t want to affect the clipboard, and Line Cut if you do want to affect the clipboard.

@Evelyn-Walker , make sure you are not using LLM or GPT or any other AI to write your posts for you: that’s expressly forbidden in this forum.

Hi Harmandeep,

Welcome to the community.

Yes, there is a good chance you may still be able to recover your unsaved work. Notepad++ has a built-in backup and session snapshot feature that often restores files after a crash.

First, try reopening Notepad++. If the session snapshot feature was enabled, the file may reopen automatically with the content you were working on before the crash.

You can also check the backup folder manually. Go to:
C:\Users\YourUsername\AppData\Roaming\Notepad++\backup
Sometimes Notepad++ stores temporary backup files there, which may contain the unsaved content.

To reduce the risk of losing data in the future, it’s a good idea to enable a few settings:

Open Settings → Preferences → Backup. Enable Session snapshot and periodic backup. Choose Remember current session for next launch. Set a backup interval such as every 7 or 10 seconds.

With these options enabled, Notepad++ will automatically save temporary snapshots of your work and restore them if the program closes unexpectedly.

Hopefully your file is still in the backup folder. Let us know if you need help locating it.

Regards.