Yes, sorry for "must" and "very wrong" :) but that definitely would be cool.
The goal is to modify read only file without actually saving it.
Use case (in common) is to explore large data file by modifying its structure. (xml, html files e.t.c).
Macro doesnt work with files opened from URL. the alert pops up "this macro only works on local files"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With this explanation I have to admit, that all the editors I know are able to edit read only files. They fail on save, but allow editing. Any ideas of how this could "work for us"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> The goal is to do save as later ?
Yes. And even not to save it at all: sometimes while exploring the content of a file I need to modify it's structure: indent xml, or find/replace just to count hits.. e.t.c.
I think - something, like warn user by "unable to save readonly file" would be enough.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is pretty straightforward to implement, and I have it working well on my local. There are 5 plugins that I have found so far, and there may be others, that might need to be adjusted: the AStylePlugin, the BeautyPlugin, the P4Plugin, the TaskList plugin, and the TextTools plugin. I don't think the P4 plugin needs to be changed. For the use cases mentioned above, at least the beautifiers and the text tools should be adjusted. I'll go ahead and commit my changed for the jEdit core code, then work on the plugins separately.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You mean it should allow you to edit the file, but of course not save it?
The goal is to do save as later ?
I know many text editors which don't allow saving read only files. This is an open question. Definitely it shouldn't be done without warning.
Matthieu, this question probably regards files marked as read only, when it can be bypassed, by temporarily changing the flag.
I understand this feature request, but I don't agree with neither "must" nor "very wrong".
Macros - Files - Toggle ReadOnly seems sufficient. With the MenuEditor plugin installed, this can easily be added to the "File" menu.
Yes, sorry for "must" and "very wrong" :) but that definitely would be cool.
The goal is to modify read only file without actually saving it.
Use case (in common) is to explore large data file by modifying its structure. (xml, html files e.t.c).
Macro doesnt work with files opened from URL. the alert pops up "this macro only works on local files"
With this explanation I have to admit, that all the editors I know are able to edit read only files. They fail on save, but allow editing. Any ideas of how this could "work for us"?
Changing the subject since it seems the initial poster wanted to be able to edit the buffer without changing the actual file.
> The goal is to do save as later ?
Yes. And even not to save it at all: sometimes while exploring the content of a file I need to modify it's structure: indent xml, or find/replace just to count hits.. e.t.c.
I think - something, like warn user by "unable to save readonly file" would be enough.
This is pretty straightforward to implement, and I have it working well on my local. There are 5 plugins that I have found so far, and there may be others, that might need to be adjusted: the AStylePlugin, the BeautyPlugin, the P4Plugin, the TaskList plugin, and the TextTools plugin. I don't think the P4 plugin needs to be changed. For the use cases mentioned above, at least the beautifiers and the text tools should be adjusted. I'll go ahead and commit my changed for the jEdit core code, then work on the plugins separately.
Fixed in revision 23971. Plugins are still a separate issue and will be handled outside the scope of this ticket.