@ว-รภ-ทร-ทว-ทร-พย said in The official repository, download.notepad-plus-plus.org, is down!:

@PeterJones This means historical releases of NPP will also be lost forever? Is there any plan to put them back online somewhere?

GitHub releases for Notepad++ goes back as far as version 6.7.9, released on Jun 11, 2015. If you’re prepared to build from source, the tags on GitHub go back as far as v4.2.1, committed on August 13th, 2007.

I tried to find older versions from the SourceForge days on web.archive.org, but it looks like they didn’t archive the actual binaries, just the index page.

@PeterJones Thank you.

@jpatterson-ATL said in Unsaved?:

But, as a general rule, are you saying that if I didn’t manually save the file, that the cached changes just disappeared when I made the save choice, whatever that was?

See our periodic backup FAQ. Essentially: Notepad++ believed you when you gave it the answer. The “session snapshot and periodic backup” feature was never meant as a long-term backup (there’s the backup-on-save option for that), but as a “try to protect me, if you can, if something goes wrong on the computer between my reasonable-duration saves” feature.

The notes.txt file is stored in OneDrive but the file version history shows the newest date to be over a year ago.

It boggles my mind that you would have a named file that you cared about, and not noticed that it hadn’t saved to the OneDrive in more than a year. And not noticed that the icon on the tabbar had been saying “unsaved changes” for all that time. And that you can go that long without ever thinking about hitting Ctrl+S or clicking the Save menu or toolbar button.

Given your habit, I would highly suggest installing and configuring the AutoSave plugin, so that you don’t lose data again in the future. How to set up that plugin is described in detail in the FAQ.

@LaMar-M said in Modleine Parser No Longer Works:

I’ve been using “ModelineParser_0.2” for several years to automatically select the language. This parser is still available here.

Yes. But it hasn’t been updated in 13 years. Notepad++, on the other hand, releases a new version about once a month.

Recently my NP++ version got auto updated (by IT) to version Notepad++ v8.7.4.

Your IT department chose a version from 14 months ago? It will still be missing security updates found in more recent Notepad++ versions.

But yes, in the intervening 13 years, Notepad++ has made multiple changes to the documented interface for communication between a plugin and Notepad++. There have been some changes that were known to break older/unsupported plugins. But Notepad++ cannot stop all progress just because there are legacy plugins still published out there.

When I open a program that used to default to a specific language, no language is set. I have to manually set it.

Fortunately, the NppFileSettings plugin has modeline support, including recognizing filetype, ft, syntax, and syn for setting which syntax highlighting lexer to use. And its Releases page has 32bit and 64bit downloads, so it will work in your 32-bit edition of Notepad++.

(And also, if you have a consistent filenaming convention with extensions that match the filetype, you can just set the User ext: box in the appropriate language(s) in the Style Configurator to make Notepad++ recognize the file type by extension, rather than by modeline. But if you need modeline support, hopefully NppFileSettings will work for you.)

Notepad++ v8.7.4 (32-bit)

In the modern world, where Windows OS is only maintained in 64-bit, there is virtually no reason to use 32-bit applications. For Notepad++, the only good reason for 32-bit instead of 64-bit is because you have a legacy plugin that only comes in 32-bit, that has no 64-bit version or alternative plugin with the same features.

Looking at your other non-default plugins:

CSVLint (0.4.6.7) PythonScript (0.9.2)

Both of those come in 64-bit versions now.

And PythonScript’s latest official release is up to v2.1.0, which uses Python 2.7.18, with significant bugfixes and feature improvements in both the plugin itself, and in the underlying Python interpreter (interpreter 2.7.1 from plugin 0.9.2, vs interpreter 2.7.18 from plugin 2.1.0). (Given your IT department’s apparent reticence to upgrade, I am not going to suggest moving to the “alpha” version of PythonScript 3.0.24, which uses Python interpreter 3.12.10, even though unless you use a lot of non-unicode files, I personally recommend using the version of the plugin that uses a modern Python interpreter rather than an interpreter that’s past its end of life.)

And assuming that NppFileSettings plugin works as a replacement for the unsupported and incompatible modelineparser plugin for you, then all three of the non-preinstalled plugins that you have shown an interest in will work with 64-bit Notepad++ as well.

As such, if you can confirm that PythonScript v2.1.0 and NppFileSettings will work for you, then I highly recommend that you talk with your IT:

Ask if they can switch to 64-bit Notepad++. Ask if they will support a newer Notepad++. I desparately want to recommend the newest version, because of all the recent security fixes, but if you use UDL, then v8.9.2 probably won’t work for you, so you might have to stick with v8.9.1 until the regression fix for UDL is released in v8.9.3 (hopefully soon)

@PeterJones Thank you so much. It is looking MUCH better now.

@PeterJones Thank you so much for the detailed explanation! 🤗
I understand now why it behaves differently than before and can totally relate.
Keep up the great work! 👍

btw, i am simply using the superbly integrated ‘Read-Only’ functionaility! So I get the the safety AND convenience (no restart required).

All the best.

@mr10008 ,

That’s weird. I know that last year, while Notepad++ and it’s associated installer and DLLs were self-signed, some AntiVirus software would pause/halt the installation. But that should have been fixed last year when Notepad++ moved to the new GlobalSign signature.

My only thought is that for whatever reason, NppShell.dll is being write-protected while the rest of the installled executable and DLL and config files are not… which makes no sense to me, but maybe. If so, then I wonder if your taskbar shows the UAC icon (2cdfa78e-bc0a-422e-b8f3-6fa8e28f46fc-image.png) – if so, if you click on it, then Windows can ask you permission to let Notepad++ finish installing.

I am doubtful it’s the UAC, however, so I had been hoping that @xomx would chime in by now, in case he had other ideas for a solution, or questions that he can ask for clarification (as he’s really good at issues with the installer).

@harmansinghdeepkandhari:

When you install through Plugins Admin, Notepad++ verifies that the hash of the downloaded zip file containing the plugin matches the hash that was supplied when the plugin was added to or updated in the plugins list.

That is all that is done. Aside from the three plugins included with Notepad++ (MIME Tools, Converter and NppExport), the author/maintainer of Notepad++ does not vet plugins.

Realistically, he could not do that comprehensively. And — in my opinion, wisely — he does not make a halfway, superficial attempt (like running them through a “virus checker”) which would only give a false sense of security and open up the project to claims that it didn’t do “enough.”

Further, it should be understood that plugins in Notepad++ are fully capable of doing anything Notepad++ itself can do. They are C++ programs (or the equivalent) running in the same security context as Notepad++. The architecture is very flexible, but it presumes one only installs plugins worthy of trust.

The user (or system administrator, in a managed system) is completely responsible for establishing the suitability of Notepad++ plugins (just as the same responsibility applies regarding Notepad++ itself). Nearly all are open source; you can examine the code, the issues, and so on. You cannot assume that inclusion in the plugins list means any plugin is “safe”; your own due diligence is required.