Changing Read-Only Status of Files
In this section:
Different version control systems have different semantics for the action of removing read-only status from a file so that you can edit it. Some systems never put read-only status on local files at all unless specifically configured to do so (i.e. the system is configured to support the file locking model).
Different version control systems use different names for this action: check out, edit, Open for Edit, or Get. Regardless of the terminology used by your VCS, if it sets read-only status on your local working files, you can remove read-only status and make files writeable from within RubyMine, which will also take care of setting a lock on the server, or take whatever other action is required by the VCS, via the respective VCS integration.
This behavior is configurable in the Confirmation page of the Version Control settings.
Enabling explicit removal of read-only status
To enable explicit removal of read-only status:
- In the Confirmation page of the Version Control settings, check the option Show "Clear Read-Only Status" Dialog.
Changing writable status by icon
You can make a file writable using the lock icon in the Status bar. Open the desired file in the editor, and click the lock, as shown below:
Removing read-only status in Perforce looks as follows:
- With the Show "Clear Read-Only Status" Dialog option enabled, an attempt to edit a
file brings up the respective dialog box.
If you click the radio button Using file system, the file will not be added to the default changelist. If you click radio button Using version control integration, the file is added to the default changelist.