Feature Request: Add Read-Only Mode/Lock for Safer Code Review and Demos #45343
CreatorHell
started this conversation in
Feature Requests
Replies: 1 comment
-
|
Agreed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Use Case:
When reviewing code or giving live demonstrations (especially in pair programming/screen sharing scenarios), accidental edits frequently occur. A read-only lock would:
Prevent unintended modifications during critical sessions
Allow focused code reading without edit distractions
Provide peace of mind when sharing screens
Suggested Implementation:
Toggleable via command palette (Ctrl/Cmd+Shift+P) or status bar icon
Visual indication (e.g. lock icon, red status bar, or dimmed text)
Optional password/privilege requirement to unlock (for enterprise scenarios)
Bonus Considerations:
Workspace-level vs file-level locking granularity
Integration with version control (e.g. auto-lock files not in current branch)
This would significantly improve Zed’s utility as both a production and presentation tool. Similar implementations exist in VSCode (“.lock” files) and IntelliJ (“View as Read-Only”).
Beta Was this translation helpful? Give feedback.
All reactions