When I rename a file outside NP++, NP++ simply says the file doesn't exist anymore and asks if I want to keep the file in the editor...
Of course, the file STILL exists, it just has got another name.
I would like NP++ to recognize this and ask if the file is to be renamed in NP++, too.
If I would choose not to rename the file, it should be marked somewhere simply as a new file or a file that has changes and still has to be saved, even if the file itself may not have changed since it was opened.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you clarify what you mean ?
In NP++, a file that is deleted, or renamed, gives a message to that effect, asking
if you want to keep the editor copy.
In fact, it asks you that EVERY time you switch to NP++, which could be an
overkill/annoying in some situations
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Will you implement file renamed notification in N++?
When a file has changed outside N++, or has been deleted, N++ asks you for an "update" action.
Will this also be implemented for files that are open in N++ and are renamed outside N++?
Yeah, right...
When I rename a file outside NP++, NP++ simply says the file doesn't exist anymore and asks if I want to keep the file in the editor...
Of course, the file STILL exists, it just has got another name.
I would like NP++ to recognize this and ask if the file is to be renamed in NP++, too.
If I would choose not to rename the file, it should be marked somewhere simply as a new file or a file that has changes and still has to be saved, even if the file itself may not have changed since it was opened.
Can you clarify what you mean ?
In NP++, a file that is deleted, or renamed, gives a message to that effect, asking
if you want to keep the editor copy.
In fact, it asks you that EVERY time you switch to NP++, which could be an
overkill/annoying in some situations