Bug ID: 383406
Summary: Should reset read-only buffer flag when saving under a
Platform: Debian stable
Target Milestone: ---
When saving a read-only buffer with "Save as" under another name, the buffer
remains read-only after the save.
In my opinion, it is pointless to keep read-only flag for a newly created file.
After all we have just wrote the file, why should it be read-only after
I advise to reset read-only flag, when saving under a different name.
You are receiving this mail because:
You are watching all bug changes.