The developer only pays attention to any given “new release” thread in the Community Forums for a short while – and especially once he’s moved on to a newer version, he won’t be paying attention to the thread for an older version.

If you want better tracking, follow this FAQ to the Notepad++ Issues tracker on GitHub. You will want to search the existing issues (both open and closed) to make sure you aren’t repeating someone else’s request (I’ve seen this request multiple times).

Even posting the request there, there is no guarantee that it will be implemented to your liking: he may choose to not implement any given feature request, and might not always close issues he’s privately rejected.

@donho Yes, this fixes the problem, thanks!

@Allan-Marques,

It doesn’t seem to do that for me, but maybe I’m not doing it exactly the way you are–can you provide more detail/screenshots?

@Vinod-Jacob

Any updates on the new version of plugin manager

I don’t think you are going to see any replies to that query from the N++ author. Maybe the best you can do is look in the codebase for related commits and infer status from that. Example: I see something on 2018-04-30 that seems related…

@Carlo-TNX said:

@dail
@donho

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.

@donho

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] = 0

Thanks to: https://serverfault.com/a/487401

hi everi one

@donho
Please fix this regression:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4313

Holy Moly, you have absolutely saved me!!! Adobe Bridge is so STUPID that every time you upgrade all keywords are blown away! Each image that I have has the keywords in the exif data but the list of keywords is gone. So since I’ve slept since creating these I forget just exactly how I have things organized. With EXIFTOOL (executed at the command level (DOS)) I can get the keywords and with Notepad++ I can add them into the xml file.
There are probably many other more exciting things to do with Notepad++ but I love it for this simple use.
THANK YOU THANK YOU THANK YOU!

I got an Exception message says Access violation.
I’ve tried installing the older version, version number 7.5, Didn’t get this exception message.
Here is the Screenshot
By the way, 7.5.3 the new updated didn’t fix this issues

(I accidentally wrote that the user should be able to “disable” local conf mode, but I meant enforce! Couldn’t edit. Sorry about the confusion.)

Found an annoying though minor bug in 7.4.2. It’s probably been around for a while.
Editing a 1000+ line CSS file, if I have line 1000 at the bottom of the NPP window, that tab-view shutters like crazy as it tries to reconcile the width of the line-number column and horizontal scroll (I think). No other tab-views are affected. At first, I thought my video card was failing. I adjusted my Npp app width and not only did it go away, but I can’t reproduce it.

@Parpaluck209 Notepad++ is an open source project. You could always code up the feature and get it added through a Pull Request. hint hint

Salut, @donho! The issue with hungin npp on large files preview is successfully fixed in the Notepad++ 7.4.1. Thanks!

Rearranging tabs doesn’t work. Can’t drag them to reorder.

@miaXcova Please disregard and delete my above post. I reinstalled 7.3.2 and can no longer duplicate the above issue I poorly demonstrated. Apologies - was probably something to do with settings.

@Artur-Hareson This is the expected behavior.

@Claudia-Frank nope…it was an update

After installation 7.3 version, the problem is over.
I don’t know why.
Thanks for you help

@donho 7.2.2 does not help. I post some Details at 7.2.2 thread.