Firstly, I'd like to say that NP++ is an excellent product!
I've found that the "Keep non existing file dialog" behavior is not correct and a bit annoying. And I think some small changes would greatly improve this.
When an open file no longer exists, NP++ asks whether the file should be left open in the editor. It doesn't remember your response, so each time you switch back to NP++ it asks again. It's quite common for that to happen, because temporary files are often opened and then deleted immediately.
You can't turn off this functionality through options. If you turn off the status update check, you also lose the notification when files are changed (which is very important).
I'd like to suggest a couple of solutions for consideration:
1. Add an additional option/preference to switch off the "non existing file" test.
2. Make NP++ remember the answer to your question. So you only get asked once.
It would probably be good to have both of these implemented ... but either one of these would make a big difference.
Regards,
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firstly, I'd like to say that NP++ is an excellent product!
I've found that the "Keep non existing file dialog" behavior is not correct and a bit annoying. And I think some small changes would greatly improve this.
When an open file no longer exists, NP++ asks whether the file should be left open in the editor. It doesn't remember your response, so each time you switch back to NP++ it asks again. It's quite common for that to happen, because temporary files are often opened and then deleted immediately.
You can't turn off this functionality through options. If you turn off the status update check, you also lose the notification when files are changed (which is very important).
I'd like to suggest a couple of solutions for consideration:
1. Add an additional option/preference to switch off the "non existing file" test.
2. Make NP++ remember the answer to your question. So you only get asked once.
It would probably be good to have both of these implemented ... but either one of these would make a big difference.
Regards,
Matt