简体中文
EnglishHow TextMate Supports Version Control
Updated
TextMate supports version control by surfacing changes in two places—the file browser and the editor—and by letting you review and commit at a finer grain than "all or nothing." According to the product page, it shows which files have changes in the file browser view, which lines have changes in the editor view, brings up a diff of the current file's changes, and supports committing a subset of changes. The page states this works "for all the major version control systems," so the features are presented as system-agnostic rather than tied to one tool.
What you see while working
Changed files in the file browser
The file browser marks files that have changes. This gives you a project-level view of what's been touched without leaving the editor or running a separate status command.
Changed lines in the editor
Within an open file, the editor view indicates which lines have changed. You can see the scope of an edit in context rather than reconstructing it from memory.
Reviewing changes
Diff of the current file
TextMate can bring up a diff of the current file's changes. This is the review step: compare what's on disk against the committed state before deciding what to keep.
Committing a subset
The page explicitly lists the ability to commit a subset of changes. Instead of committing everything at once, you can select part of the work and commit that portion—useful when a file contains both a fix you want to record now and unrelated edits you want to keep working on.
What the page does and doesn't specify
| Question | What the source says |
|---|---|
| Which version control systems? | "All the major version control systems" (no list given) |
| How is a subset selected for commit? | Not described |
| Is there a built-in commit UI, or does it call external tools? | Not described |
| Are there keyboard shortcuts for these actions? | Not described |
The page describes capabilities, not mechanics. If your decision depends on a specific system (for example, a particular distributed or centralized tool) or on the exact commit workflow, verify that against the app itself rather than assuming from this summary.
How to evaluate it for your workflow
- Install TextMate 2.0 (the page lists macOS 10.12 or later as the requirement) and open a project that is already under version control.
- Make a small edit and confirm the file browser marks the file and the editor marks the changed lines.
- Open the diff for that file and check that it matches what you expect.
- Test the subset-commit path on a file with two unrelated edits: stage one, commit, and confirm the other remains uncommitted.
If steps 2–4 behave as described with your version control system, the integration fits your setup. If the diff or subset commit doesn't appear for your system, that's the practical limit to check before relying on it.
Where this fits among TextMate's features
Version control is one of several editing-oriented capabilities on the page, alongside multiple carets, file search, scoped settings, commands, snippets, bundles, and macros. The version control features are presented as awareness and review tools inside the editor—seeing changes and committing selectively—rather than as a replacement for a full version control client. For history browsing, branching, or merging, the page makes no claims.