Reset read-only dialog - undo "don't show this again"
Hi folks,
when you make a file read-only (e.g. via the lock icon) and try to write inside the file, a popup comes up, asking for a way how to reset read-only. I did check the "don't show this again" dialog and can't find a way to show the dialog again.
Can somebody advise how I reset this behaviour?
Much thanks in advance.
Please sign in to leave a comment.
Please try Version Control | Confirmation > Show "Clear Read-only Status" Dialog checkbox, that should work.
Awesome, thanks Vasiliy!
The checkbox was still checked, but disabling it->apply->check it->apply again did work.
Hi Vasiliy Yur and IntelliJ team,
I face the very same issue as Dochoh.
I want to protect files from myself accidentally updating them.
When I have the current and the new versions of code open in two tabs I want to protect the current version from updating it accidentally. Since both tabs have almost identical names and codes it is very easy to start typing the wrong one and I've done it many times and the following painful recovery process.
At the moment IntelliJ is very eager to help you out and remove the read-only status of a file once you start typing in it. That totally defeats the purpose of the read-only state.
I don't want to see "But I wonna help! Would you like to make it writable for you?!" type of message with an extremely easy way to hit yes before you even notice what the message was about.
Currently, if you check "Don't ask again" and click "Cancel". Meaning, do not make it writable and do not ask again. The system does not make it writable (which is good), but cancel "Do not ask again" and eagerly asks again.
Is there a way to make it harder to make the file writable by mistake?
I usually start an update with a few enters to open space for it. The first enter triggers the question, the second makes the file writable, and the third updates the file. The window opens and closes fast enough for me not to see it.
Thank you in advance,
Dimitar
No, unfortunately, there isn't.
It's fair to assume that you are not using a version control system since the process is painful for you. May I ask why?
I do use version control. I am a database person and the DB procedures I work on usually take between few minutes and few days. Sometimes while waiting I create more servers and run a modified version on each server before deciding which approach to take. While the versions are still in a flux state I don't commit them. Meanwhile, I would like to make only one file writable and keep the rest open, but in read-only mode, so I can see them while making sure I will not accidentally update a wrong file.
BTW: The pain in the recovery is not in restoring the old/current version, but find out what did not go where it was supposed to go, what version is currently running on which server (if the code in the file is already different then the deployed version), how to reintegrate it correctly, and where and how to restart the process from to minimize the additional waste of human or machine time and potential issues.
I see now, thank you for the explanation. Unfortunately, there's still nothing we can offer at the moment to work that around.
Please submit this as a usability issue on our tracker: https://youtrack.jetbrains.com/newIssue?project=IDEA