Notepad++ v8.4.8 Release

Bogdan Voaidas

@donho I get frequent error popups on exit now saying “Closing file wasn’t registered” for each open file. And each document starts to disappear from the list.
I reopen NPP and all documents are there still, and on exit again same errors. Downgraded to 8.4.7 and the same
I will try to uninstall everything and see after.

Bogdan Voaidas

@Bogdan-Voaidas said in Notepad++ v8.4.8 Release:

@donho I get frequent error popups on exit now saying “Closing file wasn’t registered” for each open file. And each document starts to disappear from the list.
I reopen NPP and all documents are there still, and on exit again same errors. Downgraded to 8.4.7 and the same
I will try to uninstall everything and see after.

After a fresh/clean reinstall + plugins the problem persisted.
Traced the issue to ElasticTabStops plugin.
https://github.com/mariusv-github/ElasticTabstops/issues/2

donho

@Bogdan-Voaidas
I have installed ElasticTabStops v1.50 and got the messages on unsaved files. However, all my unsaved files are kept - it seems to me an issue of ElasticTabStops, but not Notepad++'s one.

donho

@Bogdan-Voaidas said in Notepad++ v8.4.8 Release:

After upgrading to this version, all my open documents (saved and un saved) disappeared from the Document List!!!
After upgrading the Notepad++ opened in a total white state, only menus appearing and on closing it crashed with an error about an existing plugin, ElaticTabStops (a great plugin btw which since some npp versions ago was broken by it).
After deleting the plugin’s folder, NPP opened with just 2 documents in the Document List!!!

I believe it’s also your case:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/13002#issue-1562579267

S. Merk

@Karlo-F said in Notepad++ v8.4.8 Release:

There’s an error in localization\german.xml.
For a quick fix open german.xml and replace all CMID with CMDID

Again, thanks a lot for that, works perfect! But, as I had to do it on another machine again: One little hint is missing: After the replace, the language has to become switched one time in the settings. Maybe you could/should mention this in your post also.

Bogdan Voaidas

Some related question … where we can report broken plugin versions so we avoid this kind of problems and lost data?
I see this plugin (elastic tab stops) is not marked as incompatible … which is not really incompatible but definitely loosing data because of it should be treated very seriously.

donho

Another user (I guess it’s @Bogdan-Voaidas ) has reported ElasticTabstops makes data losing:
https://github.com/mariusv-github/ElasticTabstops/issues/2#issuecomment-1420414954

I’m wondering if we should block this plugin in the next version.

@Bogdan-Voaidas

Some related question … where we can report broken plugin versions so we avoid this kind of problems and lost data?
I see this plugin (elastic tab stops) is not marked as incompatible … which is not really incompatible but definitely loosing data because of it should be treated very seriously.

Obviously this plugin is out of maintenance - I will see what I could do about it.

Alan Kilborn

@donho said in Notepad++ v8.4.8 Release:

Obviously this plugin is out of maintenance

Actually, this plugin just changed hands, from @dail 's control to a new developer ( @mariusv-github) that expressed an interest in maintaining it. Maybe that new developer is not meeting expectations? (“Sorry” to the new developer if that is NOT the case…).

rdipardo

@donho, @Bogdan-Voaidas, the only problem with Elastic Tabstops is this annoying dialog that hooks the NPPN_FILEBEFORECLOSE event when the given buffer has not been added (“regist[er]ed”) to the plugin’s private list of remembered files. The code never reads from or writes to session.xml, posing zero risk to a user’s unsaved files.

It’s more likely @Bogdan-Voaidas’s session file was moved / overwritten / corrupted by N++'s installer. Lesson learned: if you’re not backing up your personal config files before every upgrade, you’re rolling the dice.

MeanUncleMonster

@donho If this is not the place to post this, I apologize. However, after upgrading from 8.4.7 to 8.4.8, I found that I was no longer able to scroll down on an open document to open up additional ‘paper’ or text area to work in, as I was able to do with every version of NP++ up until 8.4.8. Now, for some reason, when I get to the bottom of my available text area, I can no longer use the scroll wheel (or the scroll buttons on the work area) to add more open space to work in.
Was this an intentional thing in the update? I find it pretty hard to work on a text file staring at the bottom of the screen/window, personally, especially when the rest of the window is full of text. I generally like it best when I’ve got half a page of text to reference, and a half-page empty, which NP++ was one of the few editors that allowed me to do up until this update.
Besides just not upgrading past 8.4.7, is there any way to retain this feature in the later versions?

Terry R

@MeanUncleMonster said in Notepad++ v8.4.8 Release:

is there any way to retain this feature in the later versions

I think you are referring to “enable scrolling beyond last line” which is under Settings, Preferences, Editing. Just tick the box for that option. I would have thought that option would have been retained from the previous version as it seems you did have it enabled.

So the option was not removed, but in your case it may have been reset which led you to believe it was removed.

Terry

PS i just upgraded from and to the same versions as you refer to. In my situation the option was still enabled after the upgrade.