Skip to content

Document all conditions that trigger file lock and unlock #796

@tbsbdr

Description

@tbsbdr

Create clear documentation outlining all conditions under which a file becomes locked or unlocked.

This should include:

  • User actions (e.g. opening, editing, saving)
  • System events (e.g. timeouts, crashes, background processes)
  • Temporary or system files (e.g. ~$ files)
  • etc. ...

The goal is to make file locking behavior transparent to users so they understand why a file is locked and when it will be released.

@Svanvith as discussed 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions