Notepad++ v4.2.1 comes out -> fix crash issue
Notepad++ project is moving to GitHub:
Brought to you by:
donho
Menu
▾
▴
Notepad++ v4.2.1 just cames out, you can download it here :
https://sourceforge.net/project/showfiles.php?group_id=95717&package_id=102072&release_id=532004
v4.2.1 fixes v4.2 crash issue by removing Explorer.dll from release.
In this release, a regression bug (replace in the selection bug) is fixed, as well Light Explorer is added.
Please let me know if you find any critical issue.
Don
What's the difference between vulgarity and deity then?
Thankfully I haven't seen any error messages with "questionable" language. It won't stop me from using this super app, I would just find it annoying.
Hi
There is a problem in find in files filter, indeed it is not filled with appropriate things. Some time, it is filled with path of the file, sometimes with the correct file extension but with strange character at the beginning, and often it is filled with nothing.
Thanks
Hi,
I can confirm this bug. Actually this was there in V4.2 itself and now the upgrade did not fix this. The character that was typed in the filters field is either lost and left blank around the next time or is converted to some weird character. looks like some mess up with unicode characters. Thanks.
Again, it's a regression bug.
I'll get it fixed then do another release ASAIC.
Please notice me if there's any other regression.
Don
I have problems to open *.nfo files. When i try to open it it instantly eats all the system memory so the system is unusable. Complete slowdown. I must terminate the process in process manager, this also takes some time. Same problem occurs when i try to save a document as an NFO file. With TXT files everything works fine. Other files i didn't try. This error was already present in version 4.2. I run it under XP PRO on Intel Celeron CPU with 512MB RAM.
I personally do not appreciate the use of profanity in error messages. It is EXTREMELY unprofessional.
OK, profanity? Now what an interesting idea. I actually want to see _more_ descriptive profanity in error messages!
Its better than "Error at 0x034712389761398761237686239874-3".
I guess how ever if you don't like it you could always ask for a full refund on the purchase price. ;-)
"I personally do not appreciate the use of profanity in error messages. It is EXTREMELY unprofessional."
I personally don't mind, it's kind of fun. Who cares whether the program looks unprofessional ? I enjoy the "Zyva!" button (French slang for "Go!"). Texts are merely a detail, and I'd say that bug fixes are infinitely more important than watching out not to hurt sensitive people's feelings.
** descriptive VULGARITY would be fine ** just don't invoke Deity ** :)