n++:
a) lacks a "file information" tool, which shows the basic featuresof the file opened.
b) seems not to be able to interact with files denominated in Windows as 'read-only'. I have some of these files with this attribute acquired only in transit from one OS to another. Most/all editors (including notepad) will allow you to edit the file all the same. This does not seem possible with n++. I am getting crazy out of this!
Does anyone have a solution to this problem to 'force' n++ to let people edit also read-only files?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
a) What kind of information are you talking about? Can you give a few examples?
b) Read-only flag is there for a reason. Editors (text editors, image editors, * editors) must not ignore this flag. Never. If you found an editor, that lets you edit read-only files - you should fill in a bug report on the editors web-site. Notepad++ acts correctly - if you want to edit a file, make sure it isn't read only. Personaly - i think it is great feature of Notepad++ - i can make sure that some important files will not be edited by accident by simply setting read-only attribute.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Other editors allow you to open and edit the file, and prompt for a new filename on save - notepad++ open the file in a read-only mode where it will not allow you to edit the file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
a) Information which I would find useful is the one you camn get from Windows Explorer-> Right Click on the file and go to Properties, i.e. File Size, Date Created, Date modified, flags (read-only, owner etc)
b) ALL text editors I know of WILL allow you to edit files which under windows have a 'read-only' flag. I name three for your convenience, but every single one I tried does the same (except notepad++):
- Windows Notepad (the standard Windows text editor)
- Notetab Light (probably the most successful and supported editor)
- Editpad (another solid text editor)
I believe these will also work normally and allow you editing respectless of flags (even if I could not try them now, but used in the past):
- Crimson editor
- Context
The behaviour of Notepad++ is the one that is non-standard and shopuld be changed. If anything for one reason: flags under windows are 90% of the time set by mistake by windows itself while transferrinf files across PCs or memory cards. So some PCs will show loads of read-only files which were NOT set to that state by their owners.
By definition in my view a text editor should allow to edit content. Maybe a warning message could be passed to the user telling him: "this file is set to read-only: do you want to edit it?", but NOT leave the user with no way of editing the file itself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
a) Ah yes. I noticed that most text editors, word processors, image editors etc. has a Properties menu entry under the File menu. I was always wondering why, though. I never use it. I don't need it. I do not know a single situation, when this could be useful. But, i guess, it's just me - other people needs it... Can you give an example where this is useful?
b) The correct behaviour is NOT TO ALLOW OVERWRITING OF READ-ONLY FILES! At least not silently. Personaly, when developing a project, i might have a few source files that i want to lock. These are usualy files of finished classes (test cases of those classes passes with 100% success) - i don't want to bring a bug in the file by accident, so i just set read-only flag and the Notepad++ will simply not allow me to do anything to the file.
On the other hand i do not have any problems with files copied from non-writable media (CD, DVD etc), because i use FAR manager (it clears the read-only flag automaticaly). I guess, if you're not using FAR - those attributes are not cleared. Then, for you, it might indeed be useful if Notepad allowed to edit and save the files (not without a warning, ofcourse).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>By definition in my view a text editor should allow to edit content.
It is ok for a memory editor to edit content in a read only file.
>Maybe a warning message could be passed to the user telling him: "this file is set to read-only: do you want to edit it?", but NOT leave the user with no way of editing the file itself.
What the editor must never do is save to a read-only file with or without a prompt such as "Would you like to overwrite the read-only file?". The only acceptable course of action when the user attempts to save to a read-only file is to bring up the save-as dialog offering to save to a different file. Under no circumstance should the save dialog ask, overwrite, clear, or assist the user in clearing read-only.
An editor handling read-only must provide it in a separate area like a file manager or file properties and that must never be offered automatically or suggested during a save. If you don't know how to clear read-only, you have no business clearing it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
a) For the File Properties, I find it extremly useful in many occasions.
Just a few here:
- Have to pass the file full path to a friend that needs to read it (same LAN). I go to properties, copy the full path and pass to him without having to fire up Explorer or write very long paths with the risk to get wrong.
- Need to do some calculations on space occupation before uploading a flat database on a server. Just fire up properties and check the file size.
- Need to know when that file was written or modified last time. Fire up the Properties and check it before I start my editing.
I really miss this function in Notepad++
b) For the read-only, I have no idea what FAR is, but I can guarantee you are simplyfying the situation. I work in a LAN (managed by IT professionals) where we have clusters of different machines (some linux, some HP UX, some BSD, some Windows of differnet versions etc). Plus of course all type of external devices, USB HD, USB keys etc.
The programs used to interface these systems are NOT that easy to control, and you end up with really loads of read-only flags which are NOT set by the file owner.
In short: for a small system where you have few files and control everything read-only might be nice.
If you have 5+ OSs talking each other and 1000s of file exchanges, I can guarantee you that manual change of properties is a nightmare and having a text-editor which stops you editing the file is also not a choice.
Why don't you simply have a setting in the Configuration file to have something like:
'Overrulle any read-only flags' (set by default to 0). So if people in my situation want to force the editor to edit the file, they can....
And BTW: ALL other editors I mentioned allow you to edit those 'read-only' files with no confirmation, no need to press any key and no need to change anything in their original configuration. I understand that for you this is a bug, but if this is done in 95% of the text editors in the market, you have to ask if this is a feature to which users are also used to and maybe think to introduce it (optionally at least) in notepad++
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I have no idea what FAR is
FAR Manager is a shareware tool for managing files. It's Norton Comander clone. But it isn't relevant to the problem, i guess.
>The programs used to interface these systems are NOT that easy to control, and you end up with really loads of read-only flags which are NOT set by the file owner.
From your description, i understand that the tools you use set read-only flag without even asking the user about it. Wich leads to the following conclusion: what you're asking us is to change the Notepad++, so that it is easier to work with the (irrelevant to Notepad++) buggy tools you use. Does that sounds right to you? Maybe you should report to the authors of those tools, so that they can fix the bugs? Or am i wrong about this?
> I understand that for you this is a bug
You're right, i think it is a bug in those editors. Or maybe i should say, that it's a feature of Notepad++ - not to ingore the read-only flag.
In fact, i'd like to ask you something about those other editors... Is there a way (in those other editors) to *lock* the file, so that you (or someone else) do not change it by accident? Because with Notepad++ you *can*! You simply set the read-only flag for that file.
Again, i don't think read-only flag should ever be ignored or cleared without even notifying the user about the action. So far, i understand your frustration caused by the other tools that sets this flag for no reason. Maybe there will be some configurable changes, but personaly - i'd prefer Notepad++ to work the way it works now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today I noticed that Notepad++ (v3.9) also seems to have a problem with detecting access right on files. After editing a configuration file and saving it using Notepad++, I discovered that nothing had changed. Notepad++ did not give any error message on this.
The behaviour in this case (and all cases where the write attempt is unsuccessful) should be: At least a warning to the user. I case of wrong access rights, the option to save the file somewhere else is the only alternative. In case of the read-only property, an option of removing the read-only property from within Notepad++ is also very useful. There is no real objection to do this: if a user can do this using the Explorer, why not make it easier and allow to do this form Notepad++.
The mos ideal situation would be:
Give a warning about the failing write-attempt, with three options:
- save under a different name/location,
- remove read-only property permanently
- re-apply read-only property after saving the file
In effect, the same you could do using the Explorer, but much easier for the user!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I only recently started using notepad++ and find it to be a very useful product. I agree that the one thing I would like to see is some notification on the title bar or status bar that the file I am currently reading/editing is set to "read only" access. That saves head scratching when I cannot save the file and do not immediately see the reason. I just upgraded to version 5.3.1 and was disappointed that this problem still exists.
Otherwise, I had no problems using Notepad++.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Again, have a look at how other editors support the read-only flag: they allow you to edit documents, but on save they prompt to save-as under a different name, since the document is read-only.
In Notepad++ you can open & view a read-only file, but you cannot edit it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>Have to pass the file full path to a friend that needs to read it (same LAN)
TextFX Insert | Current Full Path
>just fire up properties and check the file size.
"nb char" at the bottom of the screen.
>manual change of properties is a nightmare
In your case you'd want to go the extra mile and leave the the read-only clear after the save. This would save trouble for the editors that do not work with read-only easily. This of course would be a secret setting.
Without changing any settings, these editors do not allow editing of read only files.
Windows Notepad, brings up Save As
UltraEdit, no editing allowed, did not indicate to user that readonly needed to be cleared, brings up Save As
PSPad, no editing allowed until read only cleared, easily saves over read-only files and the read-only bit is replaced after save
Textpad, tells user to change readonly, editing allowed when read-only is cleared, brings up Save As
Only one editor would let me save to a read only file and none left the read-only bit turned off.
>i don't think read-only flag should ever be ignored or cleared without even notifying the user about the action
It shouldn't be cleared or overruled *with* a notification to the user either.
>Why don't you simply have a setting in the Configuration file to have something like:
This would be ok as a secret setting in the INI or XML config files but it shouldn't be available anywhere in the user interface. Noone but the IS department should be able to enable overwriting read-only files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These editors typically allow editing after clearing read-only but only offer Save As to change the name. There's no sequence that will overwrite read-only files.
The following editors will save to read-only files as noted.
Boxer, Zeus, can't edit until read-only is cleared which immediately clears the read-only attribute on the file.
HTML-Kit, odd error produced, read only file renamed and deleted, new non read-only file saved in its place.
Textpad, can't edit until read-only is cleared, Save notices read-only and brings up Save As dialog which is able to overwrite the read-only file after an unexpected beep leaving a non read only file in it's place.
Notepad++ is in the majority being an editor that refuses to write to read-only files. The editors that do write to read-only files handle it inconsistently and are not clear about what they are doing.
Do you have a solution that makes your situation easy while allowing IT the option to block all read-only access?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no easy answer for an optimal read-only flag behaviour.
But introducing the 'option' (by default disabled) to overrule the flag and edit the file even if it is read-only might help users.
Or if this really cannot be made, the program should all the same allow editing, but once the user asks for saving, it should refuse to save in the same file explaining it is read-only and offering the option to save as in a different name.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe the desired behavior is implemented by Visual Studio:
1) respect the RO flag by opening the file in RO mode
2) detect when the user attempts to modify the file (as he tries to type)
3) Ask the user what he wants to do: leave the file as RO and refuse the modification or Set the file as RW and accept changes
Just my 2 cents....
-Pat
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just made some changes(based on ver3.4) so that the read-only files can be edited with npp. If your interested in it. Please contact me at <dyuweb-1@yahoo.com>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
n++:
a) lacks a "file information" tool, which shows the basic featuresof the file opened.
b) seems not to be able to interact with files denominated in Windows as 'read-only'. I have some of these files with this attribute acquired only in transit from one OS to another. Most/all editors (including notepad) will allow you to edit the file all the same. This does not seem possible with n++. I am getting crazy out of this!
Does anyone have a solution to this problem to 'force' n++ to let people edit also read-only files?
a) What kind of information are you talking about? Can you give a few examples?
b) Read-only flag is there for a reason. Editors (text editors, image editors, * editors) must not ignore this flag. Never. If you found an editor, that lets you edit read-only files - you should fill in a bug report on the editors web-site. Notepad++ acts correctly - if you want to edit a file, make sure it isn't read only. Personaly - i think it is great feature of Notepad++ - i can make sure that some important files will not be edited by accident by simply setting read-only attribute.
Other editors allow you to open and edit the file, and prompt for a new filename on save - notepad++ open the file in a read-only mode where it will not allow you to edit the file.
a) Information which I would find useful is the one you camn get from Windows Explorer-> Right Click on the file and go to Properties, i.e. File Size, Date Created, Date modified, flags (read-only, owner etc)
b) ALL text editors I know of WILL allow you to edit files which under windows have a 'read-only' flag. I name three for your convenience, but every single one I tried does the same (except notepad++):
- Windows Notepad (the standard Windows text editor)
- Notetab Light (probably the most successful and supported editor)
- Editpad (another solid text editor)
I believe these will also work normally and allow you editing respectless of flags (even if I could not try them now, but used in the past):
- Crimson editor
- Context
The behaviour of Notepad++ is the one that is non-standard and shopuld be changed. If anything for one reason: flags under windows are 90% of the time set by mistake by windows itself while transferrinf files across PCs or memory cards. So some PCs will show loads of read-only files which were NOT set to that state by their owners.
By definition in my view a text editor should allow to edit content. Maybe a warning message could be passed to the user telling him: "this file is set to read-only: do you want to edit it?", but NOT leave the user with no way of editing the file itself.
a) Ah yes. I noticed that most text editors, word processors, image editors etc. has a Properties menu entry under the File menu. I was always wondering why, though. I never use it. I don't need it. I do not know a single situation, when this could be useful. But, i guess, it's just me - other people needs it... Can you give an example where this is useful?
b) The correct behaviour is NOT TO ALLOW OVERWRITING OF READ-ONLY FILES! At least not silently. Personaly, when developing a project, i might have a few source files that i want to lock. These are usualy files of finished classes (test cases of those classes passes with 100% success) - i don't want to bring a bug in the file by accident, so i just set read-only flag and the Notepad++ will simply not allow me to do anything to the file.
On the other hand i do not have any problems with files copied from non-writable media (CD, DVD etc), because i use FAR manager (it clears the read-only flag automaticaly). I guess, if you're not using FAR - those attributes are not cleared. Then, for you, it might indeed be useful if Notepad allowed to edit and save the files (not without a warning, ofcourse).
>By definition in my view a text editor should allow to edit content.
It is ok for a memory editor to edit content in a read only file.
>Maybe a warning message could be passed to the user telling him: "this file is set to read-only: do you want to edit it?", but NOT leave the user with no way of editing the file itself.
What the editor must never do is save to a read-only file with or without a prompt such as "Would you like to overwrite the read-only file?". The only acceptable course of action when the user attempts to save to a read-only file is to bring up the save-as dialog offering to save to a different file. Under no circumstance should the save dialog ask, overwrite, clear, or assist the user in clearing read-only.
An editor handling read-only must provide it in a separate area like a file manager or file properties and that must never be offered automatically or suggested during a save. If you don't know how to clear read-only, you have no business clearing it.
a) For the File Properties, I find it extremly useful in many occasions.
Just a few here:
- Have to pass the file full path to a friend that needs to read it (same LAN). I go to properties, copy the full path and pass to him without having to fire up Explorer or write very long paths with the risk to get wrong.
- Need to do some calculations on space occupation before uploading a flat database on a server. Just fire up properties and check the file size.
- Need to know when that file was written or modified last time. Fire up the Properties and check it before I start my editing.
I really miss this function in Notepad++
b) For the read-only, I have no idea what FAR is, but I can guarantee you are simplyfying the situation. I work in a LAN (managed by IT professionals) where we have clusters of different machines (some linux, some HP UX, some BSD, some Windows of differnet versions etc). Plus of course all type of external devices, USB HD, USB keys etc.
The programs used to interface these systems are NOT that easy to control, and you end up with really loads of read-only flags which are NOT set by the file owner.
In short: for a small system where you have few files and control everything read-only might be nice.
If you have 5+ OSs talking each other and 1000s of file exchanges, I can guarantee you that manual change of properties is a nightmare and having a text-editor which stops you editing the file is also not a choice.
Why don't you simply have a setting in the Configuration file to have something like:
'Overrulle any read-only flags' (set by default to 0). So if people in my situation want to force the editor to edit the file, they can....
And BTW: ALL other editors I mentioned allow you to edit those 'read-only' files with no confirmation, no need to press any key and no need to change anything in their original configuration. I understand that for you this is a bug, but if this is done in 95% of the text editors in the market, you have to ask if this is a feature to which users are also used to and maybe think to introduce it (optionally at least) in notepad++
> I have no idea what FAR is
FAR Manager is a shareware tool for managing files. It's Norton Comander clone. But it isn't relevant to the problem, i guess.
>The programs used to interface these systems are NOT that easy to control, and you end up with really loads of read-only flags which are NOT set by the file owner.
From your description, i understand that the tools you use set read-only flag without even asking the user about it. Wich leads to the following conclusion: what you're asking us is to change the Notepad++, so that it is easier to work with the (irrelevant to Notepad++) buggy tools you use. Does that sounds right to you? Maybe you should report to the authors of those tools, so that they can fix the bugs? Or am i wrong about this?
> I understand that for you this is a bug
You're right, i think it is a bug in those editors. Or maybe i should say, that it's a feature of Notepad++ - not to ingore the read-only flag.
In fact, i'd like to ask you something about those other editors... Is there a way (in those other editors) to *lock* the file, so that you (or someone else) do not change it by accident? Because with Notepad++ you *can*! You simply set the read-only flag for that file.
Again, i don't think read-only flag should ever be ignored or cleared without even notifying the user about the action. So far, i understand your frustration caused by the other tools that sets this flag for no reason. Maybe there will be some configurable changes, but personaly - i'd prefer Notepad++ to work the way it works now.
Today I noticed that Notepad++ (v3.9) also seems to have a problem with detecting access right on files. After editing a configuration file and saving it using Notepad++, I discovered that nothing had changed. Notepad++ did not give any error message on this.
The behaviour in this case (and all cases where the write attempt is unsuccessful) should be: At least a warning to the user. I case of wrong access rights, the option to save the file somewhere else is the only alternative. In case of the read-only property, an option of removing the read-only property from within Notepad++ is also very useful. There is no real objection to do this: if a user can do this using the Explorer, why not make it easier and allow to do this form Notepad++.
The mos ideal situation would be:
Give a warning about the failing write-attempt, with three options:
- save under a different name/location,
- remove read-only property permanently
- re-apply read-only property after saving the file
In effect, the same you could do using the Explorer, but much easier for the user!
Oops... just noticed that the Edit menu already has "Set read Only" and "Clear read only Flag" options. That's great and should be even enough...
Still there is the issue of not warning when writing the file is unsuccessful, either because of the read-only property or the access rights.
I only recently started using notepad++ and find it to be a very useful product. I agree that the one thing I would like to see is some notification on the title bar or status bar that the file I am currently reading/editing is set to "read only" access. That saves head scratching when I cannot save the file and do not immediately see the reason. I just upgraded to version 5.3.1 and was disappointed that this problem still exists.
Otherwise, I had no problems using Notepad++.
Again, have a look at how other editors support the read-only flag: they allow you to edit documents, but on save they prompt to save-as under a different name, since the document is read-only.
In Notepad++ you can open & view a read-only file, but you cannot edit it.
>Have to pass the file full path to a friend that needs to read it (same LAN)
TextFX Insert | Current Full Path
>just fire up properties and check the file size.
"nb char" at the bottom of the screen.
>manual change of properties is a nightmare
In your case you'd want to go the extra mile and leave the the read-only clear after the save. This would save trouble for the editors that do not work with read-only easily. This of course would be a secret setting.
Without changing any settings, these editors do not allow editing of read only files.
Windows Notepad, brings up Save As
UltraEdit, no editing allowed, did not indicate to user that readonly needed to be cleared, brings up Save As
PSPad, no editing allowed until read only cleared, easily saves over read-only files and the read-only bit is replaced after save
Textpad, tells user to change readonly, editing allowed when read-only is cleared, brings up Save As
Only one editor would let me save to a read only file and none left the read-only bit turned off.
>i don't think read-only flag should ever be ignored or cleared without even notifying the user about the action
It shouldn't be cleared or overruled *with* a notification to the user either.
>Why don't you simply have a setting in the Configuration file to have something like:
This would be ok as a secret setting in the INI or XML config files but it shouldn't be available anywhere in the user interface. Noone but the IS department should be able to enable overwriting read-only files.
SC Unipad
Crimson Editor
EditPlus
Notetab
SciTE
These editors typically allow editing after clearing read-only but only offer Save As to change the name. There's no sequence that will overwrite read-only files.
The following editors will save to read-only files as noted.
Boxer, Zeus, can't edit until read-only is cleared which immediately clears the read-only attribute on the file.
HTML-Kit, odd error produced, read only file renamed and deleted, new non read-only file saved in its place.
Textpad, can't edit until read-only is cleared, Save notices read-only and brings up Save As dialog which is able to overwrite the read-only file after an unexpected beep leaving a non read only file in it's place.
Notepad++ is in the majority being an editor that refuses to write to read-only files. The editors that do write to read-only files handle it inconsistently and are not clear about what they are doing.
Do you have a solution that makes your situation easy while allowing IT the option to block all read-only access?
There is no easy answer for an optimal read-only flag behaviour.
But introducing the 'option' (by default disabled) to overrule the flag and edit the file even if it is read-only might help users.
Or if this really cannot be made, the program should all the same allow editing, but once the user asks for saving, it should refuse to save in the same file explaining it is read-only and offering the option to save as in a different name.
I believe the desired behavior is implemented by Visual Studio:
1) respect the RO flag by opening the file in RO mode
2) detect when the user attempts to modify the file (as he tries to type)
3) Ask the user what he wants to do: leave the file as RO and refuse the modification or Set the file as RW and accept changes
Just my 2 cents....
-Pat
I just made some changes(based on ver3.4) so that the read-only files can be edited with npp. If your interested in it. Please contact me at <dyuweb-1@yahoo.com>