Notepad++ 7.5.4 release
-
According to this github issue and this forum post it seems to only effect Windows XP systems. It seems once Notepad++ was moved to VS2015 is when the problem started to occur.
-
@donho said:
It’s in progress. I cannot estimate the date of shipping this feature, but I guess I need one or 2 months more.
That’s precise enough for me. Thanks so much for this awesome editor! :)
-
I found one bug (7.5.4 release). its in Language/define your language/ and there if i click to Export, it wants to open file… and also if i click to import, it enable me to save file. So these two buttons have interchangeabled functions or names. (sorry for my english)
-
Import and Export work fine for me. What localization are you using? Maybe the two got translated incorrectly.
-
another user reported this as well
Cheers
Claudia -
Completely missed that :) Seems like we had the same idea in mind as to what the problem might be.
-
-
@dail said:
According to this github issue and this forum post it seems to only effect Windows XP systems. It seems once Notepad++ was moved to VS2015 is when the problem started to occur.
Could be - since VS2015 don’t use the same runtime dll as VS2013’s ones.
However xp’s support has been dropped by Microsoft since long time, and I have no xp anymore, we will drop also the xp support. -
sorry for delay, I didn’t get the notification…
I was completly wrong, access time doesn’t matter in my problem (it changes after file status auto-detection).
I’m on Windows 7 / 10 and files on a debian machine, it’s something related to network samba shares, since I can’t reproduce with local files.
On network I reproduce in this way:
- open a file
- change and save it
- leave (blur) n++ window
- wait 10 seconds
- focus n++ window
- change alert shown
I’ll update this thread as soon I find more details.
-
Just for information, I’m strongly against dropping Windows XP support. Notepad++ is not Microsoft to do such bad things.
-
Hello, @don-ho,
Did you see that post :
It seems that @vitaliy-dovgan found out a solution, regarding VS2015 and the auto-detection problem, in XP
Cheers,
guy038
-
@Vitaliy-Dovgan & @guy038, are you serious? You want an OS full of unpatched security holes to receive continued support from N++?
Sorry, if that sounds harsh, but: are you out of your mind?
It’s about time that this mess of an OS finally dies - the sooner the better.
-
@Eagle3386,
Another text editor, which has some plugins developed by me, does support ReactOS, Windows XP, Windows 2000 and even WIndows 98 (and yes, we did hear from people who were still using it - I mean, Windows 98!). Modern or not, there are still a lot of people on Windows XP, for whatever reason. (Just an example, just think about people who are using 10-20 year old PC or notebook.)
I think it answers your question. -
ALL:
This seems to be the FINAL word on it, in case you missed it above:
@donho said:
I have no xp anymore, we will drop also the xp support.
It would be nice if there was some sort of statement like:
The latest version of Notepad++ that is known to fully support Windows XP is version number (fill-in-the-blank). If you use XP and want to use Notepad++, please use that version.
Unfortunately, I lack the interest to research a good answer for the fill-in-the-blank part. :-D
This should become the standard response to bug reports with ? (menu) -> Debug Info… -> OS : WIndows XP
-
Hello @eagle3386,
You say : You want an OS full of unpatched security holes
I’m not contesting that fact, and with the use of modern applications in order to surf on many many sites, to get messages and attached files from any source, I agree that recent OS, with a good anti-virus program, are technically more robust and protect the general integrity of our computers !
But, honestly, regarding my general behaviour to explore the WWW ( technical and standard sites, principally, without Facebook and Twitter account ! ) I’ve never been annoyed, yet, with viruses or security problems ;-)) More over, N++, whatever the version used, very rarely crashed, and, up to now, I never lost data ( except, sometimes, when hitting the Shift + Delete shortcut too quickly => NO backup in the Trash ! )
I’ve just liked, for numerous years, by now, to use Win XP, without the UAC restrictions and user rights problems or other similar goodies, which make things more complex that they should be !
However, I’m not ignorant about modern OS ! At work, we build, repair and manage Win7 configurations. My wife has a Win8.1 laptop and my two children have, both, a Win10 laptop. It’s just that I really like that “old good fellow” ( a NEC Versa 350, with Win XP SP3, though rather slow with its 1Gb of RAM, only ! )
Don’t be mistaken ! It’s a problem of money and I just can go out home and afford, myself, a Win10 laptop, these next days ! And I probably will, in a reasonable future. But I’m sure that I will think about this antiquity, with some nostalgia ( and also for an other simple reason : it would have been my laptop when I was young !! )
Best Regards,
guy038
-
7.5.1 build with platform sdk v120_xp was the last version supporting winxp. Also newer version are build with v140_xp they suffer from the problem with _stat() is not working as expected on win xp.
-
Open files with drag and drop don’t working in win10 64bits version :/
-
@Vitaliy-Dovgan said:
Another text editor, which has some plugins developed by me, does support ReactOS, Windows XP, Windows 2000 and even WIndows 98 (and yes, we did hear from people who were still using it - I mean, Windows 98!).
I don’t care about other text editors and their supported OS - and I’m pretty sure, @donho thinks the same.
Additionally — and I’m definitely not alone on this — there’s N++ and that’s it. If there’s ever something N++ can’t do, either search for a plugin or do it in another way. Having more than 1 tool for a task on any of my machines goes beyond my imagination.
Sure, there were several N++ alternatives back in the days, but none of them offered such a rich feature set with such a comfortable workflow like N++ (still) does. N++ is pretty much “VIM on Windows”.@Vitaliy-Dovgan said:
Modern or not, there are still a lot of people on Windows XP, for whatever reason. (Just an example, just think about people who are using 10-20 year old PC or notebook.)
I think it answers your question.Hardware that old will, sooner or later, die. Hence, I refuse to understand people clinging to such devices and/or software for nostalgic reasons.
(Software) development is about progression (read: fix bugs, enhance or even add features), not “install once, use indefinitely”.@Eagle3386 said:
Therefore I remain with my previous statement:It’s about time that this mess of an OS finally dies - the sooner the better.
-
@guy038 said:
[…] But, honestly, regarding my general behaviour to explore the WWW […] I’ve never been annoyed, yet, with viruses or security problems ;-)) […]
It’s not about getting “annoyed”, like you say. It’s about supporting some guys clinging to “the old days”, refusing to adapt - look out your window, nature always did (and hopefully always will) deal in one simple way: adapt or die, period.
@guy038 said:
I’ve just liked, for numerous years, by now, to use Win XP, without the UAC restrictions and user rights problems or other similar goodies, which make things more complex that they should be !
Seriously? Stating UAC and user rights are “problems” and “make things more complex” shows three things:
- You neither understand user permissions nor machine/user security — at all!
- You’ve probably never used any *nix-based OS.
- I’m wasting my time, trying to explain benefits to people only reading/seeing drawbacks when it comes to Microsoft’s most overdue action ever taken: implementing usable user account control in Windows prior to Windows 7 (I consider Vista as “Alpha-Windows 7”).
@guy038 said:
[…] It’s just that I really like that “old good fellow” ( a NEC Versa 350, with Win XP SP3, though rather slow with its 1Gb of RAM, only ! )
As stated above, I realize that I’m wasting time, but for the sake of completeness: that’s okay, but then also accept that (software) development moves on and your platform is dead. I wouldn’t even keep a device taking more than 30 seconds to get me to the login screen nowadays. But then again: your device, your time.
@guy038 said:
Don’t be mistaken ! It’s a problem of money and I just can go out home and afford, myself, a Win10 laptop, these next days !
No, it’s not! Stop spreading such lies!
AFAIK, up to mid-January, Microsoft offered its Windows 10 upgrade for free for any device having a genuine Windows 7 or newer. So, you had several chances to update any of your devices for free - even if it wasn’t equipped with Windows 7 upon your purchase, a new Windows 7 (even Professional!) costs less than 20 bucks as of now.
You needn’t to buy new hardware in order to upgrade your OS as long as it’s not that old - and even if it was, put in a SSD to get a 10 times shorter boot time.@guy038 said:
[…] But I’m sure that I will think about this antiquity, with some nostalgia ( and also for an other simple reason : it would have been my laptop when I was young !! ) […]
Nostalgia is the top reason for this whole mankind to be stuck in such a slow progression rate. We could be way further, if only mankind could drop its silly nostalgic behaviors. Don’t believe me? Take human languages as an example: is it really that hard to agree on one language (maybe even a new one, so nobody feels discriminated) so that everybody understands everybody without translation?
And no, by unifying language I do not mean sacrificing your culture. -
@Carlo-TNX said:
sorry for delay, I didn’t get the notification…
I was completly wrong, access time doesn’t matter in my problem (it changes after file status auto-detection).
I’m on Windows 7 / 10 and files on a debian machine, it’s something related to network samba shares, since I can’t reproduce with local files.
On network I reproduce in this way:
- open a file
- change and save it
- leave (blur) n++ window
- wait 10 seconds
- focus n++ window
- change alert shown
I’ll update this thread as soon I find more details.
I’ve finally solved the file status auto-detection problem.
It was a Win7 <> SMB2 cache problem (it didn’t affect N++ before 7.5.2).
I’ve solved adding:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters\FileInfoCacheLifetime[DWORD] = 0Thanks to: https://serverfault.com/a/487401
-
P PeterJones locked this topic on
