Notepad++ v8.2.2 Release Candidate 2
Notepad++ v8.2.2 Release Candidate 2:
Notepad++ v8.2.2 RC2 regression-fix & new enhancement from Notepad++ v8.2.2 RC:
- Fix unsaved untitled files not being opened on the next session regression (Fix 11080)
Due to the performance issue, the loading of large files disables automatically the following feature:
- auto-completion (only for large files)
- snapshot periode backup (only for large files)
- backup on save (only for large files)
- word wrap (persistent for all files. Need to re-enable it manually)
Any suggestion is welcome.
Please let me know if you find crash / regression / critical issue / performance issue.
The new version works much better.
On my machine, it took ~15 seconds to open a 2.2 GB text file and editing went smoothly until I entered a round closing bracket
This seems to trigger something special, as it takes a few seconds for Npp to respond again. I have not found any other asscii character that behaves this way. Any ideas what could be causing this?
I have not done any configuration. I downloaded the portable version, opened the file, jumped to the end and started editing.
Now we have fixed another big issue, so there will be another RC for sure.
I think that e.g. the auto-completion feature will work even with the 2GB+ files in the future. Or we can extend the current syntax styling limit (200MB).
As Don stated, the changes in the Notepad++ codebase are huge, so you have to be patient, if there will be temporarily some troubles or not fully functional things you are accustomed to use. Don is doing great job there.
Don’t misunderstand, I’m just a tester here and extremely grateful for what all the developers have done and are still doing for Npp. The report was just my humble contribution to this.
The probability that I currently have to work with such large files is close to 0%.
👍 Keep up the good work.
a round closing bracket ).
This seems to trigger something special, as it takes a few seconds for Npp to respond again
)thing be “bad bracket checking” or is that a Lexer component not enabled in large files. My first thought was auto-inserting the closing bracket, but this was the closing bracket itself.
I - like @Ekopalypse am just a happy tester always getting the latest AppVeyor commit build to use in my daily work (mainly Python coding, XML and JSON file manipulation). Very rarely “large” files and by large I’m still talking < 10Mb so any changes have kept my base case rather stable to your all’s credit!
In 8.2.2 RC3 the edit performance issue should be improved. Please try here: